- Knowledge base
- Product news
- Release notes
-
Security updates
-
Product news
-
Next-Gen Vulnerability Management
-
Getting started
-
General
-
Operating status
-
Network & System Security
-
Web Application Security
-
Cloud Security
-
API Security
-
Phishing Simulation & Awareness Training
-
Attack Surface Management
-
Scanner Appliance
-
Device Agent
-
On-premise platform deployment
-
Asset management
-
Vulnerability manager
-
Reports
-
Digest reports
-
Organizer
-
Continuous monitoring
-
Integrations
-
Platform API
-
Remediation
-
Users
-
PCI DSS
-
Terms & conditions
-
Dashboard
2025-03-05: Performance improvements, API & Device Agent feature enhancements
Headlines in this release:
Public API improvements
Full severity details
Devices now display full severity information instead of a max severity when listing devices through the API.
Schedule owner set
The user that creates a schedule via the API is now the set owner for that schedule.
Device Agent enhancements
Device name updates
In some instances, changes to device names on the source device were not properly synchronized and reflected in Security Center. We have now enhanced the synchronization process to ensure that device name changes reliably update across all Windows environments.
Improved operating system details
Device vulnerabilities now display all the impacted operating systems for each vulnerability. In an upcoming release, this will also be visible for vulnerabilities related to Microsoft patches.
Notice
The Device Agent is available for Windows.
Easier access to common scan profiles
The top recommended scan profile to use when starting a scan now appears at the top of the profile list.
Performance improvements in unified views
In recent weeks, we've significantly optimized performance across key views in Security Center, with a particular focus on the unified assets and vulnerabilities view. These improvements result in faster response times, enhancing both user actions and the overall experience.
Additional enhancements
- Report schedules are now properly created when using the “Schedule and Run” action on the reports page.