[2.5.189] FSE-Windows - July 01, 2025

1. Overview

This article provides an overview of new features and improvements in the Fortanix Filesystem Encryption (FSE)-Windows 2.5.189 release.

2. New Features

• Fortanix FSE now supports automatic key rotation on FSE Windows Agent using a Key rotation policy defined in Fortanix DSM, along with audit logging and access to view rotation history using REST API (JIRA: FSE-365).
  For more information, refer to Filesystem Encryption for Windows as a Service Using Fortanix Data Security Manager - Client Configuration.

• Added support for Prometheus telemetry integration in the Fortanix FSE Windows Agent, enabling the export of encryption metrics to improve observability and monitoring (JIRA: FSE-363).
  For more information, refer to Filesystem Encryption for Windows as a Service Using Fortanix Data Security Manager - Monitoring.

3. Improvements

• Fortanix FSE user interface (UI) now supports updating the heartbeat interval on a mounted drive without requiring a remount or restart (JIRA: FSE-493).
  For more information, refer to Filesystem Encryption for Windows as a Service Using Fortanix Data Security Manager - Client Configuration.

• Added support in Fortanix FSE for Windows to initialize encryption on existing drive points without requiring a drive letter change, enabling seamless encryption for applications that depend on specific drive paths (for example, C:) (JIRA: FSE-359).
  For more information, refer to Filesystem Encryption for Windows as a Service Using Fortanix Data Security Manager - Client Configuration.

4. Known Issues

• The Fortanix FSE agent does not restrict access to files such as databases and logs by default. This means that unauthorized users might access them (JIRA: FSE-185).
  Workaround: Set file permissions to ensure only the Fortanix FSE Agent’s service account and authorized administrators can access these files.

• Named pipe squatting occurs when an unauthorized process listens on a named pipe before the Fortanix Filesystem Encryption service starts. This may lead users to mistakenly connect to the unauthorized process instead of the legitimate service (JIRA: FSE-161).
  Workaround: Ensure that no other service or application on the server uses the same named pipe as the Fortanix Filesystem Encryption service.

5. Installation