Identity Threat Hunting
Hunt for suspicious authentication, privilege use, consent, session, and recovery behavior.
On this page · 4 sections
Operating context
Identity hunts connect user baselines, device trust, authentication strength, session context, privilege changes, and resource access across providers.
- Define the security decision that identity threat hunting must support.
- Assign accountable owners, escalation paths, service levels, and privacy boundaries.
- Measure signal quality, response consistency, operational cost, and improvement over time.
Operational workflow
- 01
Establish scope, dependencies, normal behavior, and a documented baseline.
- 02
Collect the minimum telemetry and context needed for identity threat hunting.
- 03
Correlate independent signals and state confidence before taking disruptive action.
- 04
Document the decision, evidence, containment or control action, and responsible owner.
- 05
Review the outcome, tune the process, and validate the improvement with a safe test.
Signals, evidence & decisions
| Signal or artifact | Decision it supports |
|---|---|
| authentication and session events | Establish event sequence and affected scope. |
| privilege, consent, and recovery changes | Confirm identity, asset, or control context. |
| device, network, and resource context | Support containment, recovery, or tuning. |
Record source, timestamp, collection method, confidence, owner, and disposition. Preserve the smallest useful evidence set and document any uncertainty.
Implementation & improvement
- Model service and human identities separately.
- Account for travel, automation, and proxy behavior.
- Prioritize high-impact identities and unusual control changes.