Version 14.24.00 Release Notes

Summary: A high-level overview of the changes/updates included in Ivanti Neurons for RBVM, ASOC, and Vulnerability KB version 14.2400, released on October 4, 2024.

Release version 14.24.00 of Ivanti Neurons for RBVM, ASOC, and Vulnerability KB includes the following:

• Integrations

• Miscellaneous Changes

• Fixed Issues

• Notices

For assistance with using our new features, receiving feature documentation, and/or scheduling training, please contact support through the Ivanti Success Portal.

Integrations

SNOW Priority Synchronization - Service Now Incident tickets can now be configured to set the ticket priority based on the criticality of the findings associated. Users can map the Critical, High, Medium, Low, and Informational VRR score or Severity for the findings to the desired SNOW ticket priority. Adopting ticket prioritization can help organizations ensure the most critical findings are worked first.

Miscellaneous Changes

• The Wiz finding filter options UI on the configuration form has been updated.
• Quick Filters will now load after the list view. When the Quick Filters load, they will expand to show available options. This change in load order will improve the initial responsiveness of our list views.

Fixed Issues

• An issue was resolved with the Cherwell ticket creation caused by customized Category and Subcategory field names.
• Application finding counts will now be correct for Fortify On Demand DAST and SAST findings.
• An issue has been resolved with the calculation of SLA dates for application findings caused by a previous job failure.
• Cherwell tickets will no longer be created with <br> tags.
• Column order will successfully be saved when a saved view is updated.

Notices

• MS Teams has been removed as an available notification delivery channel. This change has no impact on existing MS Teams delivery channels.
• Customers creating tickets with attachments must grant the configured ticketing service account privileges to delete attachments. Refer to your ticketing vendor’s documentation to select the appropriate role based on your organization's setup. This is to ensure a successful transition to the upcoming feature that synchronizes status updates to ticket attachments.
• Users with API authorization tokens will now have a subscription to the API Token Expiration in platform notification. By default, the platform will send one notification for an expiring token 14 days before the expiration date and another after the token expires. Users can configure the system to send the messages through a different delivery channel or disable the notification configuration.