Google Workspace Restrictions for Marketplace Modified to Allow Any App

  1[metadata]
  2creation_date = "2022/08/25"
  3integration = ["google_workspace"]
  4maturity = "production"
  5updated_date = "2024/09/23"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Detects when the Google Marketplace restrictions are changed to allow any application for users in Google Workspace.
 11Malicious APKs created by adversaries may be uploaded to the Google marketplace but not installed on devices managed
 12within Google Workspace. Administrators should set restrictions to not allow any application from the marketplace for
 13security reasons. Adversaries may enable any app to be installed and executed on mobile devices within a Google
 14Workspace environment prior to distributing the malicious APK to the end user.
 15"""
 16false_positives = [
 17    """
 18    Applications can be added and removed from blocklists by Google Workspace administrators, but they can all be
 19    explicitly allowed for users. Verify that the configuration change was expected. Exceptions can be added to this
 20    rule to filter expected behavior.
 21    """,
 22]
 23from = "now-9m"
 24index = ["filebeat-*", "logs-google_workspace*"]
 25language = "kuery"
 26license = "Elastic License v2"
 27name = "Google Workspace Restrictions for Marketplace Modified to Allow Any App"
 28note = """## Triage and analysis
 29
 30### Investigating Google Workspace Restrictions for Marketplace Modified to Allow Any App
 31
 32Google Workspace Marketplace is an online store for free and paid web applications that work with Google Workspace services and third-party software. Listed applications are based on Google APIs or Google Apps Script and created by both Google and third-party developers.
 33
 34Marketplace applications require access to specific Google Workspace resources. Applications can be installed by individual users, if they have permission, or can be installed for an entire Google Workspace domain by administrators. Consent screens typically display what permissions and privileges the application requires during installation. As a result, malicious Marketplace applications may require more permissions than necessary or have malicious intent.
 35
 36Google clearly states that they are not responsible for any product on the Marketplace that originates from a source other than Google.
 37
 38This rule identifies when the global allow-all setting is enabled for Google Workspace Marketplace applications.
 39
 40#### Possible investigation steps
 41
 42- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
 43- This rule relies on data from `google_workspace.admin`, thus indicating the associated user has administrative privileges to the Marketplace.
 44- Search for `event.action` is `ADD_APPLICATION` to identify applications installed after these changes were made.
 45    - The `google_workspace.admin.application.name` field will help identify what applications were added.
 46- With the user account, review other potentially related events within the last 48 hours.
 47- Re-assess the permissions and reviews of the Marketplace applications to determine if they violate organizational policies or introduce unexpected risks.
 48- With access to the Google Workspace admin console, determine if the application was installed domain-wide or individually by visiting `Apps > Google Workspace Marketplace Apps`.
 49
 50### False positive analysis
 51
 52- Identify the user account associated with this action and assess their administrative privileges with Google Workspace Marketplace.
 53- Google Workspace administrators may intentionally add an application from the marketplace based on organizational needs.
 54    - Follow up with the user who added the application to ensure this was intended.
 55- Verify the application identified has been assessed thoroughly by an administrator.
 56
 57### Response and remediation
 58
 59- Initiate the incident response process based on the outcome of the triage.
 60- Disable or limit the account during the investigation and response.
 61- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
 62    - Identify the account role in the cloud environment.
 63    - Assess the criticality of affected services and servers.
 64    - Work with your IT team to identify and minimize the impact on users.
 65    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
 66    - Identify any regulatory or legal ramifications related to this activity.
 67- 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.
 68- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
 69- Implement security best practices [outlined](https://support.google.com/a/answer/7587183) by Google.
 70- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
 71- 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).
 72
 73## Setup
 74
 75The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 76
 77### Important Information Regarding Google Workspace Event Lag Times
 78- 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.
 79- 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.
 80- By default, `var.interval` is set to 2 hours (2h). Consider changing this interval to a lower value, such as 10 minutes (10m).
 81- See the following references for further information:
 82  - https://support.google.com/a/answer/7061566
 83  - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html"""
 84references = [
 85    "https://support.google.com/a/answer/6089179?hl=en",
 86    "https://www.elastic.co/security-labs/google-workspace-attack-surface-part-one",
 87    "https://www.elastic.co/security-labs/google-workspace-attack-surface-part-two"
 88]
 89risk_score = 47
 90rule_id = "a2795334-2499-11ed-9e1a-f661ea17fbce"
 91severity = "medium"
 92tags = [
 93    "Domain: Cloud",
 94    "Data Source: Google Workspace",
 95    "Use Case: Configuration Audit",
 96    "Tactic: Defense Evasion",
 97    "Resources: Investigation Guide",
 98]
 99timestamp_override = "event.ingested"
100type = "query"
101
102query = '''
103event.dataset:"google_workspace.admin" and event.action:"CHANGE_APPLICATION_SETTING" and event.category:(iam or configuration)
104    and google_workspace.event.type:"APPLICATION_SETTINGS" and google_workspace.admin.application.name:"Google Workspace Marketplace"
105        and google_workspace.admin.setting.name:"Apps Access Setting Allowlist access"  and google_workspace.admin.new_value:"ALLOW_ALL"
106'''
107
108
109[[rule.threat]]
110framework = "MITRE ATT&CK"
111[[rule.threat.technique]]
112id = "T1562"
113name = "Impair Defenses"
114reference = "https://attack.mitre.org/techniques/T1562/"
115[[rule.threat.technique.subtechnique]]
116id = "T1562.001"
117name = "Disable or Modify Tools"
118reference = "https://attack.mitre.org/techniques/T1562/001/"
119
120
121
122[rule.threat.tactic]
123id = "TA0005"
124name = "Defense Evasion"
125reference = "https://attack.mitre.org/tactics/TA0005/"