Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
A security engineer is configuring and troubleshooting context-aware access controls for administrative access to resources protected inside a VPC Service Controls perimeter.
The engineer has created Access Context Manager access levels that enforce device posture verification and IP origin restrictions. Different access bindings were applied to multiple Google Groups in Cloud Identity to govern various developer tiers. During security validation, the engineer discovers that a user assigned to both the Security-Core group (which enforces a strict managed device posture) and the General-Auditors group (which only requires a corporate network IP) can successfully invoke Google Cloud APIs on perimeter-protected resources from an unapproved personal device.
Why is this access permitted, and how should the security engineer remediate the issue?
Enforcement groups in Cloud Identity prevent members from voluntarily removing themselves from security-sensitive groups. Security Command Center Event Threat Detection (ETD) monitors Cloud Audit Logs for anomalous actions, such as leaked credentials or brute-force attempts.
OR, leaving the permissive hole intact.The issue was caused by employees deliberately leaving an access group to escape context-aware access requirements.
Access Context Manager access bindings are explicitly built to govern workforce human identities managed in Cloud Identity or Google Workspace, enforcing context-aware access to Google Cloud console and APIs.
The requirement specifically involved enforcing contextual attributes on non-human service accounts accessing APIs via conditional role grants.
VPC Service Controls perimeter rules define the directional network and identity criteria under which clients outside a service perimeter can communicate with protected services inside the perimeter (ingress), or under which protected workloads can call external resources (egress).
AND logic. In fact, access bindings combine multiple applicable levels using OR logic, which explains why the less restrictive condition allowed traffic through.The goal was to control cross-perimeter project-to-project communication where workloads in one perimeter needed to push data to another perimeter.
Access bindings in Google Cloud link Access Context Manager (ACM) access levels directly to user groups or organizational units to enforce context-aware requirements (such as device security posture, geographical location, or corporate IP network) across administrative interfaces like the Google Cloud console and gcloud CLI.
When a user is simultaneously a member of multiple groups that have distinct access bindings applied:
OR semantics.General-Auditors), the overall request is authorized, effectively bypassing the stricter device posture required by the Security-Core binding.To remediate this context-aware policy loophole, security engineers should implement the following architectural best practices:
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated