Skip to main content
Control and respond

Incident rules

An incident rule opens incidents for you. You say what it watches (findings, alerts or AI activity), narrow it with filters, and choose whether matches join the incident that is already open or start…

Written By Christopher Scaminaci

Last updated 16 days ago

An incident rule opens incidents for you. You say what it watches (findings, alerts or AI activity), narrow it with filters, and choose whether matches join the incident that is already open or start a new incident each time. This page covers how to write a rule, what each choice does, and what the rule will and will not do on its own.

At a glance

  • What it does: opens incidents automatically, to your own specification, from findings, alerts or AI activity.
  • Plan: Business and above. After a downgrade, your rules stay readable and stop opening incidents until the plan is back.
  • Who: an Administrator writes, changes, switches and deletes rules. Every governance role reads them.
  • Where: AI Governance → Alerts → Incident rules.
  • Needs: nothing to start.

Write a rule

  1. Open Alerts → Incident rules and select New rule.
  2. Give it a Name, and choose whether it applies to This organization or Every organization the tenant governs. A rule for every organization needs an administrator who is not limited to some organizations.
  3. Choose what it Watches: Findings, Alerts or AI activity.
  4. Set the filters. Leave a list empty for "any".
  5. Set the count and the window, choose how it groups matches, and choose the incident's type, severity, owner and title.
  6. Select Preview the last 7 days, then Add rule.

The filters

The filters that apply depend on what the rule watches. Choices that do not apply are not shown, and a rule that names one is refused when you save it, so a rule never sits on while it can never match.

WatchesWhat you can narrow by
FindingsLowest severity, rule packs, data-loss rules, only findings of rules that are Live.
AlertsLowest severity, kinds of alert, particular alerts, and for sensitive-content alerts the rule and pack.
AI activityThe kind of activity, its outcome (for example Refused) and the provider.

All three can also be narrowed to particular people or applications, clients and sources. A rule never matches an item that has none of what a list asks for. A test alert never matches, and neither does the alert of an incident: otherwise an incident could open incidents without end.

How many matches it takes

A count of 1 acts on every match. A higher count, for example 3 within 60 minutes, acts only when that many matches fall inside the window. Matches that did not reach the count wait, and count again while they are inside the window.

Add to the open incident, or a new one each time

  • Add to the open incident keeps one incident open for each group and adds every new match to it. The group is the whole rule, or one per person, or one per client, as you choose. When that incident is Resolved or Closed, the next match opens a new one.
  • Open a new incident each time opens one incident for every match, or for every burst of matches when the count is above 1.

A match joins only one incident of a rule. Matches are never linked twice.

What the incident looks like

  • The title comes from your template. Use for the rule's name, for what matched (the data-loss rule, the kind of alert or of activity), for finding, alert or activity, and for how many matches opened it. No token names a person or a client.
  • The severity is the one you choose, or the highest severity among the matches.
  • It opens with no GDPR or NIS2 clock. A rule matching is not the decision that a breach happened. You switch a clock on when you decide, and set when you became aware.
  • Each match is a link on the incident: a finding, an alert or an activity record.

The daily limit

An organization's rules open at most 50 incidents in a UTC day, counting incidents opened by a data-loss rule too. After that, further matches join one overflow incident for the day, the same one a data-loss rule uses. A match that belongs to an incident that is already open is still added to it. Nothing is dropped, and a rule that is too broad cannot flood the register.

Try it first

Preview the last 7 days counts what the rule would have matched in this organization and how many incidents it would have opened. It assumes nobody closes an incident meanwhile and ignores the daily limit. It writes nothing.

What you will see

  • Each rule with what it watches, its count, how it groups matches, and whether it is on.
  • The incidents a rule opens on Alerts → Incidents, shown as opened by a rule.
  • Every change to a rule in the audit trail, with the names of the fields that changed and never their values.

Good to know

  • A rule starts from the moment it is on. It does not look back through history.
  • A rule that is switched off, or deleted, opens nothing. Incidents it already opened stay.
  • A data-loss rule whose action is Open an incident still works on its own. Incident rules are separate and can overlap with it.

Troubleshooting

What you seeWhat to do
The page says it needs BusinessIncident rules need the Business plan or above. Rules you saved stay here.
A save says the filter is not valid for this kind of ruleRemove the choices that do not apply to what the rule watches.
A save says someone changed the ruleReload the rule and make your change again.
A rule opens nothingCheck that it is on, that its filters are not too narrow, and use Preview the last 7 days.

Next