Attempt to Create Okta API Token

edit

An 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: medium

Risk score: 47

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: 4 (version history)

Added (Elastic Stack release): 7.9.0

Last modified (Elastic Stack release): 7.11.2

Rule authors: Elastic

Rule license: Elastic License

Potential false positives

edit

If the behavior of creating Okta API tokens is expected, consider adding exceptions to this rule to filter false positives.

Investigation guide

edit

The Okta Filebeat module must be enabled to use this rule.

Rule query

edit
event.dataset:okta.system and event.action:system.api_token.create

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
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.create