Severity and risk rating
Every event has a severity, which is stored with the event, and a risk rating from 1 to 5, which the feed works out when it shows the event.
Severity
Section titled “Severity”Every event has one of five severities.
| Severity | Risk rating | Meaning |
|---|---|---|
DEBUG |
1 | Diagnostic detail |
INFO |
1 | Routine activity |
WARN |
3 | Worth a look |
ERROR |
4 | Something failed or was denied |
CRITICAL |
5 | Needs attention now |
An event with a severity Identiguard does not recognise is rated 3.
No severity maps to a rating of 2. A rating of 2 appears only when a priority rule set gives an event type that score.
Where the severity comes from
Section titled “Where the severity comes from”- The provider’s own severity, where the provider gives one.
- Otherwise, Identiguard’s baseline for that event type.
Entra ID risk levels are mapped onto the same scale when events arrive. High risk becomes ERROR.
Identiguard does not store a severity called HIGH. When you ask Alex or an AI client for “high” severity events, it looks for ERROR.
The risk rating in the feed
Section titled “The risk rating in the feed”The Risk Rating column of the event feed shows the rating as {n}/5 beside a coloured dot.
| Rating | Colour |
|---|---|
| 1 | Green |
| 2 | Lime |
| 3 | Orange |
| 4 | Red |
| 5 | Purple |
The legend above the table reads Risk Rating: 1 2 3 4 5 (1: Low Risk, 5: High Risk).
Your own priorities
Section titled “Your own priorities”A priority rule set gives an event type an importance that you choose, from 1 to 5, for the tenants that you choose. For a matching event, your importance replaces the risk rating.
What changes for a matching event:
- The row has a coloured left border.
- Risk Rating shows your score as
{n}/5with a small flag icon. Hover over the flag to read Priority set by rule set {name}. Screen readers announce “Priority {n} of 5, set by rule set {name}”. - Event Details shows Analyst priority as {n}/5 set by rule set {name}.
- Sorting by Risk Rating uses your score.
- Flagged only shows the event.
- Alex and AI clients are given the same score.
What does not change:
- The Severity column still shows the provider’s severity.
- The stored event and its stored severity are not changed.
- Alert channels still use severity. A priority does not change which alerts are sent.
- Incident scoring still uses severity.
A rule works in both directions. It can raise an INFO event to 5, and it can lower a CRITICAL event to 1.
Where severity is used
Section titled “Where severity is used”- The Severity column and its sort order in the event feed.
- The Risk Rating column, unless a priority rule set matched the event.
- The severity label on each tenant card on the dashboard: Critical, Error, Warning or Info.
- The Minimum severity of each alert channel.
- Incident scoring. A
CRITICALevent escalates its incident. - A ServiceNow incident raised from an event. See Raise a ticket from an event.
Incident and finding ratings
Section titled “Incident and finding ratings”These are separate from event severity.
- An incident has a score built from several factors. See Incidents.
- A finding on the Correlations page is rated high, medium or low.
Troubleshooting
Section titled “Troubleshooting”| What you see | Why | What to do |
|---|---|---|
| Risk Rating does not match Severity, and the row has a flag | A priority rule set matched the event | Hover over the flag to see which rule set. See Event priorities. |
A CRITICAL event shows a low rating |
A rule set gave that event type a low importance | An admin edits or deletes the rule set |
| A rating of 3 on an event with an unusual severity | Identiguard did not recognise the severity | Nothing. 3 is the default. |
| A new rule set does not change the ratings | Open feeds load rule sets only on reload or when the browser tab is shown again | Reload the dashboard |
| An event that you scored 5 did not send an alert | Alert channels filter on severity, not on your priority | Lower the channel’s Minimum severity. See Alert channels. |