Multiple Device Token Hashes for Single Okta Session
This rule detects when a specific Okta actor has multiple device token hashes and multiple source IPs for a single Okta session. This may indicate an authenticated session has been hijacked or replayed from a…
Description
This rule detects when a specific Okta actor has multiple device token hashes and multiple source IPs for a single Okta session. This may indicate an authenticated session has been hijacked or replayed from a different device and network. Adversaries may steal session cookies or tokens to gain unauthorized access to Okta admin console, applications, tenants, or other resources.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersIaaSIdentity ProviderLinuxmacOSOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| developer.okta.com/docs/reference/api/event-types/ | 56from 2 sources |
| developer.okta.com/docs/reference/api/system-log/ | 54from 2 sources |
| sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection | 17from 2 sources |
| support.okta.com/help/s/article/session-hijacking-attack-definition-damage-defense?language=en_US | Only this detection cites it |
| www.elastic.co/security-labs/monitoring-okta-threats-with-elastic-security | 48from 2 sources |
| www.elastic.co/security-labs/starter-guide-to-understanding-okta | 48from 2 sources |
| www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy | 45 |
From the source
- At source
- Open at source
- Upstream identifier
- cc382a2e-7e52-11ee-9aac-f661ea17fbcd
- Tagged by the source as
- Data Source: OktaData Source: Okta System LogsDomain: IdentityDomain: SaaSNoise: HighPerformance: FastPlatform: OktaProfile: AggressiveResources: Investigation GuideRule Type: ES|QLTactic: Credential AccessThreat: AiTM Phishing
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3