Known issues

These are cumulative release notes. If a release does not appear in this section, then there were no associated known issues.

  • Due to time differences between a user’s local time and the system UTC time, users may be able to duplicate an active existing automated workflow in the brief window before it expires.

  • If a given job adds more than 100,000 findings to an automated workflow, the system disables workflow automation instead of adding findings up to the 100,000 finding limit. (Automated workflows can only map up to 100,000 findings at a time).

  • Columns in the “Group SLAs by Due Dates” widget may currently be using the wrong operator to show findings overdue more than a certain number of days.

  • While users without Integration Control can now open the wizard for creating an automated ticketing configuration from a collection, the wizard will not load successfully for these users.
  • The custom attributes update dialogue shows numbers at the bottom near the “next” and “back” buttons. These numbers show the total number of jobs across all tabs rather than the total number of jobs that you can scroll through per tab.
  • There is a known issue with identifying findings synced through Rapid7’s InsightVM’s connector. In some cases, two or more findings could have the same uniqueness, resulting in only the last one being persisted in Neurons and others being dropped. The Ivanti Neurons team has communicated the issue to Rapid 7 and is waiting for a response.
  • To optimize on latency and resources, the Microsoft Defender for Endpoint connector is currently Implemented as a delta sync. This results in the connector only syncing the changes since its last run. The Ivanti Neurons team identified some cases where this could cause a drift between the states of findings between Ivanti Neurons and Defender. Microsoft has recommended that Ivanti Neurons runs a full sync every 15 days as a solution. Customers could see this drift for the 15 day period. If you see this scenario, you can contact support to trigger an ad hoc sync out of band.
  • You may not be able to set a new value for the API Token Expiration setting in Client Settings > Security.
  • The Application Findings and Applications detail panes still show the old icon shown for the Checkmarx ONE connector.
  • Updates to the description of a finding collection may not show up in the UI.
  • “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.