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 manages its Google Cloud Identity user accounts and directory groups programmatically using automated service accounts and identity provisioning pipelines. The security operations center (SOC) must implement continuous auditing, standardized log parsing, and real-time alerting within Google Security Operations (SecOps / Chronicle) to detect unauthorized or anomalous additions to privileged administrative groups.
Which approach should the security engineer implement to properly standardize the audit logs and trigger real-time alerts on these programmatic identity modifications?
This option suggests deploying local host-based logging tools (OSSEC and Linux auditd) on virtual machines, classifying all audit logs as SYSTEM_AUDIT_LOG_UNCATEGORIZED, and relying on local CIS benchmark scanning scripts to monitor programmatic changes.
SYSTEM_AUDIT_LOG_UNCATEGORIZED bypasses normalized UDM fields (such as principal.user.userid and target.group.product_object_id), preventing automated rule evaluation in the SecOps Detection Engine./etc/audit/auditd.conf), but cannot provide real-time alerting on cloud directory membership changes.The requirement specifically focused on auditing OS-level user modifications (such as commands like usermod or setfacl) on an on-premises Linux directory server.
This option suggests mapping Cloud Identity audit events to process execution UDM types (PROCESS_LAUNCH and PROCESS_TERMINATION) and deploying Cloud IDS (Cloud Intrusion Detection System) with packet mirroring to inspect REST API calls for unauthorized group additions.
PROCESS_LAUNCH and PROCESS_TERMINATION represent operating system process lifecycle events (such as daemon starts or binary executions via execve), not identity management and access control operations. Mapping identity events to process types breaks detection schemas and reporting.The objective were to monitor host-level binary execution anomalies on Linux virtual machine instances running identity synchronization daemons.
This option suggests utilizing Event Threat Detection (ETD) to analyze VPC Flow Logs and Cloud DNS logs to identify Cloud Identity group modifications, followed by configuring VPC firewall rules to mitigate threats.
The organization needed to detect compromised workloads communicating with known external malicious command-and-control servers or mining pools over VPC networks.
Google Security Operations (SecOps / Chronicle) ingests structured and unstructured audit logs, normalizing disparate event schemas into the Unified Data Model (UDM). In UDM, identity lifecycle events (such as ADD_GROUP, ADD_USER, and group membership updates) are mapped to standardized event types (such as GROUP_CREATION or USER_RESOURCE_UPDATE_CONTENT) and schema fields such as principal.user.userid, target.group.product_object_id, and security_result.action.
principal) and the affected group (target).target.group.product_object_id matches sensitive administrative groups and the principal.user.userid is not an approved automation service account or authorized admin.principal.user.userid), target resources (target.group.product_object_id), and execution contexts.Leveraging UDM normalization paired with the SecOps Detection Engine and YARAL rules provides native, schema-aware security monitoring that scales with automated identity operations and delivers sub-minute alerting on unauthorized directory changes.
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