Attempt to Create Okta API Token
editAttempt to Create Okta API Token
editAn adversary may create an Okta API token to maintain access to an organization’s network while they work to achieve their objectives. An attacker may abuse an API token to execute techniques such as creating user accounts, or disabling security rules or policies.
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: 2 (version history)
Added (Elastic Stack release): 7.9.0
Last modified (Elastic Stack release): 7.10.0
Rule authors: Elastic
Rule license: Elastic License
Potential false positives
editIf the behavior of creating Okta API tokens is expected, consider adding exceptions to this rule to filter false positives.
Investigation guide
editThe Okta Filebeat module must be enabled to use this rule.
Rule query
editevent.dataset:okta.system and event.action:system.api_token.create
Threat mapping
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Persistence
- ID: TA0003
- Reference URL: https://attack.mitre.org/tactics/TA0003/
-
Technique:
- Name: Create Account
- ID: T1136
- Reference URL: https://attack.mitre.org/techniques/T1136/
Rule version history
edit- Version 2 (7.10.0 release)
-
-
Updated query, changed from:
event.module:okta and event.dataset:okta.system and event.action:system.api_token.create
-