Professional-Cloud-Security-Engineer Exam Dumps - Google Cloud Certified Questions and Answers

Objective: Encrypt data using envelope encryption.

Solution: Follow the envelope encryption process.

Steps:

Step 1: Generate a Data Encryption Key (DEK) locally. The DEK is used to encrypt the actual data.

Step 2: Encrypt the data using the DEK.

Step 3: Use a Key Encryption Key (KEK) to wrap the DEK. The KEK is used to encrypt the DEK.

Step 4: Store the encrypted data and the wrapped DEK. This ensures that the data can be securely decrypted in the future using the KEK to unwrap the DEK.

Envelope encryption enhances security by adding an additional layer of encryption to the data encryption key, which is particularly useful for managing large volumes of encrypted data.

References:

Envelope Encryption Overview

Google Cloud Key Management Service Documentation

https://cloud.google.com/bigquery/docs/scan-with-dlp

Cloud Data Loss Prevention API allows to detect and redact or remove sensitive data before the comments or reviews are published. Cloud DLP will read information from BigQuery, Cloud Storage or Datastore and scan it for sensitive data.

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

Define Trusted Image Projects:

Identify the project or projects where your trusted operating system images are stored.

Ensure these images meet your organization’s security requirements and are regularly updated to mitigate vulnerabilities.

Create an Organization Policy:

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

Create a policy constraint that restricts the creation of boot disks to only those images stored in your trusted image project(s).

The policy constraint to use is constraints/compute.trustedImageProjects.

Apply the Policy:

Apply this organization policy at the appropriate level (organization, folder, or project) to enforce that all new VM instances use images from the trusted repository.

This ensures consistency in the security posture across all projects within the organization.

Monitor Compliance:

Regularly monitor the compliance with this policy using audit logs and other monitoring tools.

Update the trusted images as necessary to ensure they remain secure and compliant with your security standards.

References:

Organization Policy Service

Trusted Image Projects Constraint

To prevent developers from creating user-managed service account keys and reduce the risk of key mismanagement, you should enable an organization policy that specifically prohibits the creation of these keys.

Enable an organization policy to prevent service account keys from being created (C):

Google Cloud provides the capability to enforce organizational policies that restrict various actions, including the creation of service account keys. By enabling this policy, you ensure that developers cannot create new user-managed service account keys, thus minimizing the risk of key mismanagement and potential security breaches.

References

Service Accounts documentation

Organization Policy Service documentation

https://cloud.google.com/resource-manager/docs/organization-policy/restricting-domains#setting_the_organization_policy

The domain restriction constraint is a type of list constraint. Google Workspace customer IDs can be added and removed from the allowed_values list of a domain restriction constraint. The domain restriction constraint does not support denying values, and an organization policy can't be saved with IDs in the denied_values list. All domains associated with a Google Workspace account listed in the allowed_values will be allowed by the organization policy. All other domains will be denied by the organization policy.

To enforce access control policies for applications and resources in Google Cloud, the recommended service is Identity-Aware Proxy (IAP).

Identity-Aware Proxy (IAP):

IAP allows you to control access to your applications and resources based on the identity of the user and the context of the request. It integrates with IAM to provide fine-grained access control, ensuring that only authorized users can access specific resources.

IAP helps enforce security policies at the application layer, providing an additional layer of protection beyond traditional network-based security measures.

References

Identity-Aware Proxy documentation

To maintain a historical record of what was running in Google Cloud Platform at any point in time, you should use Forseti Security to automate inventory snapshots. Forseti Security is an open-source toolkit that helps to automate security and compliance in GCP by taking inventory snapshots of GCP resources.

Step-by-Step:

Install Forseti Security:

Follow the installation guide to deploy Forseti Security on your GCP environment.

Configure Inventory:

Set up the inventory module in Forseti to capture and store snapshots of GCP resources.

Schedule Snapshots:

Use Forseti’s configuration to schedule regular inventory snapshots.

Access Historical Data:

Review and access historical records through Forseti’s dashboard or by querying the Forseti database.

Compliance and Monitoring: Use Forseti to ensure compliance and monitor changes over time.

References:

Forseti Security Overview

Inventory Module

Use Cloud External Key Management (EKM) that integrates with an external Hardware Security Module (HSM) system from supported vendors: Cloud EKM allows you to use encryption keys that are managed externally to Google Cloud. This means you can generate and store your keys in an on-premises HSM or another supported external HSM service, and integrate these keys with various Google Cloud services.

Integration with Google Services: Cloud EKM integrates seamlessly with many Google Cloud services, including BigQuery, Cloud Storage, Compute Engine, and more. This provides you with full control over your encryption keys while still taking advantage of Google Cloud's powerful services.

References

Cloud External Key Management (EKM) documentation

External Key Management overview