Objective: Ensure that a Cloud Storage bucket in Project A can only be readable from Project B and prevent data access or copying to Cloud Storage buckets outside the network, even with correct credentials.

Solution: Use VPC Service Controls to create a security perimeter.

Steps:

Step 1: Open the Google Cloud Console.

Step 2: Navigate to the VPC Service Controls page.

Step 3: Create a new service perimeter.

Step 4: Add Project A and Project B to the service perimeter.

Step 5: Include Cloud Storage service in the perimeter configuration.

Step 6: Define access levels to ensure that only resources within the perimeter can access the Cloud Storage bucket.

By setting up a VPC Service Controls perimeter, you can enforce security boundaries that restrict data access and movement to within defined projects, providing an extra layer of protection beyond IAM permissions.

To meet data residency requirements on Google Cloud, the recommended option is to use Organization Policy Service constraints. This service allows you to define and enforce specific constraints across your organization, including constraints related to the geographical location where data is stored.

Organization Policy Service constraints allow administrators to enforce policies that restrict resources to specific locations. For instance, you can set policies to ensure that all storage buckets, databases, and other data resources reside within specific geographic boundaries. This helps in complying with data residency requirements.

References

Organization Policy Service documentation

Google Cloud Data Residency

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: Provide evidence of access reviews for an upcoming audit.

Solution: Use Policy Analyzer to review and report on IAM policies.

Steps:

Step 1: Open the Google Cloud Console.

Step 2: Navigate to the Policy Analyzer tool.

Step 3: Select the project for which you need to review access policies.

Step 4: Use the tool to generate reports on IAM roles and permissions.

Step 5: Export the reports as evidence for the audit.

Policy Analyzer provides detailed insights into IAM policies, helping you to review access configurations and generate necessary reports for compliance and auditing purposes.

Identity-Aware Proxy (IAP) controls access to web resources based on user identity and context, not network firewalls (like Option B). The tool used to define the contextual requirements (IP range) and identity (group membership) is an Access Level within Access Context Manager.

Access Level: Defines the required context (e.g., source IP range of the internal network) and the required identity attributes (e.g., user is a member of the AppDev group).

IAP Policy: The IAP policy for the Cloud Run application is then configured to only allow access if the user meets the conditions defined in the Access Level.

Extracts:

" Identity-Aware Proxy works by verifying a user ' s identity and context of the request to determine if the user should be allowed to access an application. " (Source 3.1)

" When you set an IAP policy, you can define an Access Level from Context-Aware Access to enforce conditions based on user location (IP address), security status, and device policy, along with user identity/group membership. " (Source 3.2)

" IAP with Context-Aware Access is the recommended zero-trust approach for enforcing both identity (AppDev group) and context (internal IP address) requirements. " (Source 3.3)