How the attack works
Google Workspace tells administrators about risky activity through rules and the alert center. System-defined rules are supplied by Google, for example for a suspicious login, a user granted an admin privilege or a suspended user made active. Activity rules, which replaced reporting rules in 2025, are written by the organization on audit log events. A rule can send email to chosen recipients and create an alert in the alert center. Organizations that use Google Security Operations can also connect Workspace to it so that log events are exported continuously.
An attacker who holds an admin account can quiet these channels before the noisy part of an intrusion. They turn a rule off or delete it, change its conditions or actions so that it no longer fires or no longer notifies, replace the recipients of an alert, delete alerts that already sit in the alert center, change the alert center's notification settings or disconnect the export to Google Security Operations. Nothing is taken or changed in user data by any of this. The damage is that the people who would respond are not told.
The Admin audit log records these changes. For alerts it has DELETE_ALERT, ALERT_STATUS_CHANGED with the old and the new value on or off, ALERT_RECEIVERS_CHANGED with the old and the new recipients, and CHANGE_ALERT_CRITERIA. For rules it has DELETE_RULE, RULE_STATUS_CHANGED, RULE_ACTIONS_CHANGED, CHANGE_RULE_CRITERIA and UPDATE_RULE. Organizations that share Workspace data with Google Cloud receive them in Cloud Audit Logs at organization level as Admin Activity entries of admin.googleapis.com. Google's list of methods for Cloud Audit Logs also holds alert center methods, such as alertCenterDeleteAlert, and turnOffChronicleExport for the export. Google's event reference has no entry for those, so the rules for them are written on the method names alone.
What an attacker needs
- An admin account whose role can manage the control in question. Google names the Activity Rules Manage privilege for rules and the Alert Center privilege for the alert center, and requires super administrator privileges to connect Workspace to Google Security Operations.
- Super admins and holders of the prebuilt Services Admin role have full access to the alert center by default.
Impact
Alerts that would have reached the administrators or the security team are not sent, or are removed before anyone reads them. If the export to Google Security Operations is disconnected, a team that works from that platform stops receiving Workspace log events. The attacker gains time. A rule that was edited to never match, or whose recipients were replaced, keeps looking active in the rules list.
Detection rules
Alerts Deleted From the Alert Center in Google Workspace
Detects the deletion of alerts from the alert center of a Google Workspace or Cloud Identity account, one at a time or in a batch (Cloud Audit Logs methods alertCenterDeleteAlert and alertCenterBatchDeleteAlerts). The alert center holds Google's notifications about potential security issues in the domain, such as a suspicious login or a leaked password. An attacker with access to the alert center deletes the alerts their own actions produced before an administrator reads them. Google states that a deleted alert is marked for deletion and removed after 30 days, and that admins can view and recover it during that time with the Recently deleted filter. The method names are in Google's list of Admin audit methods for Cloud Audit Logs under the event type ALERT_CENTER. Google's event reference has no entry for them, so their parameters are not documented and the rule matches the method names alone. The admin is in principalEmail. The entries reach Cloud Audit Logs as Admin Activity entries at organization level, which are always written once Google Workspace data sharing with Google Cloud is enabled, and reach the SIEM only when the organization-level logs are routed to it.
title: Alerts Deleted From the Alert Center in Google Workspace
id: 0f078e58-4990-4411-a99d-712c8ff0cc74
status: experimental
description: >-
Detects the deletion of alerts from the alert center of a Google Workspace
or Cloud Identity account, one at a time or in a batch (Cloud Audit Logs
methods alertCenterDeleteAlert and alertCenterBatchDeleteAlerts). The
alert center holds Google's notifications about potential security issues
in the domain, such as a suspicious login or a leaked password. An
attacker with access to the alert center deletes the alerts their own
actions produced before an administrator reads them. Google states that a
deleted alert is marked for deletion and removed after 30 days, and that
admins can view and recover it during that time with the Recently deleted
filter. The method names are in Google's list of Admin audit methods for
Cloud Audit Logs under the event type ALERT_CENTER. Google's event
reference has no entry for them, so their parameters are not documented
and the rule matches the method names alone. The admin is in
principalEmail. The entries reach Cloud Audit Logs as Admin Activity
entries at organization level, which are always written once Google
Workspace data sharing with Google Cloud is enabled, and reach the SIEM
only when the organization-level logs are routed to it.
references:
- https://docs.cloud.google.com/logging/docs/audit/gsuite-audit-logging
- https://knowledge.workspace.google.com/admin/security/delete-alerts
- https://developers.google.com/workspace/admin/alertcenter/reference/rest/v1beta1/alerts/delete
- https://developers.google.com/workspace/admin/alertcenter/reference/rest/v1beta1/alerts/batchDelete
- https://attack.mitre.org/techniques/T1685/
author: Forestall
date: 2026-11-18
tags:
- attack.defense-impairment
- attack.t1685
logsource:
product: gcp
service: gcp.audit
detection:
selection:
protoPayload.serviceName: admin.googleapis.com
protoPayload.methodName:
- google.admin.AdminService.alertCenterDeleteAlert
- google.admin.AdminService.alertCenterBatchDeleteAlerts
condition: selection
falsepositives:
- Administrators who clear alerts they have handled, and tools that manage alerts through the Alert Center API. Where that is routine, exclude those identities by principalEmail in a filter_* selection. For anyone else, open the alert center with the Recently deleted filter and read what was removed.
level: medium
False positives
- Administrators who clear alerts they have handled, and tools that manage alerts through the Alert Center API. Where that is routine, exclude those identities by principalEmail in a filter_* selection. For anyone else, open the alert center with the Recently deleted filter and read what was removed.
Alert Center Customer Settings Updated in Google Workspace
Detects the Cloud Audit Logs method alertCenterUpdateCustomerSettings of the Admin audit log of a Google Workspace or Cloud Identity account, which Google lists under the event type ALERT_CENTER. The Alert Center API has one method that updates the customer-level settings, and those settings hold the list of notifications, each of which names a Cloud Pub/Sub topic that alerts are published to. Organizations use such a topic to deliver alerts to a SIEM or a response tool. An attacker who removes or replaces the notification stops that delivery while the alert center itself keeps filling. Google's event reference has no entry for this method, so the link to the settings method of the API is made by its name, its parameters are not documented and the rule is written on the method name alone and at a low level. Compare the current settings with your record. The admin is in principalEmail. The entry reaches Cloud Audit Logs as an Admin Activity entry at organization level, which is always written once Google Workspace data sharing with Google Cloud is enabled, and reaches the SIEM only when the organization-level logs are routed to it.
title: Alert Center Customer Settings Updated in Google Workspace
id: 842cdc86-3110-490b-9d0b-b474f37dd434
status: experimental
description: >-
Detects the Cloud Audit Logs method alertCenterUpdateCustomerSettings of
the Admin audit log of a Google Workspace or Cloud Identity account, which
Google lists under the event type ALERT_CENTER. The Alert Center API has
one method that updates the customer-level settings, and those settings
hold the list of notifications, each of which names a Cloud Pub/Sub topic
that alerts are published to. Organizations use such a topic to deliver
alerts to a SIEM or a response tool. An attacker who removes or replaces
the notification stops that delivery while the alert center itself keeps
filling. Google's event reference has no entry for this method, so the
link to the settings method of the API is made by its name, its
parameters are not documented and the rule is written on the method name
alone and at a low level. Compare the current settings with your record.
The admin is in principalEmail. The entry reaches Cloud Audit Logs as an
Admin Activity entry at organization level, which is always written once
Google Workspace data sharing with Google Cloud is enabled, and reaches
the SIEM only when the organization-level logs are routed to it.
references:
- https://docs.cloud.google.com/logging/docs/audit/gsuite-audit-logging
- https://developers.google.com/workspace/admin/alertcenter/reference/rest/v1beta1/TopLevel/updateSettings
- https://developers.google.com/workspace/admin/alertcenter/reference/rest/v1beta1/Settings
- https://attack.mitre.org/techniques/T1685/
author: Forestall
date: 2026-11-18
tags:
- attack.defense-impairment
- attack.t1685
logsource:
product: gcp
service: gcp.audit
detection:
selection:
protoPayload.serviceName: admin.googleapis.com
protoPayload.methodName: google.admin.AdminService.alertCenterUpdateCustomerSettings
condition: selection
falsepositives:
- The team that integrates the alert center with a SIEM or a response tool setting up or changing the notification topic. This is done rarely. Verify each event with that team and check that alerts still arrive.
level: low
False positives
- The team that integrates the alert center with a SIEM or a response tool setting up or changing the notification topic. This is done rarely. Verify each event with that team and check that alerts still arrive.
Alert or Rule Criteria, Actions or Receivers Changed in Google Workspace
Detects five Admin audit events of a Google Workspace or Cloud Identity account that change what an alert or a rule looks for or whom it tells: the criteria of an alert changed (CHANGE_ALERT_CRITERIA), the receivers of an alert changed (ALERT_RECEIVERS_CHANGED, with the old and the new list in OLD_VALUE and NEW_VALUE), the criteria of a rule changed (CHANGE_RULE_CRITERIA), the actions of a rule changed (RULE_ACTIONS_CHANGED) and a rule updated (UPDATE_RULE). A rule whose conditions can no longer match, or whose notification goes to a different mailbox, still looks active in the rules list. Google's help describes turning an alert on or off for a rule as an edit of the rule's actions that ends with an update of the rule, and its reference does not say which of these events that edit writes, so the rule covers all of them. For the criteria and action events Google documents only the name of the alert or rule (ALERT_NAME, RULE_NAME in protoPayload.metadata), not what was changed, so compare the rule with your record. The entries reach Cloud Audit Logs as Admin Activity entries at organization level, which are always written once Google Workspace data sharing with Google Cloud is enabled, and reach the SIEM only when the organization-level logs are routed to it.
title: Alert or Rule Criteria, Actions or Receivers Changed in Google Workspace
id: 41419234-56df-4d60-b88b-8f8b77fb5aae
status: experimental
description: >-
Detects five Admin audit events of a Google Workspace or Cloud Identity
account that change what an alert or a rule looks for or whom it tells:
the criteria of an alert changed (CHANGE_ALERT_CRITERIA), the receivers of
an alert changed (ALERT_RECEIVERS_CHANGED, with the old and the new list
in OLD_VALUE and NEW_VALUE), the criteria of a rule changed
(CHANGE_RULE_CRITERIA), the actions of a rule changed
(RULE_ACTIONS_CHANGED) and a rule updated (UPDATE_RULE). A rule whose
conditions can no longer match, or whose notification goes to a different
mailbox, still looks active in the rules list. Google's help describes
turning an alert on or off for a rule as an edit of the rule's actions
that ends with an update of the rule, and its reference does not say
which of these events that edit writes, so the rule covers all of them.
For the criteria and action events Google documents only the name of the
alert or rule (ALERT_NAME, RULE_NAME in protoPayload.metadata), not what
was changed, so compare the rule with your record. The entries reach Cloud
Audit Logs as Admin Activity entries at organization level, which are
always written once Google Workspace data sharing with Google Cloud is
enabled, and reach the SIEM only when the organization-level logs are
routed to it.
references:
- https://docs.cloud.google.com/logging/docs/audit/gsuite-audit-logging
- https://developers.google.com/workspace/admin/reports/v1/appendix/activity/admin-domain-settings
- https://knowledge.workspace.google.com/admin/security/use-rules-to-turn-alerts-on-or-off
- https://attack.mitre.org/techniques/T1685/
author: Forestall
date: 2026-11-18
tags:
- attack.defense-impairment
- attack.t1685
logsource:
product: gcp
service: gcp.audit
detection:
selection:
protoPayload.serviceName: admin.googleapis.com
protoPayload.methodName:
- google.admin.AdminService.changeAlertCriteria
- google.admin.AdminService.alertReceiversChanged
- google.admin.AdminService.changeRuleCriteria
- google.admin.AdminService.ruleActionsChanged
- google.admin.AdminService.updateRule
condition: selection
falsepositives:
- Routine tuning of rules, which is the normal use of these events. In organizations that edit rules often, exclude the administrators who run them by principalEmail in a filter_* selection and review changes by anyone else.
- Changes that add recipients or widen the conditions match as well. Read the old and the new receivers in the event parameters.
level: low
False positives
- Routine tuning of rules, which is the normal use of these events. In organizations that edit rules often, exclude the administrators who run them by principalEmail in a filter_* selection and review changes by anyone else.
- Changes that add recipients or widen the conditions match as well. Read the old and the new receivers in the event parameters.
Alert or Rule Deleted or Its Status Changed in Google Workspace
Detects four Admin audit events of a Google Workspace or Cloud Identity account that remove an alert or a rule or switch it: an alert deleted (DELETE_ALERT), the status of an alert changed (ALERT_STATUS_CHANGED, with OLD_VALUE and NEW_VALUE of on or off), a rule deleted (DELETE_RULE) and the status of a rule changed (RULE_STATUS_CHANGED). An attacker with admin rights turns alerting off before the part of an intrusion that would trigger it. The alert or rule is named in the event parameter ALERT_NAME or RULE_NAME in protoPayload.metadata and the admin is in principalEmail. The status events are written for a change in either direction, because the method name does not carry it, so read NEW_VALUE before acting. The entries reach Cloud Audit Logs as Admin Activity entries at organization level, which are always written once Google Workspace data sharing with Google Cloud is enabled, and reach the SIEM only when the organization-level logs are routed to it.
title: Alert or Rule Deleted or Its Status Changed in Google Workspace
id: 6aea434e-733f-4429-82ba-729e62ebf5c1
status: experimental
description: >-
Detects four Admin audit events of a Google Workspace or Cloud Identity
account that remove an alert or a rule or switch it: an alert deleted
(DELETE_ALERT), the status of an alert changed (ALERT_STATUS_CHANGED, with
OLD_VALUE and NEW_VALUE of on or off), a rule deleted (DELETE_RULE) and
the status of a rule changed (RULE_STATUS_CHANGED). An attacker with admin
rights turns alerting off before the part of an intrusion that would
trigger it. The alert or rule is named in the event parameter ALERT_NAME
or RULE_NAME in protoPayload.metadata and the admin is in principalEmail.
The status events are written for a change in either direction, because
the method name does not carry it, so read NEW_VALUE before acting. The
entries reach Cloud Audit Logs as Admin Activity entries at organization
level, which are always written once Google Workspace data sharing with
Google Cloud is enabled, and reach the SIEM only when the
organization-level logs are routed to it.
references:
- https://docs.cloud.google.com/logging/docs/audit/gsuite-audit-logging
- https://developers.google.com/workspace/admin/reports/v1/appendix/activity/admin-domain-settings
- https://knowledge.workspace.google.com/admin/reports/view-and-edit-system-defined-rules
- https://attack.mitre.org/techniques/T1685/
author: Forestall
date: 2026-11-18
tags:
- attack.defense-impairment
- attack.t1685
logsource:
product: gcp
service: gcp.audit
detection:
selection:
protoPayload.serviceName: admin.googleapis.com
protoPayload.methodName:
- google.admin.AdminService.deleteAlert
- google.admin.AdminService.alertStatusChanged
- google.admin.AdminService.deleteRule
- google.admin.AdminService.ruleStatusChanged
condition: selection
falsepositives:
- A status change that turns an alert or rule on matches as well. Read the new value in the event parameters.
- Clean-up and tuning of rules by the administrators who run them. Verify each deletion and each rule that was turned off against a change record, and give priority to rules about sign-ins, admin privileges and data sharing.
level: medium
False positives
- A status change that turns an alert or rule on matches as well. Read the new value in the event parameters.
- Clean-up and tuning of rules by the administrators who run them. Verify each deletion and each rule that was turned off against a change record, and give priority to rules about sign-ins, admin privileges and data sharing.
Log Export to Google Security Operations Turned Off in Google Workspace
Detects the Cloud Audit Logs method turnOffChronicleExport of the Admin audit log of a Google Workspace or Cloud Identity account. Google lists it under the event type CHRONICLE_SETTINGS next to turnOnChronicleExport. Google's help describes connecting Workspace to Google Security Operations so that log events are exported continuously, and disconnecting it again on the Data integrations page of the Admin console. A team that detects from that platform stops receiving Workspace events once the export is off. Google's event reference has no entry for this method, so the link between the method and the Disconnect action is made by its name, its parameters are not documented and the rule is set one level lower than a confirmed log source being switched off would deserve. The admin is in principalEmail. This rule reads Cloud Audit Logs, which is a separate path from the export it watches. The entry reaches Cloud Audit Logs as an Admin Activity entry at organization level, which is always written once Google Workspace data sharing with Google Cloud is enabled, and reaches the SIEM only when the organization-level logs are routed to it.
title: Log Export to Google Security Operations Turned Off in Google Workspace
id: 526cd2b8-9367-4f8c-bda7-bdfb213b7ab5
status: experimental
description: >-
Detects the Cloud Audit Logs method turnOffChronicleExport of the Admin
audit log of a Google Workspace or Cloud Identity account. Google lists it
under the event type CHRONICLE_SETTINGS next to turnOnChronicleExport.
Google's help describes connecting Workspace to Google Security
Operations so that log events are exported continuously, and
disconnecting it again on the Data integrations page of the Admin
console. A team that detects from that platform stops receiving Workspace
events once the export is off. Google's event reference has no entry for
this method, so the link between the method and the Disconnect action is
made by its name, its parameters are not documented and the rule is set
one level lower than a confirmed log source being switched off would
deserve. The admin is in principalEmail. This rule reads Cloud Audit
Logs, which is a separate path from the export it watches. The entry
reaches Cloud Audit Logs as an Admin Activity entry at organization level,
which is always written once Google Workspace data sharing with Google
Cloud is enabled, and reaches the SIEM only when the organization-level
logs are routed to it.
references:
- https://docs.cloud.google.com/logging/docs/audit/gsuite-audit-logging
- https://knowledge.workspace.google.com/admin/reports/export-log-events-to-google-security-operations-to-monitor-insider-risk
- https://attack.mitre.org/techniques/T1685/002/
author: Forestall
date: 2026-11-18
tags:
- attack.defense-impairment
- attack.t1685.002
logsource:
product: gcp
service: gcp.audit
detection:
selection:
protoPayload.serviceName: admin.googleapis.com
protoPayload.methodName: google.admin.AdminService.turnOffChronicleExport
condition: selection
falsepositives:
- A planned move to another log pipeline or the end of a Google Security Operations subscription. The export is set up once and rarely touched, so verify every event with the team that owns the SIEM.
level: medium
False positives
- A planned move to another log pipeline or the end of a Google Security Operations subscription. The export is set up once and rarely touched, so verify every event with the team that owns the SIEM.
Detection logic
Patterns that need more than one event, a baseline or knowledge of your own environment. Each is a hypothesis to build and tune in your SIEM, not a ready rule.
Alert or rule turned off and turned on again by the same admin
An attacker who wants no trace in the configuration turns an alert or a rule off, acts, and turns it on again. Afterwards the rules page looks as it did before. The two opposite status changes for the same alert or rule, with other admin actions in between, are the trace.
- A
google.admin.AdminService.alertStatusChangedorruleStatusChangedentry. Note the event parameterALERT_NAMEorRULE_NAME, the values inOLD_VALUEandNEW_VALUE, and the admin inauthenticationInfo.principalEmail. - Within 24 hours, a second status change for the same
ALERT_NAMEorRULE_NAMEwhoseNEW_VALUEequals theOLD_VALUEof the first. - Collect the other
admin.googleapis.comentries of the same admin between the two events and review them.
Eventsgoogle.admin.AdminService.alertStatusChangedgoogle.admin.AdminService.ruleStatusChanged
LimitsAn admin who tests a rule or quiets it during planned maintenance produces the same pair. The 24 hours are a starting point. An attacker who leaves the rule off, or who edits its conditions and never touches the status, does not match.
Triage
- Read the event parameters in protoPayload.metadata. ALERT_NAME or RULE_NAME names the alert or rule. For a status change, OLD_VALUE and NEW_VALUE give the direction. For a change of receivers they hold the old and the new recipients.
- Decide what the rule or alert was for. A rule about suspicious logins, admin privilege grants, password leaks or data sharing matters more than one about license usage.
- Identify the admin who made the change (principalEmail), confirm it with that person through a second channel and check the recent sign-ins of that account.
- For alerts deleted from the alert center, open the alert center with the Recently deleted filter and read what was removed. Deleted alerts stay there for 30 days.
- Review what the same admin did in the hours after the change, such as role assignments, password resets, 2-Step Verification settings, app access and mail routing.
Response
Once the attack is confirmed:
- Turn the rule or alert back on, restore its conditions, actions and recipients, and create deleted rules again from your record.
- Recover the alerts that were deleted from the alert center within the 30 days Google keeps them, and investigate each one as if it had just arrived.
- Reconnect the export to Google Security Operations if it was disconnected. Google states that it can take up to 24 hours before data is exported again, so read the events of the gap from the audit log directly.
- Secure the admin account that made the change. Reset its password, reset its sign-in cookies so that existing sessions end, and review its 2-Step Verification methods and admin roles.
- Go through the Admin audit log and the sign-in log for the whole time the control was off, starting with the actions of the same admin, and reverse what was not approved.
Mitigation
- Give the privileges for rules, the alert center and reporting data integrations only to the administrators who run them, and keep super admins and Services Admins few.
- Send rule notifications to a group mailbox that several people read, so that one changed recipient is noticed, and review the recipients of important rules regularly.
- Share Workspace data with Google Cloud and route the organization-level audit logs to the SIEM. The changes on this page are Admin Activity entries, so a detection in the SIEM does not depend on the alerts inside Workspace.
- Keep a record of the rules that must be on and compare the rules page with it. Google lists a system-defined rule as Inactive when its alerts are turned off.
- Monitor the export itself from the receiving side, with an alert in the SIEM when Workspace events stop arriving.
Frequently asked questions
Are these changes still recorded when alerting in Google Workspace is turned off?
Yes. Turning off a rule, deleting an alert or changing recipients is itself an administrator action, and the Admin audit log records it. With Google Workspace data sharing enabled, these entries reach Cloud Audit Logs as Admin Activity entries, which are always written. A detection in a SIEM that reads those logs keeps working after the alerts inside Workspace have been silenced.
Does the rule tell whether an alert or rule was turned off or turned on?
No. The status events are written for a change in either direction and the method name is the same. For alerts Google documents the values on and off in `OLD_VALUE` and `NEW_VALUE`. For rules it documents the two parameters without listing their values. Read them in the event parameters in `protoPayload.metadata` before acting.
Can alerts deleted from the alert center be recovered?
Yes, for a time. Google states that deleted alerts have a 30-day grace period before they are permanently removed. During those 30 days admins can view them with the Recently deleted filter and recover them. An attacker who deletes alerts therefore hides them from the default view and does not destroy them at once.
Which events on this page are documented by name only?
The alert center methods and the method for the Google Security Operations export appear in Google's list of Admin audit methods for Cloud Audit Logs, under the event types `ALERT_CENTER` and `CHRONICLE_SETTINGS`. Google's event reference for the Admin audit log has no entry that describes them or their parameters. The rules for them match the method name and are set to a lower level for that reason.
References
- MITRE ATT&CK T1685: Disable or Modify Tools
- MITRE ATT&CK T1685.002: Disable or Modify Tools: Disable or Modify Cloud Log
- Audit logs for Google Workspace (Cloud Audit Logs)
- Admin audit events: domain settings (alert and rule events)
- View and edit system-defined rules
- Admin access to reporting rules and activity rules
- Use rules to turn alerts on or off
- Delete alerts (alert center)
- Grant access to the alert center
- Alert Center API: Settings (notifications)
- Export log events to Google Security Operations