Enterprise TruRisk™ Platform Release 3.25
August 10, 2026
We are introducing the following new enhancements for Enterprise TruRisk™ Platform.
Issues Addressed
The following important and notable customer issues are fixed in this release:
| Category/Component | Application | Description |
|---|---|---|
| Cloud Agent Search | Cloud Agent | Resolved an asset indexing issue that caused Cloud Agent QQL searches to return incorrect results for agent communication status. Due to changes in data retrieval logic, asset records were indexed with outdated values, causing recently checked-in assets to appear as non-communicating. Asset information is now re-fetched before indexing, and asset communication filters return accurate results. |
| Asset Reporting | Shared Platform | Resolved an issue where users received an Internal Server Error (500) and could not open asset details from the Vulnerabilities view when assets contained non-standard identifier values. Validation logic now handles invalid asset identifiers correctly, and asset details pages load successfully. |
| Reporting | Administration | Fixed a discrepancy between the ADMIN UI and exported User Management CSV reports. The CSV export previously included modules that were hidden in the UI because visibility rules were not consistently applied. The export process now uses the same module visibility rules as the UI, ensuring matching module counts and module lists. |
| Asset Reporting | Threat Protection | Addressed an issue where assets were incorrectly displayed as impacted in Microsoft Patch Tuesday Security Update Reviews. Asset-to-vulnerability mapping logic has been corrected so impacted asset counts and vulnerability associations are now accurately displayed. |
| Dashboard Widgets | Shared Platform | Resolved inaccurate Risk Score Trending data where the dashboard trend calculations used a different scoring version than the displayed TruRisk score. Trending widgets now show consistent risk score calculations and accurate historical trends. |
| Policy Audit Jobs | Shared Platform | Fixed a Policy Audit and Audit Fix job processing issue that caused completed jobs to be marked as timed out. The problem was related to malformed tracking data in the asset feed header. Job execution status is now reported correctly and completed jobs no longer appear as timeouts. |
| WAS Scans | WAS | Fixed an issue where non-QSS WAS schedules incorrectly displayed scans as Error on the UI even after scans completed successfully. A scheduling validation issue caused long-running scans to be marked incorrectly during subsequent schedule executions. Completed scans now retain the correct status. |
| Scan Schedule API | WAS API | Restored the missing lastScan.name field in the WAS Schedule APIs. The endpoints /qps/rest/3.0/get/was/wasscanschedule/ and related schedule APIs now return the scan name under the lastScan section, restoring compatibility with customer integrations that depended on this field. |
| Scan Schedule API | WAS API | The endpoint /qps/rest/3.0/search/was/wasscanschedule previously returned HTTP 400 responses when schedule records contained null last-scan values. The API now handles these records correctly and returns valid search results. |
| Authentication | WAS API | Fixed a security issue where authentication record passwords were exposed in API responses. The GET/SEARCH WAS Authentication Record API V3 now masks form credentials and server passwords, preventing sensitive information from being returned in API output. |
| Authentication | WAS API | Fixed API certificate upload failures when creating authentication records through /qps/rest/3.0/create/was/webappauthrecord. Certificate validation logic was incompatible with newer Java security restrictions, causing upload failures. Client certificates can now be uploaded successfully through the API. |
| API Support | Malware Detection Service API | Removed the unsupported Malware Detection API endpoint /qps/rest/1.0/download/md/detection from product documentation. Customers previously encountered OPERATION_NOT_SUPPORTED errors because the endpoint was never supported. Documentation now correctly reflects available API functionality. |