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.
An enterprise security operations team is configuring continuous threat detection and alerting across their Google Cloud environment to satisfy CIS Google Cloud Computing Platform Benchmark controls. During an audit, Security Command Center (SCC) generates an active OWNER_NOT_MONITORED compliance and security finding across several production projects.
Which configuration must the team implement to continuously monitor unauthorized project ownership modifications and resolve this finding?
roles/owner IAM role, and configure a Cloud Monitoring alert policy with assigned notification channels.Creating a logs-based counter metric coupled with a Cloud Monitoring alert policy establishes continuous, real-time detection for changes made to administrative permissions. It specifically tracks modifications to project-level ownership roles recorded in Cloud Audit Logs.
SetIamPolicy calls handled by cloudresourcemanager.googleapis.com. By filtering for protoPayload.serviceData.policyDelta.bindingDeltas.role="roles/owner" where the action is ADD or REMOVE (as well as ProjectOwnership or projectOwnerInvitee), any grant or revocation of ownership immediately increments the metric.OWNER_NOT_MONITORED finding: Security Command Center's Security Health Analytics detector checks that the project contains a LogsMetric resource with this exact Cloud Resource Manager filter and verifies that an associated alertPolicy exists with active conditions and notificationChannels.This architecture leverages built-in Google Cloud Observability and Security Command Center mechanisms. It requires no third-party software, eliminates batch polling delays, and natively satisfies CIS compliance auditing algorithms.
Cloud Monitoring Uptime Checks periodically send synthetic HTTP, HTTPS, or TCP requests to external or internal service endpoints to measure availability, responsiveness, and service uptime.
roles/owner deltas, and it does not resolve the OWNER_NOT_MONITORED finding.The primary goal was to monitor the network reachability and HTTP latency of a publicly accessible web service or API gateway.
This configuration exports audit logs into a centralized BigQuery dataset and uses BigQuery scheduled queries to periodically evaluate audit entries for sensitive role changes.
LogsMetric resource and Cloud Monitoring for an attached alertPolicy. A BigQuery log sink does not create a metric or alert policy, leaving the OWNER_NOT_MONITORED finding active.The requirement was to perform long-term historical audit reporting, complex forensic data joins, or multi-cloud analytical querying across petabytes of historical IAM logs.
DEFENSE_EVASION_MODIFY_VPC_SERVICE_CONTROL.Event Threat Detection (ETD) is a built-in Security Command Center Premium service that analyzes Cloud Logging streams for security threats and malicious actor behaviors, such as modifying VPC Service Controls perimeters.
OWNER_NOT_MONITORED relates specifically to log metrics and alerting policies for project IAM ownership, not VPC Service Controls modifications (DEFENSE_EVASION_MODIFY_VPC_SERVICE_CONTROL).LogsMetric or alertPolicy resources in Cloud Monitoring that Security Health Analytics validates.roles/owner grants or removals in Cloud Resource Manager.DEFENSE_EVASION_MODIFY_VPC_SERVICE_CONTROL monitors perimeter loosening and exfiltration pathway creation.THREAT class findings, whereas OWNER_NOT_MONITORED is a configuration compliance finding evaluated by Security Health Analytics.The security team needed to automatically detect and revert unauthorized perimeter modifications within VPC Service Controls to prevent defense evasion.
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