> For the complete documentation index, see [llms.txt](https://docs.flopsar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flopsar.com/7/overview/whats-new.md).

# What's New

Flopsar 7.0 is a major release that pairs a completely rebuilt user experience with a significant step forward in security and regulatory readiness. This page summarizes the most important changes; see the linked chapters for full detail.

## Redesigned Workstation

The Workstation application has been rebuilt from the ground up with a modern, streamlined interface. Navigation, search, and the diagnostic views — Live Monitoring, Data Browser, the method execution tree, Data Correlation, and Multidimensional Analysis — have been reorganized around the analyst's workflow, so moving from a high-level signal to the exact root cause takes fewer steps. The result is a faster, clearer, and more consistent experience across the entire product.

## Rebuilt, More Efficient Agent

The agent has been completely rebuilt. The new implementation lowers the runtime overhead the agent places on your application — less CPU and memory spent on instrumentation and data handling — so you can monitor more, more deeply, with less impact on the host. The rebuild also provides a cleaner foundation for the encrypted agent-server channel and for future capabilities. Because the agent is an in-process component, this efficiency gain directly benefits the stability and responsiveness of the monitored application. 

## Workstation Bundled with the Server

The Workstation is now delivered together with the server as a single bundle. There is no separate Workstation installation to deploy, version, or keep in sync: once the server is running, the interface is available directly and is always matched to the server version. This removes a whole class of version-mismatch issues and simplifies rollout and upgrades.

## Cyber Resilience Act Compliance

Flopsar 7.0 introduces a dedicated Trust & Compliance area in the documentation and aligns the product with the requirements of the EU Cyber Resilience Act (Regulation (EU) 2024/2847). This includes a coordinated vulnerability disclosure policy, clear guidance on secure configuration and the intended operating environment, software bill of materials practices, and the supporting material customers need for their own compliance work. See the [*Trust & Compliance*](broken://pages/BCKGtSySMekKuFhkzUPV) and [*Regulatory Compliance*](/7/regulatory-compliance.md) chapters.

## Encrypted Agent-Server Communication

Traffic between agents and the server is now protected by an authenticated, encrypted channel. The transport uses modern primitives — X25519 for ephemeral key exchange, XChaCha20-Poly1305 for authenticated encryption, and BLAKE2b for authentication and key derivation — with a per-application pre-shared key and forward secrecy. Telemetry collected from your applications is therefore protected in transit by default. See [*Cryptography & Key Management*](/7/security/cryptography-and-key-management.md).

## LDAP Authentication

Operators can now authenticate against an external LDAP directory, such as Microsoft Active Directory, in addition to local accounts. LDAP sign-in supports plaintext, encrypted (LDAPS), and fully verified TLS connections, with optional custom CA certificates for internal certificate authorities. Directory users are provisioned automatically on first login, and built-in test actions let you validate connectivity, user search, and login before going live. See [*LDAP*](/7/administrator-guide/ldap.md).

## Security Audit Log

A tamper-evident security audit trail records security-relevant events — sign-ins, user and role changes, key and configuration actions, and more — as structured, sequentially numbered entries linked in a hash chain. A built-in verification command lets you confirm the log has not been altered. This gives operators a reliable, reviewable record for security monitoring and compliance. See [*Logging, Monitoring & Audit Trail*](/7/security/logging-monitoring-and-audit-trail.md).

## Role-Based Access Control

Flopsar 7.0 introduces user roles, replacing all-or-nothing access with fine-grained, permission-based authorization. The built-in **Owner** role holds all permissions and **Guest** holds none, and you can define custom roles that grant exactly the permissions a given group of users needs. Combined with LDAP and the audit log, this lets organizations apply least-privilege access to Flopsar itself. See [*Authentication, Authorization & Identity*](/7/security/authentication-authorization-and-identity.md).

## Rebuilt Data Masking

Data masking has been reworked to protect sensitive values captured from your applications. Flopsar now ships with a set of built-in obfuscation rules that recognize common sensitive data and redact it automatically when invocation parameters are recorded. On top of that, you can define your own masking rules to match the formats specific to your organization, so confidential values never land in the stored data in clear form. See [*Data Masking*](broken://pages/KVPMQ6eBF1x3hw0inq3N) and [*Privacy & Data Handling*](/7/privacy-and-data-handling.md).