Use Compliance Manager with VPC Service Controls

Enterprise service tier (requires organization-level activation)

If you enable Compliance Manager within a VPC Service Controls service perimeter, you must configure egress and ingress rules.

You can adjust the following sample ingress and egress rules to meet your business requirements.

For information about limitations, see Supported products and limitations.

Before you begin

1. Make sure that you have the required roles to configure VPC Service Controls at the organization level.

2. To ensure access to resources that exist in the organization or folders, grant the Compliance Manager Admin (roles/cloudsecuritycompliance.admin) role at the organization level.

3. Make sure that you know the following:

   • The email address for the Cloud Security Compliance service agent ([e-mail]).

   • The email addresses of Compliance Manager users. Compliance Manager users are the people who administer Compliance Manager and perform activities such as audits.

4. Verify that the Cloud Security Compliance service agent has the required permissions within the perimeter to complete an audit. For more information, see Audit your environment with Compliance Manager.

Add ingress and egress rules

1. Add the following ingress rule:

   - ingressFrom:
     identities:
     - user: USER_EMAIL_ADDRESS
     sources:
         - accessLevel: "*"
     ingressTo:
       operations:
         - serviceName: securitycenter.googleapis.com
           methodSelectors:
             - method: "*"
       resources: "*"
   

   Replace USER_EMAIL_ADDRESS with the email address of the Compliance Manager user.

2. Add the following ingress rule to permit Compliance Manager to monitor and audit the resources in your Google Cloud organization:

   - ingressFrom:
     identities:
     - user: USER_EMAIL_ADDRESS
     sources:
         - accessLevel: "*"
     ingressTo:
       operations:
         - serviceName: cloudsecuritycompliance.googleapis.com
           methodSelectors:
             - method: "*"
       resources: "*"
   

   Replace USER_EMAIL_ADDRESS with the email address of the Compliance Manager user.

3. Configure the following ingress rule to run audits for a project:

   - ingressFrom:
     identities:
     - serviceAccount: COMPLIANCE_MANAGER_SA_EMAIL_ADDRESS
     - user: USER_EMAIL_ADDRESS
     sources:
         - accessLevel: "*"
     ingressTo:
       operations:
         - serviceName: cloudasset.googleapis.com
           methodSelectors:
             - method: "*"
       resources: "*"
   

   Replace the following:

   • USER_EMAIL_ADDRESS: the email address of the Compliance Manager user.

   • COMPLIANCE_MANAGER_SA_EMAIL_ADDRESS: the email address of the Cloud Security Compliance service agent.

4. Configure the following ingress rule to run audits for a folder:

   - ingressFrom:
     identities:
     - serviceAccount: COMPLIANCE_MANAGER_SA_EMAIL_ADDRESS
     - user: USER_EMAIL_ADDRESS
     sources:
         - accessLevel: "*"
     ingressTo:
       operations:
           - serviceName: "*"
       resources: "*"
   

   Replace the following:

   • USER_EMAIL_ADDRESS: the email address of the Compliance Manager user.

   • COMPLIANCE_MANAGER_SA_EMAIL_ADDRESS: the email address of the Cloud Security Compliance service agent.

   Broad access is required to permit auditing of all the resources in the projects within the folder.

5. Configure the following ingress rule to run an audit when the enrolled Cloud Storage bucket is inside the perimeter:

   - ingressFrom:
     identities:
     - serviceAccount: COMPLIANCE_MANAGER_SA_EMAIL_ADDRESS
     - user: USER_EMAIL_ADDRESS
     sources:
         - accessLevel: "*"
     ingressTo:
       operations:
           - serviceName: storage.googleapis.com
             methodSelectors:
               - method: google.storage.buckets.getIamPolicy
               - method: google.storage.buckets.testIamPermissions
               - method: google.storage.objects.getIamPolicy
               - method: google.storage.buckets.setIamPolicy
               - method: google.storage.objects.setIamPolicy
               - method: google.storage.objects.create
               - method: google.storage.objects.get
     resources: "*"
   

   Replace the following:

   • USER_EMAIL_ADDRESS: the email address of the Compliance Manager user.

   • COMPLIANCE_MANAGER_SA_EMAIL_ADDRESS: the email address of the Cloud Security Compliance service agent.

6. Configure the following egress rule to run an audit when the enrolled Cloud Storage bucket is inside the perimeter:

   - egressFrom:
     identities:
       - serviceAccount: COMPLIANCE_MANAGER_SA_EMAIL_ADDRESS
         - user: USER_EMAIL_ADDRESS
       sources:
         - accessLevel: "*"
     egressTo:
       operations:
           - serviceName: storage.googleapis.com
             methodSelectors:
               - method: google.storage.buckets.getIamPolicy
               - method: google.storage.buckets.testIamPermissions
               - method: google.storage.objects.getIamPolicy
               - method: google.storage.buckets.setIamPolicy
               - method: google.storage.objects.setIamPolicy
               - method: google.storage.objects.create
               - method: google.storage.objects.get
       resources: "*"
   

   Replace the following:

   • USER_EMAIL_ADDRESS: the email address of the Compliance Manager user.

   • COMPLIANCE_MANAGER_SA_EMAIL_ADDRESS: the email address of the Cloud Security Compliance service agent.

What's next

• Diagnose issues by using the VPC Service Controls troubleshooter or the VPC Service Controls violation analyzer.