Version 14.09.00 Release Notes

Summary: A high-level overview of the changes/updates included in Ivanti Neurons Version 14.09.00, released on March 1, 2024.

The platform version 14.09.00 update includes the following features and enhancements:

• New Features
• Integrations
• Miscellaneous changes
• Fixed Issues
• Known Issues

For assistance with using our new features, receiving feature documentation, and/or scheduling training, please contact your Customer Success account manager directly or contact Ivanti support.

New Features

• Finding Collections and Jira Ticketing Automation - “Collections” within the Ivanti Neurons platform empowers users to categorize and arrange data according to defined criteria. This capability is readily available on the Host Findings and Application Findings pages, streamlining the process for users to seamlessly generate and oversee collections of findings. Initially, finding collections will only enable automated ticketing for the Jira ticketing connector. Future updates to this feature will extend automated ticketing to other connectors. For further information, please refer to the Knowledge Base article on Collections.

Integrations

• Enhanced Keyword Search for Integrations - Users can now search for common aliases associated with some integrations in addition to the full product name listed on the product card.
• Incremental Scan Indicators - Users can now identify incremental scanners by interacting with new icons on the cards for eligible connectors.
• Qualys VMDR Unique Vuln ID - The new scanner-specific field “Scanner Reported Unique Vuln ID” has been added for the Qualys VMDR integration. Users will be able to filter or group host findings, add the field as a column to the Host Findings page, or add it to the Host Findings export.

Miscellaneous Changes

• Users can now add the field Automation Stop Date to a Workflows page export.
• The privilege “Patch Core Read” has become part of the more general “Core Read” privilege. As every role (including custom roles) inherits Core Read automatically, this change should have no impact on the functionality of existing roles.
• On the Client Settings page, users will no longer see an option to configure email notifications for finding due dates. (Note that this client configuration predates the newer Notifications feature.)
• Users will now be directed to a meaningful error page if they receive a download notification via email and use that download link to navigate to the platform while logged out.

Fixed Issues

• Users can now successfully submit a new configuration for the Cherwell Service Management ticketing connector.
• New safeguards have been put in place to prevent users from having issues with creating automated workflows after previous job failures.
• Users will no longer see a blank row when doing a Group By on the Application Findings field “Location.”
• The Tenable.SC v2 connector will now ingest new assets correctly.
• Users with only the Integration Read privilege should now be able to create ITSM tickets.
• Within the Finding Details, the Tickets section header will now correctly show the number of tickets associated with the finding.
• The system should update SLAs for findings as expected on clients that regularly create or delete groups.

Known Issues

• In the findings collections auto configuration wizard,
  • The export template for attachments will not be accessible from the parent connector, and default templates will always be provided.
  • The configured Closed Status is not functioning as intended; instead, it adheres to the configuration of the parent connector.
  • The configured fields for description are not being updated in the JIRA comments when there are changes or updates in the findings.

• Although a user with C-Level Observer lacks the privileges to create a Finding Collection, that user can still open corresponding dialogues for creating one or associating it with a ticketing connector.

• The privileges necessary to create and manage finding collections will change in a subsequent release. Those privileges will be part of most foundational roles.