Attempt to Revoke Okta API Token
Identifies attempts to revoke an Okta API token. An adversary may attempt to revoke or delete an Okta API token to disrupt an organization's business operations.
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
- ESXiIaaSLinuxmacOSOffice SuiteSaaSWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- event_index
Known benign triggers
- If the behavior of revoking Okta API tokens is expected, consider adding exceptions to this rule to filter false positives.
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 |
| 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
- 676cff2b-450b-4cf1-8ed2-c0c58a4a2dd7
- Tagged by the source as
- Data Source: OktaDomain: IdentityNoise: LowPerformance: FastPlatform: OktaResources: Investigation GuideRule Type: Custom Query (KQL)Tactic: ImpactUse Case: Identity and Access Audit
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3