Skip to main content

How to configure the GCP integration to only scan projects in a specific folder

S
Written by Shannon DeLange
Updated today

Users may want to configure the GCP integration to only scan projects in a specific folder in their organization. To accomplish this, follow the steps below.

  • Select the Organization linking flow for GCP in Vanta

  • Enter your domain on the Select an organization to scan page and click Next

  • Select the products you want Vanta to scan on the Select Products page and click Next

  • Perform the steps below in lieu of the steps on the Create service account & role page

  • In GCP, create a role at the organization level with the following permissions. This role could be named "VantaOrganizationScanner"

appengine.applications.get
bigquery.datasets.get
cloudasset.assets.searchAllResources
compute.instances.get
compute.instances.getEffectiveFirewalls
compute.subnetworks.get
iam.roles.list
pubsub.topics.get
resourcemanager.folders.getIamPolicy
resourcemanager.folders.list
resourcemanager.organizations.getIamPolicy
resourcemanager.projects.get
storage.buckets.get

  • Create an additional role at the organization level with the following permission. This role could be named "VantaFolderScanner":

resourcemanager.projects.list

  • Create a service account in one of the projects that exists inside of the folder you want Vanta to scan.

  • In the Organization level IAM configuration, grant access for the service account and apply the "VantaOrganizationScanner" role created above, as well as the "Security Reviewer" role.

  • In the Folder level IAM configuration, grant access for the service account and apply the "VantaFolderScanner" role.

  • Navigate to service accounts in the project where the service account was initially created, and generate a JSON key for the service account where the permissions above were applied.

  • In Vanta, click Next to skip through the "Create service account & role" section of the GCP linking flow and upload the JSON key.

Troubleshooting

Ensure that when looking at the service account from the folder level there are two roles inherited from the organization level and one applied from the folder level. It might look something like this:

JakeFolderLevelSa.png