Complete Professional-Cloud-Security-Engineer Google Materials

This is a Customer-supplied encryption keys (CSEK). We generate our own encryption key and manage it on-premises. A KEK never leaves Cloud KMS.There is no KEK or KMS on-premises. Encryption at rest by default, with various key management options https://cloud.google.com/security/encryption-at-rest

Understanding Unmanaged Users:

Unmanaged users are those who have created Google Cloud accounts using their company email addresses outside of the organization's management (e.g., through GCDS).

Challenge:

The goal is to bring these unmanaged accounts under your company's control without disrupting their existing accounts and access.

Using the Transfer Tool:

Google provides a transfer tool specifically designed to migrate unmanaged users to a managed state.

This tool allows administrators to invite unmanaged users to join the organization's Google Cloud Identity or Google Workspace account.

Steps to Use the Transfer Tool:

Step 1: Access the transfer tool from the Google Admin console.

Step 2: Identify the unmanaged users using their email addresses.

Step 3: Send invitations to these users to transfer their accounts.

Step 4: Users accept the invitations, allowing their accounts to be managed under the organization's domain.

Benefits:

This method ensures a smooth transition for users without losing access to their existing data and services.

It aligns with best practices for managing user accounts in a corporate environment.

References:

Migrate unmanaged users

Google Cloud Directory Sync

De-identifying sensitive data Cloud Data Loss Prevention (DLP) can de-identify sensitive data in text content, including text stored in container structures such as tables. De-identification is the process of removing identifying information from data. The API detects sensitive data such as personally identifiable information (PII), and then uses a de-identification transformation to mask, delete, or otherwise obscure the data. For example, de-identification techniques can include any of the following: Masking sensitive data by partially or fully replacing characters with a symbol, such as an asterisk (*) or hash (#). Replacing each instance of sensitive data with a token, or surrogate, string. Encrypting and replacing sensitive data using a randomly generated or pre-determined key. When you de-identify data using the CryptoReplaceFfxFpeConfig or CryptoDeterministicConfig infoType transformations, you can re-identify that data, as long as you have the CryptoKey used to originally de-identify the data. https://cloud.google.com/dlp/docs/deidentify-sensitive-data

Objective: Synchronize security groups with email addresses from an LDAP directory to Cloud IAM.

Solution: Use Google Cloud Directory Sync (GCDS) to perform one-way synchronization based on LDAP search rules.

Steps:

Step 1: Download and install Google Cloud Directory Sync (GCDS) on a secure server.

Step 2: Configure GCDS with the LDAP server details and authentication.

Step 3: Define LDAP search rules to filter security groups based on the “user email address” attribute.

Step 4: Map LDAP security groups to Google Cloud IAM roles.

Step 5: Set up a synchronization schedule to keep the groups in sync.

Step 6: Perform a test sync to ensure that the configuration is correct.

Step 7: Activate the synchronization to keep the LDAP directory and Cloud IAM in sync.

Using GCDS for one-way synchronization ensures that the security groups in Cloud IAM are consistently updated based on the LDAP directory, maintaining alignment with the organization’s security policies.

References:

Google Cloud Directory Sync Documentation

Setting Up Google Cloud Directory Sync