MFA Disabled for Google Workspace Organization

  1[metadata]
  2creation_date = "2020/11/17"
  3integration = ["google_workspace"]
  4maturity = "production"
  5updated_date = "2024/09/23"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Detects when multi-factor authentication (MFA) is disabled for a Google Workspace organization. An adversary may attempt
 11to modify a password policy in order to weaken an organization’s security controls.
 12"""
 13false_positives = [
 14    """
 15    MFA settings may be modified by system administrators. Verify that the configuration change was expected. Exceptions
 16    can be added to this rule to filter expected behavior.
 17    """,
 18]
 19from = "now-130m"
 20index = ["filebeat-*", "logs-google_workspace*"]
 21interval = "10m"
 22language = "kuery"
 23license = "Elastic License v2"
 24name = "MFA Disabled for Google Workspace Organization"
 25note = """## Triage and analysis
 26
 27### Investigating MFA Disabled for Google Workspace Organization
 28
 29Multi-factor authentication (MFA) is a process in which users are prompted for an additional form of identification, such as a code on their cell phone or a fingerprint scan, during the sign-in process.
 30
 31If you only use a password to authenticate a user, it leaves an insecure vector for attack. If the users's password is weak or has been exposed elsewhere, an attacker could use it to gain access. Requiring a second form of authentication increases security because attackers cannot easily obtain or duplicate the additional authentication factor.
 32
 33For more information about using MFA in Google Workspace, access the [official documentation](https://support.google.com/a/answer/175197).
 34
 35This rule identifies when MFA enforcement is turned off in Google Workspace. This modification weakens account security and can lead to accounts and other assets being compromised.
 36
 37#### Possible investigation steps
 38
 39- Identify the user account that performed the action and whether it should perform this kind of action.
 40- Investigate other alerts associated with the user account during the past 48 hours.
 41- Contact the account and resource owners and confirm whether they are aware of this activity.
 42- Check if this operation was approved and performed according to the organization's change management policy.
 43- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
 44
 45### False positive analysis
 46
 47- While this activity can be done by administrators, all users must use MFA. The security team should address any potential benign true positive (B-TP), as this configuration can risk the user and domain.
 48
 49### Response and remediation
 50
 51- Initiate the incident response process based on the outcome of the triage.
 52- Disable or limit the account during the investigation and response.
 53- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
 54    - Identify the account role in the cloud environment.
 55    - Assess the criticality of affected services and servers.
 56    - Work with your IT team to identify and minimize the impact on users.
 57    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
 58    - Identify any regulatory or legal ramifications related to this activity.
 59- 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.
 60- Reactivate the multi-factor authentication enforcement.
 61- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
 62- Implement security best practices [outlined](https://support.google.com/a/answer/7587183) by Google.
 63- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
 64- 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).
 65
 66## Setup
 67
 68The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 69
 70### Important Information Regarding Google Workspace Event Lag Times
 71- 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.
 72- This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 73- 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.
 74- By default, `var.interval` is set to 2 hours (2h). Consider changing this interval to a lower value, such as 10 minutes (10m).
 75- See the following references for further information:
 76  - https://support.google.com/a/answer/7061566
 77  - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html"""
 78references = [
 79    "https://support.google.com/a/answer/7061566",
 80    "https://www.elastic.co/security-labs/google-workspace-attack-surface-part-one",
 81    "https://www.elastic.co/security-labs/google-workspace-attack-surface-part-two"
 82]
 83risk_score = 47
 84rule_id = "e555105c-ba6d-481f-82bb-9b633e7b4827"
 85severity = "medium"
 86tags = [
 87    "Domain: Cloud",
 88    "Data Source: Google Workspace",
 89    "Use Case: Identity and Access Audit",
 90    "Tactic: Persistence",
 91    "Resources: Investigation Guide",
 92]
 93timestamp_override = "event.ingested"
 94type = "query"
 95
 96query = '''
 97event.dataset:google_workspace.admin and event.provider:admin and event.category:iam and event.action:(ENFORCE_STRONG_AUTHENTICATION or ALLOW_STRONG_AUTHENTICATION) and google_workspace.admin.new_value:false
 98'''
 99
100
101[[rule.threat]]
102framework = "MITRE ATT&CK"
103[[rule.threat.technique]]
104id = "T1556"
105name = "Modify Authentication Process"
106reference = "https://attack.mitre.org/techniques/T1556/"
107
108
109[rule.threat.tactic]
110id = "TA0003"
111name = "Persistence"
112reference = "https://attack.mitre.org/tactics/TA0003/"