Detectors
A detector watches for a pattern across events. Identiguard has 40.
Detectors are part of automatic incidents, which is included in Super and is the Automated Identity Incidents add-on for Pro and Max.
When a detector is armed
Section titled “When a detector is armed”A detector is Armed, which means it is working, when all of these are true:
- Automatic incidents are on for the workspace.
- An admin has not switched the detector off under Incident settings.
- At least one connected tenant sends what the detector needs. For Okta and Auth0, the tenant subscribes to the needed event types. For Entra ID, the tenant subscribes to the needed streams.
- For detectors that follow an identity on Auth0: the log stream does not mask identities.
Connecting a tenant is not enough on its own. If the tenant does not subscribe to the right event types, the detector is Blocked. See When a detector cannot work.
Detectors that open an incident and detectors that add to one
Section titled “Detectors that open an incident and detectors that add to one”Most detectors can open an incident on their own. Those marked adds to an incident do not open one. They attach to an incident that is already open and raise its seriousness. Any detector hit on an incident, including one of these, escalates the incident.
Workforce: Okta and Entra ID
Section titled “Workforce: Okta and Entra ID”| Detector | What it looks for | Platforms |
|---|---|---|
| Rapid privilege grants | Four or more privilege grants to one identity within an hour. Adds to an incident. | Okta, Entra ID |
| Cluster of MFA weakenings | Three or more changes that weaken MFA for one identity within an hour | Okta, Entra ID |
| Self-granted privilege | Someone grants a privilege to themselves. PIM activation is excluded. | Okta, Entra ID |
| Factor reset by someone else, then enrolment from an unfamiliar place | A help-desk reset that turns into a takeover | Okta, Entra ID |
| One actor resetting credentials across many identities | Five or more identities within 30 minutes | Okta, Entra ID |
| Burst of security control removals | Three or more policy changes, role removals or privilege revokes by one actor within 30 minutes | Okta, Entra ID |
| Account lockouts across many identities | Five or more identities locked in one tenant within 30 minutes | Okta |
| Failed sign-in burst followed by success | Ten or more failures, then a success, within 30 minutes | Okta |
| Repeated lockouts on one identity | Three or more within 24 hours | Okta |
| Repeated Okta Verify push denials | Three or more within 30 minutes | Okta |
| Okta sign-in with a breached password | A breached-credential detection, then a success within 24 hours with no reset between | Okta |
| Sensitive change after the user reported the activity | A user reports suspicious activity and a sensitive change follows. Adds to an incident. | Okta |
| Authenticator turned off org-wide, then factor resets | Resets across three or more identities in the following 24 hours | Okta |
| Sign-on policy denials against one identity | Five or more within 30 minutes | Okta |
| One address signing in as many identities | Five or more identities from one address within an hour | Okta |
| OAuth consent followed by application credential | An application is given consent and a new credential within 4 hours. Adds to an incident. | Entra ID |
| New account granted privilege | An account created less than 24 hours earlier is given a privileged role | Entra ID |
| New service principal given a credential | Registration, then a credential, within 4 hours | Entra ID |
| Domain added then federated | Within 24 hours | Entra ID |
| Directory role granted to a service principal | An application is given a directory role | Entra ID |
| Conditional Access failures from many countries | Three or more countries within an hour | Entra ID |
| Inbox rule tampering and forwarding on one identity | Signs of business email compromise. Adds to an incident. | Entra ID |
Customer: Auth0
Section titled “Customer: Auth0”| Detector | What it looks for |
|---|---|
| Credential stuffing from one address | Failures against five or more identities with no success, within 30 minutes |
| Sign-in from a credential-stuffing address | A successful sign-in from an address already seen stuffing credentials |
| Brute force followed by success | Five or more failed passwords, then a success, within an hour |
| Sign-in with a breached password | A leaked-password warning, then a success within a day |
| MFA fatigue: rejected pushes then success | Three or more rejected pushes, then an approval, within 30 minutes |
| Second-factor guessing then a sign-in | A sign-in after a rate limit on one-time or recovery codes |
| Recovery code used after failed second factors | A recovery code follows failed MFA attempts |
| Account change straight after a sign-in from a new place | Critical when the email address or a linked account is changed |
| Blocked address unblocked, then a sign-in | All within 24 hours |
| Password reset requests across many accounts | Five or more accounts from one address within 30 minutes |
| Burst of registrations from one address | Twenty or more within 10 minutes |
| Sign-ins from two countries at once | Within 30 minutes |
| Login attempts for accounts that do not exist | Twenty or more within 10 minutes |
| Management API failures from one address | Ten or more within 10 minutes |
Across platforms
Section titled “Across platforms”| Detector | What it looks for | Platforms |
|---|---|---|
| One source address across tenants | Failures from one address in two or more tenants of the same correlation group within an hour | All |
| Baseline anomaly then a sensitive change | Unusual behaviour for an identity, followed by a sensitive change. Adds to an incident. | All |
| Privileged account deleted | A privileged account is removed | Entra ID, Auth0 |
| Many accounts deleted at once | Ten or more by one actor within 10 minutes | Entra ID, Auth0 |
Baseline anomalies
Section titled “Baseline anomalies”Baselines are not detectors, but they feed incidents. See Incidents.
When a detector cannot work
Section titled “When a detector cannot work”Each detector has a state. The state is shown as a chip.
| State | Meaning |
|---|---|
| Armed | At least one tenant sends what the detector needs. It is working. |
| Blocked | No tenant can feed it. Either a needed event type or Entra ID stream is not subscribed, or an Auth0 log stream masks identities. |
| Switched off | An admin has turned it off for the workspace |
| Not applicable | The detector does not apply here, for example because the workspace has no tenant of the platform it needs |
| Fired | Inside an incident only: the detector matched on that incident |
Where you see the states
Section titled “Where you see the states”| Place | What it shows |
|---|---|
| Incidents page, Detectors panel on the right (wide screens) | Every detector that applies, with its state chip, a hint and a count of recent detections. Detectors that can never apply are left out, and a footnote says how many. |
| Incidents page, Telemetry coverage panel | One sentence with the totals: how many detectors are evaluating, blocked or switched off |
| Dashboard, Needs attention strip | The number of armed detectors, a link when some are blocked, and the detector squares |
| An incident, What fired | Squares for the incident’s own domain. Filled squares are the detectors that fired. |
The Incident settings page does not show these states. It shows only a checkbox for each detector.
Hints on a Blocked detector
Section titled “Hints on a Blocked detector”| Hint | Cause |
|---|---|
| “Subscribe tenant to event type to evaluate detector” | An Okta or Auth0 tenant does not subscribe to the event type |
| “Subscribe tenant to any of a, b, c to evaluate detector” | The detector needs at least one of several event types, and none is subscribed |
| “Enable the name poll target on tenant to evaluate detector” | An Entra ID tenant does not subscribe to that stream |
| “Masking hides identities on tenant. Set Obscure log stream data to XXHash to evaluate detector” | The Auth0 log stream masks identities, so the detector cannot tell users apart |
How to fix a Blocked detector
Section titled “How to fix a Blocked detector”- Missing event type or stream. Open Tenants, choose Edit on the named tenant, add the event type or stream, and save. The link Fix in settings under the hint opens Incident settings, but the fix is on the tenant.
- Masked identities on Auth0. In Auth0, change Obscure log stream data on the log stream from mask to XXHash, with the client’s agreement. With XXHash the detectors work and users appear as pseudonyms, not names. With mask, the identity detectors stay blocked.
For steps, see Fix a Blocked detector.
How to fix a Switched off detector
Section titled “How to fix a Switched off detector”An admin opens Incident settings, ticks the detector under Workforce detectors or Customer detectors, and chooses Save detectors.
Troubleshooting
Section titled “Troubleshooting”| What you see | Why | What to do |
|---|---|---|
| A Blocked chip with “Subscribe tenant to …” | The tenant does not subscribe to an event type the detector needs | Edit the tenant and add the event type |
| A Blocked chip with “Enable the … poll target on tenant …” | The Entra ID tenant does not subscribe to that stream | Edit the tenant and add the stream |
| A Blocked chip with “Masking hides identities on tenant. Set Obscure log stream data to XXHash …” | The Auth0 log stream masks identities | Change the stream to XXHash in Auth0, with the client’s agreement |
| A Switched off chip with “Switched off for this workspace.” | An admin switched the detector off | Choose Turn on in settings, tick the detector and choose Save detectors |
| “N detectors not shown: they read telemetry no connected tenant sends” | The workspace has no tenant of the platform those detectors need | Nothing. Connect a tenant of that platform if you want them. |
| “N detectors not shown: they read telemetry this tenant’s provider does not send” | You filtered the Incidents page to one tenant | Set the tenant dropdown to All tenants to see all detectors |
| “N detectors not shown: they belong to the other identity domain or read telemetry no tenant here sends” | You filtered the Incidents page to one domain | Set the domain dropdown to All domains |
| “No tenants are connected yet, so no detectors are evaluating.” | The workspace has no tenants | Connect a tenant |
| A detector is Armed but never fires | Its pattern has not occurred, or the threshold in the tables above was not reached | Nothing. Check the threshold before you plan a demonstration. |
| The Detectors panel is not on the Incidents page | The panels are hidden on narrow screens | Use a wider window |