Auto-Incident Rules

Build rules that open an incident on their own when a connector event matches conditions you have set — so a known signal becomes a tracked incident without anyone watching a feed.

An auto-incident rule (a saved set of match conditions plus a template for the incident it should raise) sits between your connectors and the Incidents module. When a connector delivers an event — a cloud-security detection, an endpoint alert, a webhook (a message one system pushes to another) — Aegis checks it against every enabled rule, and a match creates an incident from the title, severity, category and tags you chose. This page is where you create, edit, test, enable, disable and delete those rules.

Rules are tenant-level configuration, so the page sits behind the settings permission — and because a broad rule can open many incidents quickly, each rule carries its own deduplication, rate-limit and cooldown controls.

Who uses it

The page belongs to the Incidents module. If that module is not provisioned for your organisation the menu entry is hidden, and typing the address in does not help: the rules API refuses the request, so no rules load. Settings shows which modules you have.

What's on this screen

The page is headed Auto-Incident Rules, with the line "Automatically create incidents from connector events using condition-based rules." beneath it. On the right sits Create Rule, the only way to start a new rule. Below that is a single-row filter bar: a Search rules... box with a Search button, and an All Statuses dropdown that narrows the list to Enabled or Disabled rules.

Everything below is the rules table. It shows Rule Name and Trigger Type as plain text, Incident Severity and Status as coloured pills, then Actions with a per-row Disable link on an enabled rule (or Enable on a disabled one) and a red Delete link. A long rule name is cut short with an ellipsis. Clicking elsewhere on a row opens it for editing. Rules are listed in priority order — lowest number first, newest first among equals — so the table reads in the order Aegis evaluates them.

Trigger types and severities appear as readable labels — Connector event, Threshold breach, Critical, High — with severity coloured red for Critical, orange for High, amber for Medium and grey for Low. A rule whose severity is taken from the event shows its template instead, such as {{data.severity}}, in an amber pill (see "Severity from the event" below). Under the table a footer counts the rules — "Showing 1 to 10 of 10 auto-incident rules" on the captured screen — with Previous, page number and Next buttons; the list pages at twenty rows.

The captured screen shows the demo organisation's ten rules: seven enabled and three disabled, covering connector events, webhooks, threshold breaches, a weekly schedule and an AI-analysis pilot. On a tenant with no rules yet, the table area shows an empty state — "Nothing here yet" — until the first rule is saved.

To find a rule, type into the Search rules... box under the heading — not the Search... box in the top bar, which searches the whole application. The list narrows after a short pause to rules whose name or description contains the text; Search applies it at once. Pair it with the All Statuses dropdown to show only enabled or only disabled rules.

  1. Open SECURITY INCIDENTS in the left menu and choose Auto-Incident Rules. The group expands to show Incidents, Reporting, Security Signals and Auto-Incident Rules; the last is admin-only, and Reporting needs Manager or above.
  2. The ? button in the top bar opens the in-app help for a reminder of how conditions or dedupe windows work while you build a rule.
The Auto-Incident Rules list with the demo organisation's ten rules — /incidents/auto-rules.
The Auto-Incident Rules list with the demo organisation's ten rules — /incidents/auto-rules.

Create a rule

Selecting Create Rule opens the Create Auto-Incident Rule dialog — a long, scrolling form in four parts: what the rule is, what it matches, what incident it produces, and how much noise it may make. Rule Name and Incident Title Template are required (marked with a red asterisk); miss either and a red message appears at the top while Aegis scrolls that field into view.

  1. Enter a Rule Name you will recognise in the list — the placeholder suggests "e.g. Critical CrowdStrike Alerts".
  2. Choose a Trigger Type — Connector event, AI analysis, Threshold breach, Webhook, Schedule or Manual. Connector event is the default and the only type the connector pipeline evaluates — the others are stored on the rule but reached only through the API, so a rule set to one of them will not fire from a connector.
  3. Add an optional Description, and a comma-separated Source Types list such as crowdstrike, aws-guardduty to limit the rule to those sources. Left empty, it accepts any source.
  4. Build the match in the Conditions panel (next section). Left empty, the rule matches every event that reaches it — rarely what you want.
  5. Fill in the incident template. Incident Title Template accepts placeholders in double braces, so {{data.title}} - {{data.hostname}} yields "Malware detected - srv-web-01" from the event itself. Set Incident Severity (Medium by default), and optionally Incident Category and a comma-separated Incident Tags list.
  6. Set the noise controls: tick Deduplicate matching events (unticked on a new rule), optionally name the Dedupe Fields (optional) that identify the same event — data.alertId, say — and give a Dedupe Window (seconds). Cap the rule with Max Incidents / Hour, pause it with Cooldown (minutes), and order evaluation with Priority — lower numbers run first. The Priority box shows a grey 0 as its placeholder, but a blank box stores 50, the middle of the 0–100 range the server accepts.
  7. Leave Rule enabled ticked to start it straight away, or clear it to save the rule dormant. Select Create Rule at the foot of the dialog: it closes and the new rule appears in the table. Cancel closes it without saving.
