IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Attempt to Retrieve User Data from AWS EC2 Instance Attempt to Unload Elastic Endpoint Security Kernel Extension »
Elastic Docs ›Elastic Security Solution [8.14] ›Detections and alerts ›Prebuilt rule reference

Attempt to Revoke Okta API Token

edit

Attempt to Revoke Okta API Token

edit

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.

Rule type: query

Rule indices:

  • filebeat-*
  • logs-okta*

Severity: low

Risk score: 21

Runs every: 5m

Searches indices from: None (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

References:

Tags:

  • Use Case: Identity and Access Audit
  • Data Source: Okta
  • Tactic: Impact

Version: 209

Rule authors:

  • Elastic

Rule license: Elastic License v2

Investigation guide

edit

Triage and analysis

Investigating Attempt to Revoke Okta API Token

The rule alerts when attempts are made to revoke an Okta API token. The API tokens are critical for integration services, and revoking them may lead to disruption in services. Therefore, it’s important to validate these activities.

Possible investigation steps:

  • Identify the actor associated with the API token revocation attempt. You can use the okta.actor.alternate_id field for this purpose.
  • Determine the client used by the actor. Review the okta.client.device, okta.client.ip, okta.client.user_agent.raw_user_agent, okta.client.ip_chain.ip, and okta.client.geographical_context fields.
  • Verify if the API token revocation was authorized or part of some planned activity.
  • Check the okta.outcome.result and okta.outcome.reason fields to see if the attempt was successful or failed.
  • Analyze the past activities of the actor involved in this action. An actor who usually performs such activities may indicate a legitimate reason.
  • Evaluate the actions that happened just before and after this event. It can help understand the full context of the activity.

False positive analysis:

  • It might be a false positive if the action was part of a planned activity or was performed by an authorized person.

Response and remediation:

  • If unauthorized revocation attempts are confirmed, initiate the incident response process.
  • Block the IP address or device used in the attempts, if they appear suspicious.
  • Reset the user’s password and enforce MFA re-enrollment, if applicable.
  • Conduct a review of Okta policies and ensure they are in accordance with security best practices.
  • If the revoked token was used for critical integrations, coordinate with the relevant team to minimize the impact.

Setup

edit

The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.

Rule query

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

Framework: MITRE ATT&CKTM

« Attempt to Retrieve User Data from AWS EC2 Instance Attempt to Unload Elastic Endpoint Security Kernel Extension »