Investigate an incident
This guide follows an analyst from an escalated incident to a decision. It takes about ten minutes for a typical incident.
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.
- Any role to read the incident and use Ask Alex. The member or admin role to close it.
- For a ticket: a ServiceNow connection. See Raise a ticket.
1. Open the incident
Section titled “1. Open the incident”- On the dashboard, look at Needs attention, or open Incidents and choose the Escalated tab.
- Open the incident with the highest score.
You should see the incident page, with the title, a row of chips, then Attack story, What fired and Evidence.
2. Read the story
Section titled “2. Read the story”- Read the line under the title. It gives the kind of entity (Identity, IP address or Tenant), the entity and the tenants.
- Select Score N in the row of chips to open How this score is built. It shows the points for each part of the score.
- Read Attack story. The tinted, numbered stages show how far the activity has gone and when each stage was first seen. An incident that has reached Privilege grant or Persistence is more urgent than one still at Credential access.
- Read What fired. Each card is a detector, with the numbers that made it match, or a baseline anomaly, with the badge new for this identity. Hover the squares to see which detectors were armed but did not fire.
3. Check the evidence
Section titled “3. Check the evidence”- In Evidence, find the row marked Trigger. The list is oldest first, 10 rows per page. Use the page control to move through it.
- Read the events before and after it. Look at the actor, the IP address and country, and the tenant.
- Note any rows marked Baseline anomaly. They show what is unusual for this identity.
- If Related incidents is shown, open each one. They share an identity or an address with this incident.
Ask yourself: is this the person, or someone using their account?
Back to incidents returns you to the same tab and page of the list.
4. Ask Alex
Section titled “4. Ask Alex”- Choose Ask Alex AI in the header. The panel opens and asks for an explanation of the whole incident: what happened, why it opened, how the score was reached and what to do next.
- To ask about one detection, choose Ask Alex AI on its card under What fired. The panel asks why that detector or baseline anomaly fired.
- Ask follow-up questions in the panel. They stay on this incident. For example: “What should I check first?”
Use the answer as a starting point and check it against the evidence. Viewers can use Ask Alex too.
5. Go from the evidence to the event
Section titled “5. Go from the evidence to the event”Evidence rows on the incident page are not links and have no actions. To explore correlations, open the Okta log or raise a ticket, find the event in the dashboard feed.
- In Evidence, note the event type, the actor, the time and the IP address of the event you care about.
- Open Dashboard and go to Real-time events.
- Find the event. Type the event type in Search event types…, filter by the tenant, and set From and To around the time.
- Choose View on the row to open Event Details.
You should see Event Details for the same event, with the actions used in the next steps.
6. See who else is involved
Section titled “6. See who else is involved”- In Event Details, choose Explore correlations.
- In the graph, select the IP address and choose Focus.
- Check whether other identities used the same address in the same period.
- Read Findings for the same scope.
You can also open Correlations from the sidebar and set the scope, the time range and a filter by hand. See Run a correlation.
7. Check the source
Section titled “7. Check the source”For an Okta event, choose View in Okta in Event Details to see the entry in the Okta system log. For the other platforms, use the event ID in the raw payload.
8. Act
Section titled “8. Act”Identiguard does not change anything in the identity platform. Depending on what you found:
- Ask the user whether the activity was theirs.
- Reset the user’s credentials or sessions in the identity platform.
- Choose Raise Ticket in Event Details to hand the event to another team in ServiceNow. See Raise a ticket.
9. Close the incident
Section titled “9. Close the incident”- Return to the incident and choose Close incident.
- Choose the reason that fits:
- Resolved: it was real and has been dealt with.
- Benign activity: it happened, and it was legitimate.
- False positive: the detection was wrong.
- Optional: if you chose False positive, the incident involves one tenant, and this pattern will keep recurring there, tick Silence incidents like this on tenant name.
- Choose Close incident.
You should see the message “Incident closed”. If the close armed a silence rule, you see “Incidents like this will now be silenced on tenant.” with Undo for 15 seconds.
Be honest with the reason. On a single-tenant incident, three False positive closes of the same pattern within 30 days teach Identiguard to silence it, when Learn from false-positive closes is on. One close with the silence box ticked does it at once. A silenced incident still opens, but it is listed on the Silenced tab, not on Open.
To reverse a close, open the incident from the Closed tab and choose Reopen incident. See Manage incidents.
If it does not work
Section titled “If it does not work”| What you see | Why | What to do |
|---|---|---|
| Incidents and Needs attention are missing | Automatic incidents are off, or not in the plan | See Manage incidents |
| Nothing happens when you select an evidence row | Evidence rows have no actions | Follow step 5 |
| You cannot find the event in Real-time events | The event is older than the workspace’s retention, or a filter hides it | Clear the filters and widen From and To. If the row said “Raw event no longer stored”, the event is gone. |
| There is no View in Okta action | The event is not from Okta | Use the event ID in the raw payload |
| “No detector or baseline hits. This incident is built from vendor signals and direct evidence.” | The incident opened from a provider risk signal | This is normal. Read the evidence. |
| “Viewers can read incidents but not close them” | You have the viewer role | Ask a member or admin to close it |
| 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. |
| Could not load this incident | The request failed | Choose Retry |
More messages are listed under Incidents.