Manage incidents
This guide covers the everyday tasks on incidents. Each task has its own heading. For a full description of the screens, see Incidents and Incident settings.
You need
Section titled “You need”- A workspace with automatic incidents: the Super plan, or Pro or Max with the Automated Identity Incidents add-on.
- The role for the task:
| Task | Role |
|---|---|
| Triage the list, read incidents, review the Silenced tab | Viewer, member or admin |
| Close, reopen, silence, This was real | Member or admin |
| Manage silence rules, switch incidents or a detector on or off | Admin |
| Fix a Blocked detector | Admin, to edit the tenant |
Triage the list
Section titled “Triage the list”Use this at the start of a shift to find what needs attention first.
- Open Incidents in the sidebar. It has a Beta badge. If it is missing, see Switch incidents or one detector on or off.
- Check that the dot above the list reads Live. If it reads Offline, reload the page.
- Choose the Escalated tab. The number beside it is how many incidents need attention.
- Optional: narrow the list with the All domains dropdown (Workforce or Customer) and the All tenants dropdown.
- Read down the Score N values and the attack-story pills on the right of each row. Open the incident with the highest score.
- Look at the line under the tabs. If it says “N incidents silenced by learned rules”, select it and scan the Silenced tab.
- On a wide screen, look at Identities at risk on the right. Look for people with several open incidents or the words “ - privileged”.
When it worked: you know how many incidents are escalated and you have opened the most serious one. To work it, follow Investigate an incident.
Close an incident
Section titled “Close an incident”- Open the incident and choose Close incident.
- In the reason dropdown, choose one:
- Resolved: it was real and has been dealt with.
- Benign activity: it happened, and it was legitimate.
- False positive: the detection was wrong.
- Choose Close incident.
When it worked: you see the message “Incident closed”. The incident moves to the Closed tab.
Reopen an incident
Section titled “Reopen an incident”There is no undo for a close. Reopen the incident.
- Open Incidents and choose the Closed tab.
- Open the incident.
- Choose Reopen incident.
When it worked: you see the message “Incident reopened”. The incident returns to Open or Escalated, as it was before the close.
Silence a recurring false positive
Section titled “Silence a recurring false positive”Use this when the same kind of incident keeps opening on one tenant for a known, harmless reason.
- Open an incident of that kind. It must involve only one tenant.
- Choose Close incident.
- Choose the reason False positive. A checkbox appears: Silence incidents like this on tenant name.
- Tick the checkbox.
- Choose Close incident.
When it worked: you see the message “Incidents like this will now be silenced on tenant.” with a description of the rule. Undo is available for 15 seconds.
What happens next:
- Matching incidents at or below this severity are listed on the Silenced tab, not on Open. They still open, still collect evidence and can still escalate.
- Event alerts by email, Teams and other channels are not affected.
- Every workspace admin receives an email about the new rule.
Review and release silenced incidents
Section titled “Review and release silenced incidents”Do this regularly. A silence rule can hide a real problem.
- Open Incidents and choose the Silenced tab. You can also select the line “N incidents silenced by learned rules” under the tabs.
- Hover the Silenced chip on a row to read the rule that is hiding it.
- Open any incident that looks unusual and read it.
- If an incident is a real problem, choose This was real on its row, or on the banner inside the incident.
When it worked: you see “Moved to Open and the rule was retired” or “Moved to Closed and the rule was retired”. Inside an incident the message is “No longer silenced, and the rule was retired”.
Manage silence rules
Section titled “Manage silence rules”Admin only.
- Open Incident settings under Workspace.
- Go to the Learned dismissals card and read the Silence rules table. The columns are Pattern, Tenant, Armed, Hits, Break-outs and State.
- Look for armed rules with many break-outs. A break-out means a silenced incident grew past what the rule learned. Such a rule is probably too broad.
- To stop a rule, choose Disarm on its row. In the dialog Disarm this rule?, choose Disarm rule.
- To stop all learning and silencing, untick Learn from false-positive closes. It saves at once. The rules are kept.
When it worked: after a disarm you see “Rule disarmed. Incidents it was silencing are back in the normal lists.” The rule stays in the table with the state Disarmed. After you untick the checkbox you see “Learned dismissal off”.
Switch incidents or one detector on or off
Section titled “Switch incidents or one detector on or off”Admin only.
- Open Incident settings under Workspace.
- On the Automatic incidents card, read the first line. If it says “Not available on the current plan.”, choose Manage plan. The workspace needs Super or the add-on first.
- To switch all incidents on or off, tick or untick Enable automatic incidents for this workspace.
- To switch one detector off, untick it under Workforce detectors or Customer detectors. Tick it to switch it on again.
- Choose Save detectors. Nothing is saved until you do.
When it worked: you see the message “Detectors saved”. The footer of the card reads “All detectors on.” or, for example, “1 detector switched off.” If you switched the master switch on, Incidents appears in the sidebar after a reload.
Fix a Blocked detector
Section titled “Fix a Blocked detector”A Blocked detector cannot work because no tenant sends it the data it needs.
- Open Incidents on a wide screen and select Detectors in the panels on the right.
- Find the rows with the Blocked chip and read the hint under each.
- If the hint says “Subscribe tenant to …” or “Enable the … poll target on tenant …”: open Tenants, choose Edit on that tenant, add the named event type or stream, and save. See Change event subscriptions.
- If the hint says “Masking hides identities on tenant. Set Obscure log stream data to XXHash …”: in the Auth0 dashboard, change Obscure log stream data on the log stream to XXHash. Agree this with the client first. See Auth0.
- Reload Incidents and open Detectors again.
When it worked: the chip reads Armed, and the Telemetry coverage sentence counts one more detector as evaluating.
If it does not work
Section titled “If it does not work”| What you see | Why | What to do |
|---|---|---|
| Incidents is missing from the sidebar | The workspace is not entitled, or the master switch is off | Follow Switch incidents or one detector on or off |
| “Viewers can read incidents but not close them” | You have the viewer role | Ask an admin to change your role to member |
| The silence checkbox does not appear | The reason is not False positive, or the incident involves more than one tenant | Choose False positive. An incident across several tenants cannot be silenced. |
| “Request failed (400)” when you close with the tick | The incident is too old to teach a rule | Close it without the tick and silence a newer incident of the same kind |
| “Could not close this incident.” or “Could not reopen this incident.” | The request failed | Try again. Check your connection. |
| You armed a rule by mistake and the Undo message has gone | The message stays for 15 seconds only | An admin disarms the rule. See Manage silence rules. |
| “Could not release this incident.” | This was real failed | Try again. Check that you are a member or admin. |
| “Could not disarm the rule.” | The disarm failed, or the rule no longer exists | Reload the page and try again |
| A 403 page when you open Incident settings | You are not an admin | Ask an admin |
| “Could not save detectors.” | The save failed. Nothing changed. | Try again |
| The detector is still Blocked after you edited the tenant | Another needed event type is missing, or the page is not reloaded | Reload Incidents and read the hint again |
| The Detectors panel is not on the page | The panels are hidden on narrow screens | Use a wider window |
More messages are listed under Incidents and Incident settings.