Attempts to Brute Force an Okta User Account

Elastic Stack Serverless Security

Identifies when an Okta user account is locked out 3 times within a 3 hour window. An adversary may attempt a brute force or password spraying attack to obtain unauthorized access to user accounts. The default Okta authentication policy ensures that a user account is locked out after 10 failed authentication attempts.

Rule type: threshold

Rule indices:

• filebeat-*
• logs-okta*

Severity: medium

Risk score: 47

Runs every: None

Searches indices from: now-180m (https://www.elastic.co/guide/en/elasticsearch/reference/current/common-options.html#date-math[Date Math format], see also Additional look-back time)

Maximum alerts per execution: 100

References:

• https://developer.okta.com/docs/reference/api/system-log/
• https://developer.okta.com/docs/reference/api/event-types/

Tags:

• Elastic
• Identity
• Okta
• Continuous Monitoring
• SecOps
• Identity and Access

version: 5

Rule authors:

• Elastic
• @BenB196
• Austin Songer

Rule license: Elastic License v2

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

event.dataset:okta.system and event.action:user.account.lock

Framework: MITRE ATT&CKTM

• Tactic:

  • Name: Credential Access
  • ID: TA0006
  • Reference URL: https://attack.mitre.org/tactics/TA0006/

• Technique:

  • Name: Brute Force
  • ID: T1110
  • Reference URL: https://attack.mitre.org/techniques/T1110/