June 2026
End Users
Table State Management
We’ve introduced Table State Management across the platform to make navigating large datasets faster and more intuitive.
What’s Improved?
When working within data-heavy areas such as Issues, Assets, Projects, and other table-based views, the platform will now remember the state of the table when navigating between records.
For example, if you apply multiple filters to identify a specific set of vulnerabilities, open an issue to review its details, and then return to the table using your browser’s back button, the platform will retain your previously applied filters, sorting, and position within the dataset.
Key Benefits
Preserves filters and sorting when navigating between records
Reduces repetitive filtering when reviewing multiple assets or issues
Improves workflow efficiency for vulnerability triage and remediation activities
Available across platform tables for a more consistent user experience
This quality-of-life enhancement helps users maintain context while investigating data, making it easier to work through large result sets without constantly reapplying filters and search criteria.
Flexible Ticket Creation for Affected Instances
We’ve enhanced the ticket export workflow to provide greater flexibility when creating tickets from affected instances.
What’s New?
When selecting multiple affected instances and exporting them to a connected ticketing system such as Jira, ServiceNow, Freshdesk, TOPdesk, or any other supported integration, users can now choose how tickets are created.
The export modal now provides two options:
Create a single ticket containing all selected affected instances.
Create individual tickets for each selected affected instance.
Key Benefits
Greater control over how remediation work is assigned and tracked.
Supports both centralised and distributed remediation workflows.
Reduces the need to manually create multiple tickets for large groups of affected assets.
Consistent experience across all supported ticketing integrations.
This enhancement allows organisations to better align ticket creation with their operational processes, whether vulnerabilities are managed by a single team or distributed across multiple asset owners.
First Seen Tracking for Asset Vulnerabilities
We’ve enhanced asset-level vulnerability visibility by introducing a new First Seen column within the affected instances view.
What’s New?
When viewing vulnerabilities associated with an individual asset, users can now see both:
First Seen – when the vulnerability was first identified on that asset within the platform.
Last Seen – when the vulnerability was most recently detected.
This provides greater context around the age and persistence of vulnerabilities, helping teams better understand exposure timelines and prioritise remediation activities.
Export Enhancements
The new First Seen field has also been added to asset-level exports. When exporting affected instances from an asset, both First Seen and Last Seen dates are included in the output.
Key Benefits
Improved visibility into vulnerability lifecycle and persistence.
Better support for remediation prioritisation and reporting.
Enhanced export data for offline analysis and audit purposes.
This enhancement provides valuable historical context, helping users quickly identify long-standing vulnerabilities that may require additional attention.
