Product news

2025-07-16: Remediation and Device Agent updates keep your workflow efficient

Enhancements to the new remediation 

When creating a ticket, you’ll now see a direct link to the ticket in the confirmation message. This small but impactful enhancement allows you to jump straight into the ticket you just created, saving time and keeping your workflow efficient. 

In the next product release, we will add additional permission settings in remediation to make it even easier to focus on your tickets across teams.  

Device Agent assets now show OS build 
OS build_july 25_product news


Device assets running on Microsoft Windows now display the OS build number in additional views in Security Center, such as in Unified Assets. This makes it easier to track patch levels and system versions at a glance. 

Device Agent tracking settings 

You can now define which email addresses the Device Agent is allowed to track, ensuring that only approved company emails are included in Security Center.

Contact Support with the email addresses you wish to track so they can make that change in your account.

Want to get started with the Device Agent?

If you're not already using the Device Agent, you can get started by reaching out to your Customer Success Manager.

Additional enhancements  

  • We have enhanced our platform API to allow filtering on the Device Agent version across your assets. 
  • The “Keep me logged in” option has been improved with a more generous session time out, allowing you to stay logged in longer.  
  • Adding tags directly from a web application asset now works properly.  
  • We solved an issue with the Microsoft Azure Sentinel integration thanks to a customer of ours. 
  • Integrations to ticketing systems are now properly linking back to the new remediation.  
  • Web scans now include a new informational HID that can give you additional guidance on how to split up the scan in additional URLs to improve the scanning in parallel.  
  • Previously, scan schedules may not have updated due to outdated tags. This has now been corrected.