How the attack works
Context-Aware Access is the conditional access control of Google Workspace and Cloud Identity. An administrator defines context conditions, which the Admin console used to call access levels, on attributes such as user identity, location, device security status and IP address. Policies then assign those conditions to apps for an organizational unit or a group. A policy is either Active, which enforces it, or in Monitor mode, which only simulates it. The feature as a whole can be turned on and off.
An organization that requires a company device or the corporate network for Gmail, Drive or the Admin console relies on these policies to make a stolen password or session less useful. An attacker with the right admin privileges removes that reliance. They turn Context-Aware Access off, set a policy from Active to Monitor, remove a context condition from an app or change the assignment for the organizational unit their target is in. The user accounts and their 2-Step Verification settings stay untouched, so the change is easy to miss.
The Admin audit log records TOGGLE_CAA_ENABLEMENT when Context-Aware Access is turned on or off and CHANGE_CAA_APP_ASSIGNMENTS when the access level assignment of an app changes, with the app, the target organizational unit or group, the mode and the old and new access levels in its parameters. 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 changeCaaDefaultAssignments, which its event reference does not describe. Context conditions are resources shared with Google Cloud and can also be changed there, which these Admin audit events do not show.
What an attacker needs
- An admin account with the Data security privileges for access level and rule management, or a super admin account.
- An organization that uses Context-Aware Access. It is available in certain editions only, which Google lists on its help pages.
Impact
The conditions that tied access to a managed device, a network or a location stop applying, for one app and one group or for the whole organization. Stolen passwords and sessions that the policy had made useless work again from anywhere. Google states that turning the feature off can take up to 24 hours to take full effect, while deleted policies and context conditions stop applying immediately.
Detection rules
Context-Aware Access Assignments Changed in Google Workspace
Detects a change to the Context-Aware Access assignments of a Google Workspace or Cloud Identity account. The Admin audit event CHANGE_CAA_APP_ASSIGNMENTS is written when the access level assignment of an app changes. Its parameters in protoPayload.metadata name the app (APPLICATION_NAME), the organizational unit or group it applies to (TARGET_ENTITY_TYPE, TARGET_ENTITY_NAME), the mode (MODE, with the values ACTIVE and MONITOR) and the old and new access levels and enforcement endpoints. A policy set to Monitor mode, or one that lost its context conditions, no longer refuses access. The rule also matches the Cloud Audit Logs method changeCaaDefaultAssignments, which Google lists next to it but does not describe in its event reference, so for that method the rule rests on the name alone. The rule fires on ANY change, including one that adds a condition or switches a policy to Active, so read the parameters before acting. 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: Context-Aware Access Assignments Changed in Google Workspace
id: 276e726e-ad88-46bd-ae96-65939eba8bf3
status: experimental
description: >-
Detects a change to the Context-Aware Access assignments of a Google
Workspace or Cloud Identity account. The Admin audit event
CHANGE_CAA_APP_ASSIGNMENTS is written when the access level assignment of
an app changes. Its parameters in protoPayload.metadata name the app
(APPLICATION_NAME), the organizational unit or group it applies to
(TARGET_ENTITY_TYPE, TARGET_ENTITY_NAME), the mode (MODE, with the values
ACTIVE and MONITOR) and the old and new access levels and enforcement
endpoints. A policy set to Monitor mode, or one that lost its context
conditions, no longer refuses access. The rule also matches the Cloud
Audit Logs method changeCaaDefaultAssignments, which Google lists next to
it but does not describe in its event reference, so for that method the
rule rests on the name alone. The rule fires on ANY change, including one
that adds a condition or switches a policy to Active, so read the
parameters before acting. 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://developers.google.com/workspace/admin/reports/v1/appendix/activity/admin-security-settings
- https://knowledge.workspace.google.com/admin/security/assign-context-aware-access-levels-to-apps
- https://attack.mitre.org/techniques/T1556/009/
author: Forestall
date: 2026-11-18
tags:
- attack.defense-impairment
- attack.persistence
- attack.credential-access
- attack.t1556.009
logsource:
product: gcp
service: gcp.audit
detection:
selection:
protoPayload.serviceName: admin.googleapis.com
protoPayload.methodName:
- google.admin.AdminService.changeCaaAppAssignments
- google.admin.AdminService.changeCaaDefaultAssignments
condition: selection
falsepositives:
- Changes that tighten access match as well, for example a new condition on an app or a policy moved from Monitor to Active.
- Rollouts and tuning by the team that runs the policies, which change several assignments in one session. Verify each change that removes a condition or sets a policy to Monitor mode against a change record.
level: medium
False positives
- Changes that tighten access match as well, for example a new condition on an app or a policy moved from Monitor to Active.
- Rollouts and tuning by the team that runs the policies, which change several assignments in one session. Verify each change that removes a condition or sets a policy to Monitor mode against a change record.
Context-Aware Access Turned On or Off in Google Workspace
Detects Context-Aware Access being turned on or off for a Google Workspace or Cloud Identity account (Admin audit event TOGGLE_CAA_ENABLEMENT, rendered as "Context Aware Access has been {NEW_VALUE}"). While the feature is off, the policies that tie app access to a managed device, a network or a location are not enforced. The rule fires on a change in EITHER direction, because the method name does not carry it, and Google's reference does not list the values of NEW_VALUE. Read the parameter in protoPayload.metadata. The admin is in principalEmail. Google states that turning the feature off can take up to 24 hours to take full effect. 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: Context-Aware Access Turned On or Off in Google Workspace
id: 66f3bb24-bb9e-44ff-8a0a-278fd3237d32
status: experimental
description: >-
Detects Context-Aware Access being turned on or off for a Google Workspace
or Cloud Identity account (Admin audit event TOGGLE_CAA_ENABLEMENT,
rendered as "Context Aware Access has been {NEW_VALUE}"). While the
feature is off, the policies that tie app access to a managed device, a
network or a location are not enforced. The rule fires on a change in
EITHER direction, because the method name does not carry it, and Google's
reference does not list the values of NEW_VALUE. Read the parameter in
protoPayload.metadata. The admin is in principalEmail. Google states that
turning the feature off can take up to 24 hours to take full effect. 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/reports/v1/appendix/activity/admin-security-settings
- https://knowledge.workspace.google.com/admin/security/deploy-context-aware-access
- https://attack.mitre.org/techniques/T1556/009/
author: Forestall
date: 2026-11-18
tags:
- attack.defense-impairment
- attack.persistence
- attack.credential-access
- attack.t1556.009
logsource:
product: gcp
service: gcp.audit
detection:
selection:
protoPayload.serviceName: admin.googleapis.com
protoPayload.methodName: google.admin.AdminService.toggleCaaEnablement
condition: selection
falsepositives:
- The first activation of Context-Aware Access at the end of a rollout, which matches as well.
- An administrator who turns the feature off to stop a policy that locks users out, as Google's deployment guide describes. The switch is used rarely, so verify every event with the admin who made it and check that the feature was turned on again.
level: high
False positives
- The first activation of Context-Aware Access at the end of a rollout, which matches as well.
- An administrator who turns the feature off to stop a policy that locks users out, as Google's deployment guide describes. The switch is used rarely, so verify every event with the admin who made it and check that the feature was turned on again.
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.
Policy for an app and a target switched from Active to Monitor
Setting a policy to Monitor mode stops enforcement while the policy stays in the list. The assignment event carries the mode, but one event cannot tell a new policy that starts in Monitor mode from an enforced policy that was switched back. Comparing with the previous event for the same app and target can.
- Take each
google.admin.AdminService.changeCaaAppAssignmentsentry and read the event parametersAPPLICATION_NAME,TARGET_ENTITY_TYPE,TARGET_ENTITY_NAMEandMODE. - Find the previous entry with the same
APPLICATION_NAMEandTARGET_ENTITY_NAME. - Raise the entry when its
MODEisMONITORand the previous one wasACTIVE, with the admin fromauthenticationInfo.principalEmail.
Eventsgoogle.admin.AdminService.changeCaaAppAssignments
LimitsThe comparison needs the earlier event, so it cannot judge policies that were set before your logs begin. Google documents the parameters and the two mode values but not every case in which the event is written, so test it against a change you make yourself. An admin who pauses a policy that blocks users by mistake matches as well.
Triage
- For the enablement event, read NEW_VALUE in the event parameters in protoPayload.metadata to see whether the feature was turned on or off.
- For an assignment change, read APPLICATION_NAME, TARGET_ENTITY_TYPE and TARGET_ENTITY_NAME for the app and the organizational unit or group, MODE for ACTIVE or MONITOR, and the old and new values of the access levels and enforcement endpoints.
- 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.
- Find out who is in the affected organizational unit or group. A change that covers administrators, or one account that was moved there shortly before, deserves more attention.
- Review sign-ins and activity for the affected apps after the change for devices, networks or countries the policy would have refused.
Response
Once the attack is confirmed:
- Turn Context-Aware Access back on, set the policy back to Active and restore its context conditions and assignments from your record.
- Check the context conditions themselves in the Admin console and in Access Context Manager, because loosening a condition has the same effect as removing the policy.
- 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.
- For the time the control was weakened, review the sign-ins of the users in scope and reset the passwords and sign-in cookies of accounts that were used from places the policy would have blocked.
- Review what else the same admin changed, such as 2-Step Verification settings, session length, app access and admin roles.
Mitigation
- Turn on multi-party approval for Context-Aware Access settings where your edition offers it, so that a change needs a second administrator.
- Give the Data security privileges for access level and rule management only to the administrators who run the policies, and keep super admins few.
- Keep a record of the policies, their mode and their assignments, and compare the Context-Aware Access page with it regularly.
- Restrict who can change access levels in Google Cloud as well, because context conditions are shared between the Admin console and Access Context Manager.
- Share Workspace data with Google Cloud and route the organization-level audit logs to the SIEM.
Frequently asked questions
Does the rule show whether Context-Aware Access was turned off or turned on?
No. The same event is written in both directions. Google renders it as Context Aware Access has been followed by the new value, which is in the event parameter `NEW_VALUE` in `protoPayload.metadata`. Google's reference does not list the possible values, so read the parameter in the entry. Turning the feature on is rare as well and worth a look.
What does it mean when a Context-Aware Access policy is switched from Active to Monitor?
Monitor mode simulates a policy without blocking anyone. Google recommends it for testing a new policy before enforcement. A policy that is switched back from Active to Monitor still appears in the list with its conditions and apps, but it no longer refuses access. The mode is in the parameter `MODE` of the assignment event, with the values ACTIVE and MONITOR.
How quickly does turning Context-Aware Access off take effect?
Google states that after the feature is turned off it can take up to 24 hours to turn off fully, and that previous access policies might still affect users during that time. Deleted policies and context conditions stop applying immediately. Do not read the delay as protection, because the attacker can remove a policy or a condition as well.
Do these events show changes to the context conditions themselves?
No. They cover turning the feature on or off and changing assignments. Google describes policies and context conditions as resources that are shared with Google Cloud and can be created in the Admin console, the Google Cloud console, the Google Cloud APIs and the SDK. Changes made on the Google Cloud side are recorded in the audit logs of Access Context Manager.
References
- MITRE ATT&CK T1556.009: Modify Authentication Process: Conditional Access Policies
- About Context-Aware Access
- Deploy Context-Aware Access (Monitor mode, turning the feature on and off)
- Create Context-Aware Access policies
- Manage Context-Aware Access policies and context conditions
- Audit logs for Google Workspace (Cloud Audit Logs)
- Admin audit events: security settings (TOGGLE_CAA_ENABLEMENT, CHANGE_CAA_APP_ASSIGNMENTS)
- Multi-party approval for sensitive actions
- Access Context Manager audit logging