Google Professional Cloud Security Engineer Exam Questions

Provision a Cloud NAT Instance:

Cloud NAT (Network Address Translation) allows instances without external IP addresses to access the internet securely.

In the Google Cloud Console, navigate to the VPC Network section and select Cloud NAT.

Create a new Cloud NAT configuration, specifying the VPC and region where your Compute Engine VMs are deployed.

Configure Cloud NAT:

Ensure that the Cloud NAT instance is configured to provide outbound internet connectivity for the VMs in your specified subnet.

This setup allows the VMs to access the internet for package updates and external installations without requiring public IP addresses.

Enable Private Google Access:

Private Google Access allows VMs in a subnet to reach Google APIs and services using internal IP addresses.

In the Google Cloud Console, navigate to the VPC Network section and select Subnets.

Edit the subnet used by your Compute Engine VMs and enable Private Google Access.

Update DevOps Scripts:

Ensure that your DevOps scripts are updated to work with the new network configuration.

Test the build process to confirm that the VMs can access necessary resources and complete the build pipeline successfully.

Cloud NAT Documentation

Private Google Access

The core requirements are: centralized, tamper-proof, long-term (seven years) immutable audit trails for administrative and data access activity.

Centralization: The current logging is fragmented. To centralize, you need to collect logs from across the organization. Cloud Logging sinks configured at the organization level are designed for this purpose. They allow you to route logs from all projects within an organization to a single destination.Extract Reference: 'Aggregated exports allow you to export logs from multiple Google Cloud projects, folders, or your entire organization. An aggregated export can include all logs from all included resources, or you can use queries to include only specific logs.' (Google Cloud documentation: https://cloud.google.com/logging/docs/export/aggregated_exports)

Long-Term Storage (Seven Years): Cloud Logging buckets have default retention periods (e.g., 30 days for Data Access logs, 400 days for Admin Activity logs) which are not sufficient for a seven-year requirement. Cloud Storage is ideal for long-term archival.Extract Reference: 'Cloud Storage is a highly scalable and durable object storage service suitable for archiving large volumes of data for extended periods.' (Google Cloud documentation, general overview of Cloud Storage features)

Tamper-Proof / Immutability: This is a critical requirement for audit trails in financial services under strict regulatory frameworks. Cloud Storage's 'object retention lock' feature provides immutability. Once an object retention lock is set on a bucket, objects within that bucket cannot be deleted or overwritten for a specified duration, ensuring data integrity for compliance purposes.Extract Reference: 'Object Retention Lock helps you meet compliance requirements by preventing data from being deleted or modified for a fixed amount of time or indefinitely. This feature satisfies SEC Rule 17a-4(f), FINRA Rule 4511(c), and CFTC Regulation 1.31(c)-(d) requirements.' (Google Cloud documentation: https://cloud.google.com/storage/docs/bucket-lock)

Let's evaluate the other options:

A . Implement Pub/Sub to stream all audit logs from each project in real-time to an external SIEM: While Pub/Sub can centralize real-time streaming to a SIEM, the solution described does not inherently guarantee tamper-proof storage or 7-year immutability within Google Cloud. The SIEM itself would need to provide those capabilities, which is outside the scope of Google Cloud's direct offering for this specific requirement.

C . Enable Security Command Center across the organization: Security Command Center (SCC) provides centralized visibility into security posture, threats, and compliance. However, SCC is a security management and monitoring platform; it does not serve as the primary long-term, immutable storage for raw audit logs. It consumes information from logs but doesn't store them in a way that meets the 7-year immutable archival requirement.

D . Individually configure Cloud Audit Logs for all Google Cloud services in each project. Store the logs in regional Cloud Logging buckets with 30-day retention policies: This fails on multiple counts: it's not centralized (requires individual configuration), and the 30-day retention in Cloud Logging buckets is far short of the seven-year requirement. It also doesn't explicitly guarantee tamper-proof storage beyond the default logging immutability.

Therefore, option B directly addresses all aspects of the requirement: centralization via organization-level sinks, long-term storage with Cloud Storage, and immutability/tamper-proofing with object retention lock.

Cloud Identity-Aware Proxy (Cloud IAP) provides a way to control access to your web applications and resources running on Google Cloud. It works by verifying the identity of a user trying to access the application and supports multi-factor authentication (MFA). Cloud IAP can restrict access to users on the corporate network and also supports access over the internet securely.

Steps:

Enable Cloud IAP: In the Google Cloud Console, navigate to the IAP section and enable IAP for your web application.

Configure OAuth Consent Screen: Set up the OAuth consent screen to manage how users grant access.

Set Up Authentication: Use Google Identity Platform to manage users and enable two-factor authentication.

Add Users: Grant users access to the application by adding their identities in the IAP settings.

Google Cloud: Identity-Aware Proxy

Setting up IAP

To allow a large number of users to access the GCP Console while keeping the existing Active Directory or LDAP server for identity management, use Google Cloud Directory Sync (GCDS).

Install GCDS:

Download and install Google Cloud Directory Sync from here.

Configure GCDS:

Set up the synchronization by specifying the LDAP server details and the Google domain.

Map the LDAP attributes to Google attributes to ensure user data is synchronized correctly.

Run Synchronization:

Perform an initial synchronization to populate the Google domain with existing users from the LDAP server.

Schedule regular synchronizations to keep the data up-to-date.

Benefits:

Automated Sync: Ensures that user data is consistently updated without manual intervention.

Secure Access: Users can log in to the GCP Console using their existing credentials, enhancing security and user experience.

Google Cloud Directory Sync Documentation

GCDS Administration Guide

Objective: Store and retrieve sensitive configuration data for an application running on Compute Engine.

Solution: Use Secret Manager to securely store and manage access to sensitive configuration data.

Steps:

Step 1: Open the Google Cloud Console.

Step 2: Navigate to the Secret Manager section.

Step 3: Create a new secret and add the sensitive configuration data.

Step 4: Set appropriate IAM policies to control access to the secret.

Step 5: Update the application to retrieve the secret from Secret Manager using the appropriate client libraries or APIs.

Secret Manager provides a secure and centralized way to manage sensitive information, with fine-grained access control and audit logging capabilities.

Secret Manager Documentation

Storing and Accessing Secrets