Professional-Cloud-Security-Engineer Dumps with Practice Exam Questions Answers

To ensure that only trusted container images are deployed on Cloud Run, you can implement Binary Authorization, which is a deploy-time security control that ensures only trusted images are used.

Set Up Binary Authorization:

Navigate to the Google Cloud Console.

Go to Security > Binary Authorization.

Configure the policy to include attestors that verify your trusted images.

Enable Binary Authorization on Cloud Run:

Go to the Cloud Run service.

Enable Binary Authorization on your existing Cloud Run services by selecting the appropriate Binary Authorization policy.

Set Organization Policy:

Go to the Organization Policies page in the Google Cloud Console.

Add a constraint for constraints/run.allowedBinaryAuthorizationPolicies.

Specify the list of allowed Binary Authorization policy names to enforce across your organization.

These steps ensure that any container image deployed on Cloud Run is validated against the specified Binary Authorization policies, preventing untrusted images from being deployed.

Binary Authorization Documentation

Enabling Binary Authorization on Cloud Run

To ensure user-uploaded comments and product reviews do not include sensitive data before publication, use the Cloud Data Loss Prevention (DLP) API.

Enable DLP API:

Go to the Cloud Console and navigate to APIs & Services > Library.

Search for "Data Loss Prevention API" and enable it.

Configure DLP API:

Create an inspection template specifying the types of sensitive data to detect.

Set up de-identification templates if you want to redact or mask sensitive data.

Implement DLP in Application:

Use the Google Cloud DLP Client Library for the desired programming language.

Send the text data to the DLP API for inspection before saving or publishing.

from google.cloud import dlp_v2 dlp_client = dlp_v2.DlpServiceClient() parent = f"projects/{project_id}" item = {"value": "User comment text here"} inspect_config = {"info_types": [{"name": "PERSON_NAME"}, {"name": "CREDIT_CARD_NUMBER"}]} response = dlp_client.inspect_content(parent=parent, inspect_config=inspect_config, item=item)

Cloud Data Loss Prevention API Documentation

DLP API Client Libraries

To enable Engineering Group A to attach a Compute Engine instance to a specific subnet (10.1.1.0/24) in a Shared VPC, you should grant the Compute Network User Role at the subnet level. This role allows users to use the subnetwork for their instances without giving them broader permissions at the project level.

Step-by-Step:

Identify the Subnet: Locate the subnet (10.1.1.0/24) in the host project.

Grant Role:

Navigate to the GCP Console > VPC network > VPC networks.

Select the Shared VPC host project and locate the specific subnet.

Click on "Edit" and go to the "IAM & Admin" section.

Assign the "Compute Network User" role to Engineering Group A at the subnet level.

Verification: Ensure that Engineering Group A can now attach Compute Engine instances to the specified subnet.

Shared VPC Overview

Compute Network User Role

https://cloud.google.com/network-intelligence-center/docs/firewall-insights/concepts/overview#shadowed-firewall-rules

Firewall Insights analyzes your firewall rules to detect firewall rules that are shadowed by other rules. A shadowed rule is a firewall rule that has all of its relevant attributes, such as its IP address and port ranges, overlapped by attributes from one or more rules with higher or equal priority, called shadowing rules.

To ensure least-privilege access and provide necessary permissions to the DevOps team only during a deployment issue, follow these steps:

Create a Service Account:

In your Google Cloud project, create a new service account specifically for the DevOps team.

Assign Limited Permissions:

Grant the service account permissions with only the necessary list/view roles. For instance, you can create a custom IAM role with compute.instances.list and compute.instances.get permissions.

Grant Service Account User Role:

Assign the Service Account User role to the DevOps team members for the created service account. This allows them to act as the service account and use its permissions.

Access Control During Incidents:

During a deployment issue, the DevOps team can temporarily use the service account to access the resources. This ensures they have the least-privilege access required to investigate and resolve the issue.

Automation and Monitoring:

Implement automation to enable and disable the service account access as needed and monitor the usage to ensure compliance with the least-privilege principle.

Benefits:

Security: Limits access to only what is necessary, reducing the risk of unauthorized changes.

Flexibility: Provides necessary access during incidents without granting permanent elevated permissions.

References

Creating and Managing Service Accounts

Service Account User Role