Potential Okta MFA Bombing via Push Notifications

calendar Sep 25, 2024 · Use Case: Identity and Access Audit Tactic: Credential Access Data Source: Okta  ·
Share on: linkedin copy

Detects when an attacker abuses the Multi-Factor authentication mechanism by repeatedly issuing login requests until the user eventually accepts the Okta push notification. An adversary may attempt to bypass the Okta MFA policies configured for an organization to obtain unauthorized access.

Elastic rule (View on GitHub)

 1[metadata]
 2creation_date = "2023/11/18"
 3integration = ["okta"]
 4maturity = "production"
 5updated_date = "2024/09/23"
 6
 7[rule]
 8author = ["Elastic"]
 9description = """
10Detects when an attacker abuses the Multi-Factor authentication mechanism by repeatedly issuing login requests until the
11user eventually accepts the Okta push notification. An adversary may attempt to bypass the Okta MFA policies configured
12for an organization to obtain unauthorized access.
13"""
14event_category_override = "event.category"
15index = ["filebeat-*", "logs-okta*"]
16language = "eql"
17license = "Elastic License v2"
18name = "Potential Okta MFA Bombing via Push Notifications"
19note = """## Triage and analysis
20
21### Investigating Potential Okta MFA Bombing via Push Notifications
22
23Multi-Factor Authentication (MFA) is an effective method to prevent unauthorized access. However, some adversaries may abuse the system by repeatedly sending MFA push notifications until the user unwittingly approves the access.
24
25This rule detects when a user denies MFA Okta Verify push notifications twice, followed by a successful authentication event within a 10-minute window. This sequence could indicate an adversary's attempt to bypass the Okta MFA policy.
26
27#### Possible investigation steps:
28
29- Identify the user who received the MFA notifications by reviewing the `user.email` field.
30- Identify the time, source IP, and geographical location of the MFA requests and the subsequent successful login.
31- Review the `event.action` field to understand the nature of the events. It should include two `user.mfa.okta_verify.deny_push` actions and one `user.authentication.sso` action.
32- Ask the user if they remember receiving the MFA notifications and subsequently logging into their account.
33- Check if the MFA requests and the successful login occurred during the user's regular activity hours.
34- Look for any other suspicious activity on the account around the same time.
35- Identify whether the same pattern is repeated for other users in your organization. Multiple users receiving push notifications simultaneously might indicate a larger attack.
36
37### False positive analysis:
38
39- Determine if the MFA push notifications were legitimate. Sometimes, users accidentally trigger MFA requests or deny them unintentionally and later approve them.
40- Check if there are known issues with the MFA system causing false denials.
41
42### Response and remediation:
43
44- If unauthorized access is confirmed, initiate your incident response process.
45- Alert the user and your IT department immediately.
46- If possible, isolate the user's account until the issue is resolved.
47- Investigate the source of the unauthorized access.
48- If the account was accessed by an unauthorized party, determine the actions they took after logging in.
49- Consider enhancing your MFA policy to prevent such incidents in the future.
50- Encourage users to report any unexpected MFA notifications immediately.
51- Review and update your incident response plans and security policies based on the findings from the incident.
52"""
53references = [
54    "https://www.mandiant.com/resources/russian-targeting-gov-business",
55    "https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy",
56    "https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection",
57    "https://www.rezonate.io/blog/okta-logs-decoded-unveiling-identity-threats-through-threat-hunting/",
58    "https://www.elastic.co/security-labs/monitoring-okta-threats-with-elastic-security",
59    "https://www.elastic.co/security-labs/starter-guide-to-understanding-okta",
60]
61risk_score = 73
62rule_id = "8a0fbd26-867f-11ee-947c-f661ea17fbcd"
63setup = """## Setup
64
65The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
66"""
67severity = "high"
68tags = ["Use Case: Identity and Access Audit", "Tactic: Credential Access", "Data Source: Okta"]
69type = "eql"
70
71query = '''
72sequence by okta.actor.id with maxspan=10m
73  [authentication where event.dataset == "okta.system"
74    and okta.event_type == "user.mfa.okta_verify.deny_push"] with runs=5
75  until [authentication where event.dataset == "okta.system"
76    and (okta.event_type: (
77      "user.authentication.sso",
78      "user.authentication.auth_via_mfa",
79      "user.authentication.verify",
80      "user.session.start") and okta.outcome.result == "SUCCESS")]
81'''
82
83
84[[rule.threat]]
85framework = "MITRE ATT&CK"
86[[rule.threat.technique]]
87id = "T1621"
88name = "Multi-Factor Authentication Request Generation"
89reference = "https://attack.mitre.org/techniques/T1621/"
90
91
92[rule.threat.tactic]
93id = "TA0006"
94name = "Credential Access"
95reference = "https://attack.mitre.org/tactics/TA0006/"

Triage and analysis

Investigating Potential Okta MFA Bombing via Push Notifications

Multi-Factor Authentication (MFA) is an effective method to prevent unauthorized access. However, some adversaries may abuse the system by repeatedly sending MFA push notifications until the user unwittingly approves the access.

This rule detects when a user denies MFA Okta Verify push notifications twice, followed by a successful authentication event within a 10-minute window. This sequence could indicate an adversary's attempt to bypass the Okta MFA policy.

Possible investigation steps:

  • Identify the user who received the MFA notifications by reviewing the user.email field.
  • Identify the time, source IP, and geographical location of the MFA requests and the subsequent successful login.
  • Review the event.action field to understand the nature of the events. It should include two user.mfa.okta_verify.deny_push actions and one user.authentication.sso action.
  • Ask the user if they remember receiving the MFA notifications and subsequently logging into their account.
  • Check if the MFA requests and the successful login occurred during the user's regular activity hours.
  • Look for any other suspicious activity on the account around the same time.
  • Identify whether the same pattern is repeated for other users in your organization. Multiple users receiving push notifications simultaneously might indicate a larger attack.

False positive analysis:

  • Determine if the MFA push notifications were legitimate. Sometimes, users accidentally trigger MFA requests or deny them unintentionally and later approve them.
  • Check if there are known issues with the MFA system causing false denials.

Response and remediation:

  • If unauthorized access is confirmed, initiate your incident response process.
  • Alert the user and your IT department immediately.
  • If possible, isolate the user's account until the issue is resolved.
  • Investigate the source of the unauthorized access.
  • If the account was accessed by an unauthorized party, determine the actions they took after logging in.
  • Consider enhancing your MFA policy to prevent such incidents in the future.
  • Encourage users to report any unexpected MFA notifications immediately.
  • Review and update your incident response plans and security policies based on the findings from the incident.

References

Related rules

to-top