liveBook · Manning

Incident settings

As explained in Azure Security

Configuration that determines whether alerts from a detection rule generate Microsoft Sentinel incidents and how those alerts are grouped.

Incident settings determine whether alerts from a detection rule generate Microsoft Sentinel incidents and how those alerts are grouped. They form one stage of the scheduled-rule configuration workflow, alongside general details, rule logic, and automated response. section 8.4.4

Configure incident settings after defining the rule’s purpose and detection logic. This separates the condition that produces an alert from the operational decision to create and organize incidents for investigation. section 8.4.4

Brute-force login detection

A scheduled rule detects more than 10 failed logins within five minutes, a pattern associated with a possible brute-force attack. Incident settings determine how resulting alerts become Sentinel incidents and whether related alerts are grouped. section 8.4.4

How Azure Security covers it

How deep it goes
Places incident settings in a four-part wizard but does not detail their individual options.
Examples
Uses a rule detecting more than 10 failed logins in five minutes as the operational scenario.
What you can do after
Configure how scheduled-rule alerts create and group Microsoft Sentinel incidents.
How it connects
Connects scheduled rules, alerts, incidents, rule logic, and automated response.

This explainer was generated by Manning's knowledge graph from the text of Azure Security. The section links point to the parts of the book it draws on.