IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Attempts to Brute Force a Microsoft 365 User Account Auditd Login Attempt at Forbidden Time »
Elastic Docs ›Elastic Security Solution [8.2] ›Detections and alerts ›Prebuilt rule reference

Attempts to Brute Force an Okta User Account

edit

Attempts to Brute Force an Okta User Account

edit

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: 5 minutes

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

Maximum alerts per execution: 100

References:

Tags:

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

Version: 5 (version history)

Added (Elastic Stack release): 7.10.0

Last modified (Elastic Stack release): 7.14.0

Rule authors: Elastic, @BenB196, Austin Songer

Rule license: Elastic License v2

Investigation guide

edit
## Config

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:user.account.lock

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 5 (7.14.0 release)

  • Updated query, changed from:

    event.dataset:okta.system and event.action:user.account.lock
Version 4 (7.13.0 release)
  • Formatting only
Version 3 (7.12.0 release)
  • Formatting only
Version 2 (7.11.0 release)
  • Formatting only
« Attempts to Brute Force a Microsoft 365 User Account Auditd Login Attempt at Forbidden Time »