Attempt to Revoke Okta API Token
editAttempt to Revoke Okta API Token
editIdentifies 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.
Rule type: query
Rule indices:
- filebeat-*
- logs-okta*
Severity: low
Risk score: 21
Runs every: 5 minutes
Searches indices from: now-6m (Date Math format, see also Additional look-back time)
Maximum alerts per execution: 100
References:
Tags:
- Elastic
- Identity
- Okta
- Continuous Monitoring
- SecOps
- Monitoring
Version: 6 (version history)
Added (Elastic Stack release): 7.9.0
Last modified (Elastic Stack release): 7.13.0
Rule authors: Elastic
Rule license: Elastic License v2
Potential false positives
editIf the behavior of revoking Okta API tokens is expected, consider adding exceptions to this rule to filter false positives.
Investigation guide
editConfig
The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
Rule query
editevent.dataset:okta.system and event.action:system.api_token.revoke
Threat mapping
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Impact
- ID: TA0040
- Reference URL: https://attack.mitre.org/tactics/TA0040/
-
Technique:
- Name: Account Access Removal
- ID: T1531
- Reference URL: https://attack.mitre.org/techniques/T1531/
Rule version history
edit- Version 6 (7.13.0 release)
-
- Formatting only
- Version 5 (7.12.0 release)
-
- Formatting only
- Version 4 (7.11.2 release)
-
- Formatting only
- Version 3 (7.11.0 release)
-
- Formatting only
- Version 2 (7.10.0 release)
-
-
Updated query, changed from:
event.module:okta and event.dataset:okta.system and event.action:system.api_token.revoke
-