Google Workspace MFA Enforcement Disabled For Organization

  1[metadata]
  2creation_date = "2020/11/17"
  3integration = ["google_workspace"]
  4maturity = "production"
  5updated_date = "2026/06/01"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Detects when an administrator disables multi-factor authentication enforcement or removes the ability for users
 11to enroll in 2-step verification across a Google Workspace organization or organizational unit. Adversaries with
 12administrative access may weaken tenant-wide authentication requirements to enable password-only sign-ins, facilitate
 13credential abuse at scale, and reduce friction for follow-on account takeover across the domain.
 14"""
 15false_positives = [
 16    """
 17    MFA policies may be modified by system administrators. Verify that the configuration change was expected. Exceptions
 18    can be added to this rule to filter expected behavior.
 19    """,
 20]
 21from = "now-130m"
 22index = ["filebeat-*", "logs-google_workspace.admin-*"]
 23interval = "10m"
 24language = "kuery"
 25license = "Elastic License v2"
 26name = "Google Workspace MFA Enforcement Disabled For Organization"
 27note = """## Triage and analysis
 28
 29### Investigating Google Workspace MFA Enforcement Disabled For Organization
 30
 31Threat actors with Google Workspace administrative access may disable organization-wide 2-step verification (2SV)
 32controls to weaken authentication for many users at once. Unlike a single user turning off 2SV on their own account,
 33this change affects tenant policy and can allow password-only sign-ins across an organizational unit or the entire
 34domain. This supports large-scale credential abuse, reduces MFA friction for follow-on compromise, and can blind
 35security teams if paired with other admin tampering.
 36
 37This rule identifies when an administrator sets `google_workspace.admin.new_value` to `false` for either
 38`ENFORCE_STRONG_AUTHENTICATION` (2SV enforcement turned off) or `ALLOW_STRONG_AUTHENTICATION` (users can no longer turn
 39on 2SV).
 40
 41### Possible investigation steps
 42
 43- Identify the initiating (actor) administrator by reviewing `user.email` or `user.name`, and note the `source.ip` and `event.ingested` timestamps.
 44- Identify the setting changed by reviewing `event.action`:
 45  - `ENFORCE_STRONG_AUTHENTICATION` — 2SV enforcement was disabled for the affected scope.
 46  - `ALLOW_STRONG_AUTHENTICATION` — users were prevented from turning on 2SV.
 47- Review `google_workspace.admin.old_value` and `google_workspace.admin.new_value` to confirm the prior and updated policy state.
 48- Determine the scope of impact by reviewing `google_workspace.admin.org_unit.name` (if present) and identifying which users or groups inherit the weakened policy.
 49- Determine whether the change is expected and authorized:
 50  - Validate there is an approved change request/ticket and that the actor is authorized to modify authentication policy.
 51  - If the actor account or `source.ip` is unusual, treat the alert as higher priority until proven benign.
 52- Search Kibana for related authentication and admin activity:
 53  - Use the following KQL example to find other MFA policy changes by the same actor:
 54    ```
 55    data_stream.dataset: "google_workspace.admin" and user.email: "<ACTOR_EMAIL>" and event.action: ("ENFORCE_STRONG_AUTHENTICATION" or "ALLOW_STRONG_AUTHENTICATION")
 56    ```
 57  - Search for user-level 2SV disables that follow this change:
 58    ```
 59    data_stream.dataset: ("google_workspace.login" or "google_workspace.user_accounts") and event.action: "2sv_disable"
 60    ```
 61  - Scope for other security-weakening admin actions from the same `user.email` within the last 48 hours, such as password policy changes, SSO/SAML modifications, or role assignments.
 62
 63### False positive analysis
 64
 65- Verify the MFA policy change aligns with an approved change window, migration, or troubleshooting activity.
 66- Confirm the initiating administrator is legitimate and not acting from unusual IPs, devices, or locations.
 67- Even authorized changes materially weaken tenant security, validate business justification and time-bound rollback plans.
 68
 69### Response and remediation
 70
 71- Initiate the incident response process based on triage findings.
 72- If the change is not clearly authorized, restore 2SV enforcement and re-enable Allow users to turn on 2-Step Verification for the affected scope while the investigation proceeds.
 73- If the initiating admin account is suspected compromised, reset credentials, revoke active sessions, and review delegated admin roles assigned to that account.
 74- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
 75    - Identify the account role in the cloud environment.
 76    - Assess the criticality of affected services and servers.
 77    - Work with your IT team to identify and minimize the impact on users.
 78    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
 79    - Identify any regulatory or legal ramifications related to this activity.
 80- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 81- Review the permissions assigned to the implicated administrator to ensure that the least privilege principle is being followed.
 82- Implement security best practices [outlined](https://support.google.com/a/answer/7587183) by Google.
 83- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
 84- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 85
 86## Setup
 87
 88The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 89
 90### Important Information Regarding Google Workspace Event Lag Times
 91
 92- As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 93- This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 94- To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
 95- By default, `var.interval` is set to 2 hours (2h). Consider changing this interval to a lower value, such as 10 minutes (10m).
 96- See the following references for further information:
 97  - https://support.google.com/a/answer/7061566
 98  - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html"""
 99references = [
100    "https://support.google.com/a/answer/9176657?hl=en#",
101    "https://www.elastic.co/security-labs/google-workspace-attack-surface-part-one",
102    "https://www.elastic.co/security-labs/google-workspace-attack-surface-part-two"
103]
104risk_score = 47
105rule_id = "cad4500a-abd7-4ef3-b5d3-95524de7cfe1"
106severity = "medium"
107tags = [
108    "Domain: Cloud",
109    "Data Source: Google Workspace",
110    "Use Case: Configuration Audit",
111    "Tactic: Impact",
112    "Tactic: Credential Access",
113    "Tactic: Defense Evasion",
114    "Tactic: Persistence",
115    "Resources: Investigation Guide",
116]
117timestamp_override = "event.ingested"
118type = "query"
119
120query = '''
121data_stream.dataset:google_workspace.admin
122  and event.action:(ENFORCE_STRONG_AUTHENTICATION or ALLOW_STRONG_AUTHENTICATION)
123  and google_workspace.admin.new_value:false
124'''
125
126[rule.investigation_fields]
127field_names = [
128    "user.name",
129    "user.email",
130    "source.ip",
131    "event.action",
132    "google_workspace.admin.org_unit.name",
133    "google_workspace.admin.old_value",
134    "google_workspace.admin.new_value",
135]
136
137[[rule.threat]]
138framework = "MITRE ATT&CK"
139
140[[rule.threat.technique]]
141id = "T1531"
142name = "Account Access Removal"
143reference = "https://attack.mitre.org/techniques/T1531/"
144
145[rule.threat.tactic]
146id = "TA0040"
147name = "Impact"
148reference = "https://attack.mitre.org/tactics/TA0040/"
149
150[[rule.threat]]
151framework = "MITRE ATT&CK"
152
153[[rule.threat.technique]]
154id = "T1556"
155name = "Modify Authentication Process"
156reference = "https://attack.mitre.org/techniques/T1556/"
157
158[[rule.threat.technique.subtechnique]]
159id = "T1556.006"
160name = "Multi-Factor Authentication"
161reference = "https://attack.mitre.org/techniques/T1556/006/"
162
163[rule.threat.tactic]
164id = "TA0006"
165name = "Credential Access"
166reference = "https://attack.mitre.org/tactics/TA0006/"
167
168[[rule.threat]]
169framework = "MITRE ATT&CK"
170
171[[rule.threat.technique]]
172id = "T1556"
173name = "Modify Authentication Process"
174reference = "https://attack.mitre.org/techniques/T1556/"
175
176[[rule.threat.technique.subtechnique]]
177id = "T1556.006"
178name = "Multi-Factor Authentication"
179reference = "https://attack.mitre.org/techniques/T1556/006/"
180
181[rule.threat.tactic]
182id = "TA0005"
183name = "Defense Evasion"
184reference = "https://attack.mitre.org/tactics/TA0005/"
185
186
187[[rule.threat]]
188framework = "MITRE ATT&CK"
189
190[[rule.threat.technique]]
191id = "T1556"
192name = "Modify Authentication Process"
193reference = "https://attack.mitre.org/techniques/T1556/"
194
195[[rule.threat.technique.subtechnique]]
196id = "T1556.006"
197name = "Multi-Factor Authentication"
198reference = "https://attack.mitre.org/techniques/T1556/006/"
199
200[rule.threat.tactic]
201id = "TA0003"
202name = "Persistence"
203reference = "https://attack.mitre.org/tactics/TA0003/"