High Number of Okta User Password Reset or Unlock Attempts

  1[metadata]
  2creation_date = "2020/08/19"
  3integration = ["okta"]
  4maturity = "production"
  5min_stack_comments = "Breaking change in Okta integration bumping version to ^2.0.0"
  6min_stack_version = "8.10.0"
  7updated_date = "2024/01/05"
  8
  9[rule]
 10author = ["Elastic", "@BenB196", "Austin Songer"]
 11description = """
 12Identifies a high number of Okta user password reset or account unlock attempts. An adversary may attempt to obtain
 13unauthorized access to Okta user accounts using these methods and attempt to blend in with normal activity in their
 14target's environment and evade detection.
 15"""
 16false_positives = [
 17    """
 18    The number of Okta user password reset or account unlock attempts will likely vary between organizations. To fit
 19    this rule to their organization, users can duplicate this rule and edit the schedule and threshold values in the new
 20    rule.
 21    """,
 22]
 23from = "now-60m"
 24index = ["filebeat-*", "logs-okta*"]
 25language = "kuery"
 26license = "Elastic License v2"
 27name = "High Number of Okta User Password Reset or Unlock Attempts"
 28note = """## Triage and analysis
 29
 30### Investigating High Number of Okta User Password Reset or Unlock Attempts
 31
 32This rule is designed to detect a suspiciously high number of password reset or account unlock attempts in Okta. Excessive password resets or account unlocks can be indicative of an attacker's attempt to gain unauthorized access to an account.
 33
 34#### Possible investigation steps:
 35- Identify the actor associated with the excessive attempts. The `okta.actor.alternate_id` field can be used for this purpose.
 36- Determine the client used by the actor. You can look at `okta.client.device`, `okta.client.ip`, `okta.client.user_agent.raw_user_agent`, `okta.client.ip_chain.ip`, and `okta.client.geographical_context`.
 37- Review the `okta.outcome.result` and `okta.outcome.reason` fields to understand the outcome of the password reset or unlock attempts.
 38- Review the event actions associated with these attempts. Look at the `event.action` field and filter for actions related to password reset and account unlock attempts.
 39- Check for other similar patterns of behavior from the same actor or IP address. If there is a high number of failed login attempts before the password reset or unlock attempts, this may suggest a brute force attack.
 40- Also, look at the times when these attempts were made. If these were made during off-hours, it could further suggest an adversary's activity.
 41
 42### False positive analysis:
 43- This alert might be a false positive if there are legitimate reasons for a high number of password reset or unlock attempts. This could be due to the user forgetting their password or account lockouts due to too many incorrect attempts.
 44- Check the actor's past behavior. If this is their usual behavior and they have a valid reason for it, then it might be a false positive.
 45
 46### Response and remediation:
 47- If unauthorized attempts are confirmed, initiate the incident response process.
 48- Reset the user's password and enforce MFA re-enrollment, if applicable.
 49- Block the IP address or device used in the attempts, if they appear suspicious.
 50- If the attack was facilitated by a particular technique, ensure your systems are patched or configured to prevent such techniques.
 51- Consider a security review of your Okta policies and rules to ensure they follow security best practices.
 52
 53## Setup
 54
 55The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 56"""
 57
 58references = [
 59    "https://developer.okta.com/docs/reference/api/system-log/",
 60    "https://developer.okta.com/docs/reference/api/event-types/",
 61    "https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy",
 62]
 63risk_score = 47
 64rule_id = "e90ee3af-45fc-432e-a850-4a58cf14a457"
 65severity = "medium"
 66tags = ["Use Case: Identity and Access Audit", "Data Source: Okta", "Tactic: Defense Evasion"]
 67type = "threshold"
 68timestamp_override = "event.ingested"
 69
 70query = '''
 71event.dataset:okta.system and
 72  event.action:(system.email.account_unlock.sent_message or system.email.password_reset.sent_message or
 73                system.sms.send_account_unlock_message or system.sms.send_password_reset_message or
 74                system.voice.send_account_unlock_call or system.voice.send_password_reset_call or
 75                user.account.unlock_token)
 76'''
 77
 78
 79[[rule.threat]]
 80framework = "MITRE ATT&CK"
 81[[rule.threat.technique]]
 82id = "T1078"
 83name = "Valid Accounts"
 84reference = "https://attack.mitre.org/techniques/T1078/"
 85
 86
 87[rule.threat.tactic]
 88id = "TA0005"
 89name = "Defense Evasion"
 90reference = "https://attack.mitre.org/tactics/TA0005/"
 91[[rule.threat]]
 92framework = "MITRE ATT&CK"
 93[[rule.threat.technique]]
 94id = "T1078"
 95name = "Valid Accounts"
 96reference = "https://attack.mitre.org/techniques/T1078/"
 97
 98
 99[rule.threat.tactic]
100id = "TA0003"
101name = "Persistence"
102reference = "https://attack.mitre.org/tactics/TA0003/"
103[[rule.threat]]
104framework = "MITRE ATT&CK"
105[[rule.threat.technique]]
106id = "T1078"
107name = "Valid Accounts"
108reference = "https://attack.mitre.org/techniques/T1078/"
109
110
111[rule.threat.tactic]
112id = "TA0001"
113name = "Initial Access"
114reference = "https://attack.mitre.org/tactics/TA0001/"
115
116[rule.threshold]
117field = ["okta.actor.alternate_id"]
118value = 5