InsightAppSec Release Notes / Jun 22, 2020

Jun 22, 20202020.06.22

Bugs Fixed

  • We have fixed a minor styling bug with spacing in the scan info panel.
  • We have fixed a minor styling bug to better display long urls in the scan crawl map.
  • We have fixed a bug which was displaying incorrect counts for the All Vulnerabilities table after applying a filter.
  • We have fixed a bug that allowed read only users to visually update the vulnerability severity and status fields and click save. Though this caused an error, as per read only permissions, no data was updated.
  • We have fixed a bug where a blacked out scan was indicated as such in the scan info panel.
  • We have fixed a bug that prevented larger traffic responses from displaying correctly.
  • We have fixed a minor styling bug where the org switch was rendering over the scan info panel.
  • We have fixed a minor styling bug with the compliance reports which caused the dark background to bleed through to the foreground.
  • We have fixed a bug that caused saving a scan config to fail if the group containing the assigned engine had been deleted without reassigning the engine to another group.

New Features and Enhancements

  • We have added the DOES NOT CONTAIN operator to the vulnerability filters.
  • You can now export a scan crawl map as JavaScript Object Notation (JSON).
  • We have added two new notification options to alert you when a running scan has completed and in the event that an on-premises scan engine has failed to automatically upgrade. Check your Notification Preferences to begin receiving these update emails.
  • We have added network speed units to the running scan screen.
  • We have released Version 7.2.122 of the scan engine. Click here to see the full engine release notes.
  • We have added Chrome 79 to the user agent list.
  • The vulnerability drawer now includes a new Vulnerability History section that will show when the vuln severity and/or status fields were changed and by whom.
  • Dashboard bar charts now support deeplinking so you review the data used to populate the chart.
  • We have enhanced the pre-save field validation checks when creating and editing Jira server details.