Incident Tuning

The Incident Tuning page allows you to view and manage incident tuning rules that determine how detections contribute to incident creation. These rules do not control whether a detection is created. For more information about native detection creation, see Native Detections.

Choose Administration > Incident Tuning in the navigation menu to view and manage incident tuning rules.

Cisco XDR evaluates rules from top to bottom for each ingested detection, starting with the Exclude tab and then the Include tab. Evaluation stops when the first matching rule sets the incident action.

Incident action determines how the detection contributes to incident creation under the applied incident tuning rule:

  • Promote - Indicates that the detection is always added to an incident. If a detection has no related detections, Cisco XDR creates an incident with this detection alone.

  • Exclude - Indicates that a rule prevents this detection from appearing in incidents.

  • Context - Indicates that the detection may be added to an incident to provide additional context. Cisco XDR does not create an incident for detections marked Context alone.

Rules do not apply retroactively, but Cisco XDR evaluates them again whenever the source updates a detection.

The tables in the Exclude and Include tabs display the evaluation order, enabled status, rule name, incident action, detection sources, author, and active-until date for each rule. Rules are evaluated from the lowest order number to the highest.

Using the Exclude and Include tabs, you can view rule details and create rules. You can also edit, enable or disable, and delete organization-defined rules. Cisco-managed rules are read-only and cannot be changed.