Scope a new rule narrowly before you widen it

A rule with no conditions, no source types and no deduplication acts on everything that reaches it. Start tight — one or two conditions, a dedupe window, a sensible Max Incidents / Hour — then loosen it once you have watched it work.

Build the conditions

The Conditions panel is a visual builder, not a text box. It opens as one blue AND group labelled "All must match" holding a single empty row; switch the group dropdown to OR and it turns orange and reads "Any can match". Reset beside the panel heading clears the tree back to one empty group, and the line beneath it repeats the warning: leave it empty and every event matches.

  1. Click the field box in a row. A suggestion list drops down with common event paths — severity, data.hostname, data.title, data.technique, sourceType and more — each described. Pick one, or type your own dotted path.
  2. Choose the operator: equals, contains, starts with, greater than, in list, matches regex, is empty and the rest. The value box adapts — in list takes a comma-separated list, is empty hides it.
  3. Enter the value, then use Add Condition for another row in the same group, or Add AND Group / Add OR Group to nest a sub-group — that is how you express "this and that, or the other thing". The small NOT button inverts a row, and the × icon removes it.

Edit a rule and test it

Clicking a row opens the same dialog headed Edit Auto-Incident Rule, pre-filled and with one panel create mode lacks: Test Rule. It evaluates the saved rule against a sample event and reports what would have happened, creating nothing.

  1. Click the rule's row. The dialog opens with every field populated; change what you need.
  2. Scroll to Test Rule at the foot of the form. The box starts with a worked sample event in JSON — a severity, a hostname and a title. Edit it to resemble a real one.
  3. Select Run Test. A green box reports "Matched — an incident would be created." with an Incident preview line showing the title the rule would produce, or a grey box reports "No match — no incident would be created." The test runs against the last saved version of the rule, not unsaved edits on screen, and anything that is not a JSON object is rejected before it is sent.
  4. Select Save Changes to keep your edits, or Cancel to discard them. The test result is never saved — it is a dry run only.

Enable, disable or delete a rule

  1. Select Disable on a live rule, or Enable on a dormant one. The Status pill flips and a confirmation appears — "Rule disabled" or "Rule enabled". A disabled rule stops matching but keeps every setting.
  2. Select Delete to remove a rule. A dialog headed Delete Rule names it — "Delete the rule ...? This cannot be undone." — and waits.
  3. Confirm to delete, or close the dialog to keep the rule. A "Rule deleted" confirmation appears and the row leaves the table. Incidents it already created stay in the Incidents list.

How a rule actually fires

Aegis hands a delivered connector event to a background job rather than evaluating rules on the request itself, so a busy source cannot slow the receiver down. The job checks the event against your enabled Connector event rules whose Source Types include the event's source (or are left empty), in priority order — lowest number first — and a matching rule can still be held back by its own controls, checked in this order.

Control Holds the incident back when…
Deduplicate matching events an event with the same identity already opened one inside the dedupe window. The identity comes from Dedupe Fields when set; otherwise from the source ID, the event's own id, or a fingerprint of the whole event.
Max Incidents / Hour the rule has already opened that many in the past hour.
Cooldown (minutes) the rule is still waiting after the incident it last created.

Two other sources feed the same rules directly. Microsoft Purview data-loss events (see Data Loss) are checked only against rules that name purview in Source Types — a catch-all rule with no source types is skipped for them — and the first rule that creates an incident stops the evaluation, so one event yields at most one incident. Changes found between Microsoft Entra ID directory snapshots are checked as connector events with the source entraid.

Severity from the event

A rule's severity does not have to be fixed. A rule created outside this dialog — through the API, for example — can store a template such as {{data.severity}}, as two webhook rules on the captured screen do; when it fires, Aegis reads the event's value and maps critical, high, medium or low — or a 1–5 score, where 5 is Critical, 4 High, 3 Medium and 1–2 Low — to the incident severity. Anything it cannot read becomes Medium. The dialog's Incident Severity dropdown offers only the four fixed levels, so it cannot display a template: on such a rule, choosing a level replaces the template with that fixed severity.

Tips and limits

Where this connects