You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rules/integrations/azure/credential_access_azure_entra_totp_brute_force_attempts.toml
+81-59Lines changed: 81 additions & 59 deletions
Original file line number
Diff line number
Diff line change
@@ -2,90 +2,61 @@
2
2
creation_date = "2024/12/11"
3
3
integration = ["azure"]
4
4
maturity = "production"
5
-
updated_date = "2025/03/20"
5
+
updated_date = "2025/07/28"
6
6
7
7
[rule]
8
8
author = ["Elastic"]
9
9
description = """
10
10
Identifies brute force attempts against Azure Entra multi-factor authentication (MFA) Time-based One-Time Password
11
11
(TOTP) verification codes. This rule detects high frequency failed TOTP code attempts for a single user in a short
12
-
time-span. Adversaries with valid credentials, when attempting to login to Azure portal or other Azure services, may be
13
-
prompted to provide a TOTP code as part of the MFA process. If successful, adversaries can bypass MFA and gain
14
-
unauthorized access to Azure resources.
12
+
time-span with a high number of distinct session IDs. Adversaries may programmatically attemopt to brute-force TOTP
13
+
codes by generating several sessions and attempt to guess the correct code.
15
14
"""
16
15
false_positives = [
17
16
"""
18
17
Based on the high-frequency threshold, it would be unlikely for a legitimate user to exceed the threshold for failed
19
-
TOTP code attempts in a short time-span.
18
+
TOTP code attempts in a short time-span over multiple sessions.
20
19
""",
21
20
]
22
21
from = "now-9m"
23
22
language = "esql"
24
23
license = "Elastic License v2"
25
-
name = "Azure Entra MFA TOTP Brute Force Attempts"
24
+
name = "Microsoft Entra ID MFA TOTP Brute Force Attempts"
26
25
note = """## Triage and analysis
27
26
28
-
### Investigating Azure Entra MFA TOTP Brute Force Attempts
27
+
### Investigating Microsoft Entra ID MFA TOTP Brute Force Attempts
29
28
30
-
This rule detects high-frequency failed TOTP code attempts for a single user in a short timespan. Such behavior could indicate an adversary attempting to bypass multi-factor authentication (MFA) protections using valid credentials. Understanding the context of the user's typical behavior and identifying anomalies in the log data are critical to determining the nature of the activity.
29
+
This rule detects brute force attempts against Azure Entra multi-factor authentication (MFA) Time-based One-Time Password (TOTP) verification codes. It identifies high-frequency failed TOTP code attempts for a single user in a short time-span with a high number of distinct session IDs. Adversaries may programmatically attempt to brute-force TOTP codes by generating several sessions and attempting to guess the correct code.
31
30
32
31
#### Possible Investigation Steps:
33
32
34
-
**Review the Source IP Address**:
35
-
- Check the `source.ip` or `azure.signinlogs.caller_ip_address` field.
36
-
- Determine if the IP address is associated with the user’s typical login locations.
33
+
- Check the source addresses associated with the failed TOTP attempts.
34
+
- Determine if the source IP address is consistent with the user’s typical login locations.
37
35
- Look for unusual geographic patterns or anomalous IP addresses (e.g., proxies, VPNs, or locations outside the user’s normal activity).
38
-
39
-
**Analyze User Activity**:
40
-
- Identify the user from the `azure.signinlogs.properties.sign_in_identifier` field.
41
-
- Determine if the user is currently active from another device or session. Session hijacking could explain parallel activity with failed attempts.
42
-
- Review past logs for the user to determine whether MFA failures or other anomalies are consistent or new.
43
-
44
-
**Inspect the Authentication Method**:
45
-
- Evaluate the `azure.signinlogs.properties.mfa_detail.auth_method` field: `OATH verification code`.
46
-
- Confirm if the user typically uses TOTP codes or another MFA method (e.g., push notifications).
47
-
- Verify if there are any recent changes to the user’s MFA settings that may explain multiple failed attempts.
48
-
49
-
**Evaluate the User Agent**:
50
-
- Check the `user_agent.original` field.
51
-
- Identify if the user agent matches a typical browser or a potentially malicious script (e.g., Python-based).
52
-
- Look for deviations in operating system or browser versions from the user’s normal activity.
53
-
54
-
**Analyze Conditional Access Policies**:
55
-
- Review the `azure.signinlogs.properties.applied_conditional_access_policies` for enforced grant controls.
56
-
- Verify if MFA failures are tied to legitimate security policies (`display_name: Require multifactor authentication for admins`).
57
-
58
-
**Correlate with Other Events**:
59
-
- Search for other authentication attempts involving the same `azure.signinlogs.caller_ip_address`, `user_principal_name`, or `azure.signinlogs.properties.app_id`.
60
-
- Look for suspicious activity patterns, such as password resets, privilege escalation, or account lockouts.
61
-
36
+
- Review the error code associated with the failed attempts. This can help identify if the failures are due to incorrect TOTP codes or other issues.
37
+
- Verify that that auth metho reported is `OAth` as it indicates the use of TOTP codes.
38
+
- Pivot into signin logs for the target user and check if auth via TOTP was successful which would indicate a successful brute force attempt.
39
+
- Review conditional access policies applied to the user or group as reported by the sign-in logs.
40
+
- Analyze the client application ID and display name to determine if the attempts are coming from a legitimate application or a potentially malicious script.
41
+
- Adversaries may use legitimate FOCI applications to bypass security controls or make login attempts appear legitimate.
42
+
- Review the resource ID access is being attempted against such as MyApps, Microsoft Graph, or other resources. This can help identify if the attempts are targeting specific applications or services.
43
+
- The correlation IDs or session IDs can be used to trace the authentication attempts across different logs or systems. Note that for this specific behavior, unique session ID count is high and could be challenging to correlate.
62
44
63
45
#### False Positive Analysis:
64
46
65
-
- **Unintentional User Behavior**:
66
47
- Verify if the failed attempts could result from the user’s unfamiliarity with TOTP codes or issues with device synchronization.
67
48
- Check if the user recently switched MFA methods or devices, which could explain multiple failures.
68
49
- Determine if this is whitebox testing or a developer testing MFA integration.
69
50
70
-
- **Administrative Actions**:
71
-
- Determine if the activity is related to legitimate administrative testing or configuration changes in the MFA system.
72
-
73
51
#### Response and Remediation:
74
52
75
-
- **Immediate Actions**:
76
53
- If proven malicious, lock the affected account temporarily to prevent further unauthorized attempts.
77
54
- Notify the user of suspicious activity and validate their access to the account.
78
55
- Reset passwords and MFA settings for the affected user to prevent unauthorized access while communicating with the user.
79
-
80
-
- **Strengthen Authentication Policies**:
81
56
- Ensure conditional access policies are configured to monitor and restrict anomalous login behavior.
82
57
- Consider a different MFA method or additional security controls to prevent future bypass attempts.
83
-
84
-
- **Monitor and Audit**:
85
58
- Implement additional monitoring to track high-frequency authentication failures across the environment.
86
59
- Audit historical logs for similar patterns involving other accounts to identify broader threats.
87
-
88
-
- **Educate and Train Users**:
89
60
- Provide guidance on the secure use of MFA and the importance of recognizing and reporting suspicious activity.
90
61
"""
91
62
references = [
@@ -95,16 +66,16 @@ references = [
95
66
]
96
67
risk_score = 47
97
68
rule_id = "3fac01b2-b811-11ef-b25b-f661ea17fbce"
98
-
setup = """#### Required Azure Entra Sign-In Logs
99
-
This rule requires the Azure logs integration be enabled and configured to collect all logs, including sign-in logs from Entra. In Entra, sign-in logs must be enabled and streaming to the Event Hub used for the Azure logs integration.
69
+
setup = """#### Required Entra ID Sign-In Logs
70
+
This rule requires the Entra ID sign-in logs via the Azure integration be enabled. In Entra ID, sign-in logs must be enabled and streaming to the Event Hub used for the Entra ID logs integration.
100
71
"""
101
72
severity = "medium"
102
73
tags = [
103
74
"Domain: Cloud",
104
-
"Domain: SaaS",
75
+
"Domain: Identity",
105
76
"Data Source: Azure",
106
77
"Data Source: Entra ID",
107
-
"Data Source: Entra ID Sign-in",
78
+
"Data Source: Entra ID Sign-in logs",
108
79
"Use Case: Identity and Access Audit",
109
80
"Use Case: Threat Detection",
110
81
"Tactic: Credential Access",
@@ -115,25 +86,76 @@ type = "esql"
115
86
116
87
query = '''
117
88
from logs-azure.signinlogs* metadata _id, _version, _index
89
+
118
90
| where
119
91
// filter for Entra Sign-In Logs
120
92
event.dataset == "azure.signinlogs"
121
93
and azure.signinlogs.operation_name == "Sign-in activity"
94
+
and azure.signinlogs.properties.user_type == "Member"
122
95
123
96
// filter for MFA attempts with OATH conditional access attempts or TOTP
124
-
and azure.signinlogs.properties.authentication_requirement == "multiFactorAuthentication"
125
97
and azure.signinlogs.properties.mfa_detail.auth_method == "OATH verification code"
126
98
127
99
// filter on failures only from brute-force attempts
128
-
and azure.signinlogs.properties.conditional_access_status == "failure"
129
-
and azure.signinlogs.result_description == "Authentication failed during strong authentication request."
0 commit comments