Professional Cloud Security Engineer Exam (Google Cloud) - Google Cloud

To ensure that a Compute Engine instance does not have access to the internet or to any Google APIs or services, you need to disable the following settings:<br />
Public IP: Disabling the public IP address ensures that the instance does not have a direct connection<br />
to the internet. Without a public IP address, the instance cannot be accessed from or communicate with the internet directly.<br />
Private Google Access: Disabling Private Google Access ensures that the instance does not have<br />
access to Google APIs and services through the internal Google network. Private Google Access allows instances without a public IP to reach Google APIs and services using private IP addresses, but disabling it will block this path. Disabling these settings will effectively isolate the instance from both the public internet and Google's internal API services. Reference Google Cloud VPC Documentation - Overview Configuring Private Google Access Compute Engine Network Overview

Implied IPv4 allow egress rule. An egress rule whose action is allow, destination is 0.0.0.0/0, and priority is the lowest possible (65535) lets any instance send traffic to any destination Implied IPv4 deny ingress rule. An ingress rule whose action is deny, source is 0.0.0.0/0, and priority is the lowest possible (65535) protects all instances by blocking incoming connections to them. https://cloud.google.com/vpc/docs/firewalls?hl=en#default_firewall_rules

Storing secrets securely is crucial for maintaining the integrity and confidentiality of your applications. Here is how you can achieve this using Google Cloud Platform: Encrypt the Secrets: Use Customer-Managed Encryption Keys (CMEK) to encrypt your secrets. CMEK allows you to have greater control over the encryption keys used to protect your data. This ensures that even if the storage medium is compromised, the secrets remain protected by strong encryption. Store in Cloud Storage: Store the encrypted secrets in Google Cloud Storage. Cloud Storage is a secure and scalable object storage service. By using encrypted storage, you can ensure that the secrets are securely stored and can only be accessed by authorized entities. This method provides a secure and managed way to store secrets, ensuring that they are not exposed in plain text within your source code management system. Reference Customer-Managed Encryption Keys (CMEK) Google Cloud Storage Security

"In order to be able to keep using the existing identity management system, identities need to be synchronized between AD and GCP IAM. To do so google provides a tool called Cloud Directory Sync. This tool will read all identities in AD and replicate those within GCP. Once the identities have been replicated then it's possible to apply IAM permissions on the groups. After that you will configure SAML so google can act as a service provider and either you ADFS or other third party tools like Ping or Okta will act as the identity provider. This way you effectively delegate the authentication from Google to something that is under your control."

When creating a secure container image, it is essential to follow best practices to minimize vulnerabilities and ensure the container operates as intended. Here are the two key practices:<br />
Package a Single App as a Container: By packaging only a single application within a container, you<br />
reduce complexity and potential attack surfaces. This practice aligns with the principle of single responsibility, ensuring each container has a clear and focused purpose. Remove Any Unnecessary Tools: Any additional tools or software that are not required by the application should be removed from the container image. This minimizes the number of potential vulnerabilities and reduces the attack surface. A minimal container image also leads to smaller image sizes and faster deployment times. These practices contribute to creating a more secure and efficient container image. Reference Container Security Best Practices Securing Container Images