Professional-Cloud-Security-Engineer Exam Dumps - Google Cloud Certified - Professional Cloud Security Engineer

Setting up separate service perimeters for dev, staging, and prod environments allows for more granular control and monitoring. Automating the addition of new projects to the respective perimeters ensures that all projects are consistently secured without manual intervention.

Steps:

Set Up Service Perimeters: Use Access Context Manager to define and configure three separate service perimeters for dev, staging, and prod.

Deploy Monitoring Function: Create a Cloud Function that monitors the "implementation" folder for new projects using Stackdriver (Cloud Monitoring) and Cloud Pub/Sub.

Automate Perimeter Updates: Configure the Cloud Function to execute Terraform scripts that automatically add new projects to the appropriate service perimeter.

References:

Google Cloud: Access Context Manager

Service perimeter automation

Objective: You want to limit the images that can be used as the source for boot disks to a set of images stored in a dedicated project.

Solution: Use the Organization Policy Service.

Steps:

Step 1: Open the Google Cloud Console.

Step 2: Navigate to the Organization Policies page.

Step 3: Create a new policy by clicking on "Create Policy".

Step 4: Select the constraint compute.trustedimageProjects.

Step 5: Set the policy to ALLOW and specify the project ID where the trusted images are stored in the whitelist.

Step 6: Save and apply the policy.

By creating a compute.trustedimageProjects constraint at the organization level and specifying the trusted project in the allow list, you ensure that only images from this project can be used for boot disks across the organization.

References:

GCP Organization Policy Service Documentation

Compute Trusted Image Projects Constraint

Challenge:

Ensuring secure access to Google Cloud resources from GitHub Actions CI/CD pipelines without directly managing service account keys.

Workload Identity Federation:

Allows for the delegation of access to Google Cloud resources based on federated identities, such as those from GitHub.

Benefits:

This approach eliminates the need to manage service account keys, reducing the risk of key leakage.

It leverages GitHub's identity provider capabilities to authenticate and authorize access.

Steps to Configure Workload Identity Federation:

Step 1: Create a workload identity pool in Google Cloud.

Step 2: Add GitHub as an identity provider within the pool.

Step 3: Configure the necessary permissions and bindings for the identity pool to allow GitHub Actions to access Google Cloud resources.

Step 4: Update the GitHub Actions workflow to use the identity federation for authentication.

References:

Workload Identity Federation

Configuring Workload Identity Federation with GitHub

To ensure that an external user cannot gain access to an internal application on Google App Engine even if an employee’s password is compromised, configure Cloud Identity-Aware Proxy (IAP).

Enable IAP:

Go to the Cloud Console, navigate to the App Engine application, and select "Identity-Aware Proxy".

Enable IAP for the application.

Configure Access Policies:

Set up access policies to restrict who can access the application.

Use IAM roles to grant access only to specific users or groups.

Enforce Authentication:

IAP enforces Google authentication, ensuring that users must log in with their GSuite credentials.

Enable Multi-Factor Authentication (MFA):

Enforce 2FA for all GSuite users to add an extra layer of security.

Advantages:

Protection against Compromised Credentials: Even if passwords are compromised, attackers cannot access the application without passing IAP authentication.

Centralized Access Management: Easily manage and monitor access through IAM and IAP policies.

References:

Identity-Aware Proxy Overview

Setting up IAP

https://cloud.google.com/load-balancing/docs/ssl - SSL Proxy Load Balancing is a reverse proxy load balancer that distributes SSL traffic coming from the internet to virtual machine (VM) instances in your Google Cloud VPC network.

The Standard Tier network only provides regional load balancing, while the Premium Tier supports global load balancing with a single anycast IP address. To distribute requests across multiple regions, you need to use the Premium Tier and update the load balancer configuration accordingly.

Steps:

Upgrade to Premium Tier: Update the load balancer to use the Premium Tier network in the Google Cloud Console.

Add New Instance Group: Add the instance group in the new region (us-east-2) to the backend configuration of the existing load balancer.

Verify Configuration: Ensure that the frontend configuration of the load balancer uses a single external IP address for global distribution.

References:

Google Cloud: Global load balancing

Objective: Identify the layers of the stack the customer shares responsibility for in a shared security responsibility model for IaaS.

Solution: Understand the shared responsibility model.

Explanation:

Network Security: Customers are responsible for configuring network security, such as setting up firewalls, managing VPCs, and ensuring secure network traffic.

Access Policies: Customers are responsible for managing access policies, including IAM roles and permissions, to ensure only authorized users can access resources.

In IaaS, the cloud provider is typically responsible for the underlying infrastructure, while the customer is responsible for securing their applications and data on the cloud.

References:

Shared Responsibility Model

Google Cloud Security Overview