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