Skip to content

Commit 02fcd43

Browse files
[Rule Tuning] Potential Okta MFA Bombing via Push Notifications (#5073)
* updated rule logic * adjusted similar rule; added factor specification * updated investigation guide --------- Co-authored-by: Jonhnathan <[email protected]>
1 parent 7ff2648 commit 02fcd43

File tree

2 files changed

+53
-26
lines changed

2 files changed

+53
-26
lines changed

rules/integrations/okta/credential_access_okta_mfa_bombing_via_push_notifications.toml

Lines changed: 26 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
creation_date = "2023/11/18"
33
integration = ["okta"]
44
maturity = "production"
5-
updated_date = "2025/07/02"
5+
updated_date = "2025/09/10"
66

77
[rule]
88
author = ["Elastic"]
@@ -12,7 +12,7 @@ user eventually accepts the Okta push notification. An adversary may attempt to
1212
for an organization to obtain unauthorized access.
1313
"""
1414
event_category_override = "event.category"
15-
index = ["filebeat-*", "logs-okta*"]
15+
index = ["filebeat-*", "logs-okta.system*"]
1616
language = "eql"
1717
license = "Elastic License v2"
1818
name = "Potential Okta MFA Bombing via Push Notifications"
@@ -60,29 +60,41 @@ references = [
6060
]
6161
risk_score = 73
6262
rule_id = "8a0fbd26-867f-11ee-947c-f661ea17fbcd"
63-
setup = """## Setup
64-
65-
The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
66-
"""
6763
severity = "high"
6864
tags = [
65+
"Domain: Identity",
6966
"Use Case: Identity and Access Audit",
7067
"Tactic: Credential Access",
7168
"Data Source: Okta",
69+
"Data Source: Okta System Logs",
7270
"Resources: Investigation Guide",
7371
]
7472
type = "eql"
7573

7674
query = '''
7775
sequence by okta.actor.id with maxspan=10m
78-
[authentication where event.dataset == "okta.system"
79-
and okta.event_type == "user.mfa.okta_verify.deny_push"] with runs=5
80-
until [authentication where event.dataset == "okta.system"
81-
and (okta.event_type: (
82-
"user.authentication.sso",
83-
"user.authentication.auth_via_mfa",
84-
"user.authentication.verify",
85-
"user.session.start") and okta.outcome.result == "SUCCESS")]
76+
[ any
77+
where event.dataset == "okta.system"
78+
and (
79+
okta.event_type == "user.mfa.okta_verify.deny_push"
80+
or (
81+
okta.event_type == "user.authentication.auth_via_mfa"
82+
and okta.debug_context.debug_data.factor == "OKTA_VERIFY_PUSH"
83+
and okta.outcome.reason == "INVALID_CREDENTIALS"
84+
)
85+
)
86+
] with runs=5
87+
until
88+
[ any
89+
where event.dataset == "okta.system"
90+
and okta.event_type in (
91+
"user.authentication.sso",
92+
"user.authentication.auth_via_mfa",
93+
"user.authentication.verify",
94+
"user.session.start"
95+
)
96+
and okta.outcome.result == "SUCCESS"
97+
]
8698
'''
8799

88100

rules/integrations/okta/credential_access_okta_potentially_successful_okta_bombing_via_push_notifications.toml

Lines changed: 27 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
creation_date = "2022/01/05"
33
integration = ["okta"]
44
maturity = "production"
5-
updated_date = "2025/07/02"
5+
updated_date = "2025/09/10"
66

77
[rule]
88
author = ["Elastic"]
@@ -12,13 +12,13 @@ user eventually accepts the Okta push notification. An adversary may attempt to
1212
for an organization to obtain unauthorized access.
1313
"""
1414
event_category_override = "event.category"
15-
index = ["filebeat-*", "logs-okta*"]
15+
index = ["filebeat-*", "logs-okta.system*"]
1616
language = "eql"
1717
license = "Elastic License v2"
18-
name = "Potentially Successful MFA Bombing via Push Notifications"
18+
name = "Potentially Successful Okta MFA Bombing via Push Notifications"
1919
note = """## Triage and analysis
2020
21-
### Investigating Potentially Successful MFA Bombing via Push Notifications
21+
### Investigating Potentially Successful Okta MFA Bombing via Push Notifications
2222
2323
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.
2424
@@ -65,23 +65,38 @@ risk_score = 73
6565
rule_id = "97a8e584-fd3b-421f-9b9d-9c9d9e57e9d7"
6666
severity = "high"
6767
tags = [
68+
"Domain: Identity",
6869
"Use Case: Identity and Access Audit",
6970
"Tactic: Credential Access",
7071
"Data Source: Okta",
72+
"Data Source: Okta System Logs",
7173
"Resources: Investigation Guide",
7274
]
7375
type = "eql"
7476

7577
query = '''
7678
sequence by okta.actor.id with maxspan=10m
77-
[authentication where event.dataset == "okta.system" and event.module == "okta"
78-
and event.action == "user.mfa.okta_verify.deny_push"] with runs=3
79-
[authentication where event.dataset == "okta.system" and event.module == "okta"
80-
and (event.action : (
81-
"user.authentication.sso",
82-
"user.authentication.auth_via_mfa",
83-
"user.authentication.verify",
84-
"user.session.start") and okta.outcome.result == "SUCCESS")]
79+
[ any
80+
where event.dataset == "okta.system"
81+
and (
82+
okta.event_type == "user.mfa.okta_verify.deny_push"
83+
or (
84+
okta.event_type == "user.authentication.auth_via_mfa"
85+
and okta.debug_context.debug_data.factor == "OKTA_VERIFY_PUSH"
86+
and okta.outcome.reason == "INVALID_CREDENTIALS"
87+
)
88+
)
89+
] with runs=5
90+
[ any
91+
where event.dataset == "okta.system"
92+
and okta.event_type in (
93+
"user.authentication.sso",
94+
"user.authentication.auth_via_mfa",
95+
"user.authentication.verify",
96+
"user.session.start"
97+
)
98+
and okta.outcome.result == "SUCCESS"
99+
]
85100
'''
86101

87102

0 commit comments

Comments
 (0)