Swimlane Vulnerability Response Management Release 25.2.0
New Features and Enhancements
- Added "Requires Attention" Field to core VRM applications (Vulnerability Finding, Vulnerability Case Management, Vulnerability Remediation Item). Field was already present in Vulnerability Asset application.
- Added supporting logic for "Requires Attention" fields in VRM - Vulnerability Response Management playbook.
- "Date Closed", "MTTR", and "Status" field are now updated in Vulnerability Finding application when Vulnerability Findings are ingested with vulnerability-finding-remediation-status set to "Closed".
Addressed Issues:
- Addressed logical error preventing caching of exports used in deduplication from refreshing as expected. Fixed in “VRM - Get Findings CSV Export” : “Evaluate Search Results” : “Not_Stale”.
- Update Case Risk Scores flow no longer times out if a large number of findings are in a Vulnerability Case.
- Vulnerability Finding max results no longer constrained at 1000 Vulnerability Findings for purposes of calculating Vulnerability Asset Max Finding Score and Open Vulnerability Count.
- EPSS scores are now rounded to 3 decimal places when returned from Swimlane Intelligence.
- CVSS scores are now rounded to 1 decimal place when returned from Swimlane Intelligence.
- Automated Grouping:
- Mapping fixes in VRM - Automate Grouping component
- Changed verbiage from "Automatic Grouping" to "Automated Grouping" as well as "Automatic Grouping and Remediation" to "Automated Grouping and Remediation" in the following locations:
- Vulnerability Case Management application
- VRM - Automate Grouping component: Highest Flow Automation block
- VRM - Case Management status now defaults to "Open" for manually created cases.
- Close Ticket button now appears on both "New" and "Open" status in Vulnerability Remediation Item application.
- vulnerability-finding-raw-json field is now enforced as a stringified JSON object