Version 14.22.00 Release Notes
Summary: A high-level overview of the changes/updates included in Ivanti Neurons for RBVM, ASOC, and Vulnerability KB version 14.22.00, released on September 6, 2024.
Release version 14.22.00 of Ivanti Neurons for RBVM, ASOC, and Vulnerability KB includes the following:
For assistance with using our new features, receiving feature documentation, and/or scheduling training, please contact support through the Ivanti Success Portal.
List View Enhancements
- Changes to Remediation Time filter - The Remediation Time filter shows the number of days between First Ingested On and Resolved On for closed findings. This release introduces the new filter “Remediation Time based on Discovery”, which shows the time difference between First Discovered On and Resolved On. The older filter has been renamed to Remediation Time based on Ingestion.
- New Case Sensitive Search Option - For the operators “exactly”, “wildcard”, “like”, and “is one of”, users can check a box to make a filter case sensitive. They can save this new setting as part of a view, widget, or finding collection. The platform will automatically turn on case sensitive search if a user applies filters by clicking a column in a Group By or if a filter value contains more than 1000 characters.
- Filters enhanced with counts and read-only search - The filter pill now shows a count of values in the filter rather than actual value. Users can open up a read-only view of all values by clicking the “info” icon that appears on interaction with an advanced filter. The read-only view of the filter lets users search on individual values. Note that the “info” view of a filter is not available for Quick Filters.
Dashboards and Reporting Enhancements
- Widget Group Selection - The “Findings First Ingested vs Resolved” and “Findings Summary” widgets can now filter on specific groups. This feature allows users to place multiple instances of the same widget side by side to compare results for individual groups or sets of related groups.
- First Discovered On added for Remediation Metrics - This release includes new versions of a bar widget and two KPIs that show the metric mean time to remediate. These include the KPI and bar chart “Mean Time to Remediate Since Discovery” and the KPI “MTTR since discovery for findings under SLA”. Unlike the versions based on ingestion, these widgets only include findings with a First Discovered On date, a value that only some scanners supply. Like the Remediation Time filter, the existing widgets based on First Ingested On have been renamed to reflect the source data.
Miscellaneous Changes
- Users uploading data from EdgeScan will now be presented with Mixed networks only.
- The configuration card for the legacy Palo Alto Expander connector will be removed.
Fixed Issues
- MetricStream tickets will now be created with a status of “Save and Continue” to enable editing.
- Workflow Automation Disabled email notifications will display the name of the workflow correctly.
- The date displayed on the Generate API Token window and in the API token table will now match.
- Users can now successfully update approved workflows to halt automation.
- Cards for rejected workflows, which cannot expire, will no longer show the expiration clock icon.
- An issue with question marks appearing in Cherwell ticket fields has been resolved.
- The platform will correctly translate the status of Qualys Policy Compliance findings to Open or Closed for findings in Ivanti Neurons.
Known Issues
- “Findings First Ingested On vs. Resolved” and “Findings Summary” will ignore dashboard-level filters for this release. In a future release, the default behavior for these widgets will be to accept dashboard filters until a user configures them to filter on specific groups.
- The preview for the “Mean time to remediate since discovery” KPI asserts that the widget uses ingestion as the starting point for calculating remediation time.
Notices
- Users will no longer be able to create delivery channels for Microsoft Teams after the first release of October. (This decision takes into account a couple of factors, including discontinuation of support for Office 365 webhooks.)