BigQuery permissions
To perform actions in BigQuery, Protect uses a GCP connection. This GCP connection must be configured with a service account that has the following permissions.
bigquery.dataPolicies.createbigquery.dataPolicies.deletebigquery.dataPolicies.getbigquery.dataPolicies.getIamPolicybigquery.dataPolicies.listbigquery.dataPolicies.setIamPolicybigquery.dataPolicies.updatebigquery.datasets.getbigquery.datasets.getIamPolicybigquery.jobs.createbigquery.rowAccessPolicies.createbigquery.rowAccessPolicies.deletebigquery.rowAccessPolicies.listbigquery.rowAccessPolicies.setIamPolicybigquery.rowAccessPolicies.updatebigquery.tables.getbigquery.tables.getDatabigquery.tables.getIamPolicyNote The GCP service account configured for Protect must have this permission. That is, this permission is required only if the Grant access to tables checkbox is selected when adding the Protect for BigQuery capability to the Edge site.bigquery.tables.listbigquery.tables.setCategorybigquery.tables.setIamPolicyNote The GCP service account configured for Protect must have this permission. That is, this permission is required only if the Grant access to tables checkbox is selected when adding the Protect for BigQuery capability to the Edge site.bigquery.tables.updatedatacatalog.categories.getIamPolicydatacatalog.categories.setIamPolicydatacatalog.taxonomies.createdatacatalog.taxonomies.getdatacatalog.taxonomies.listdatacatalog.taxonomies.updatelogging.logEntries.listresourcemanager.projects.get
In addition, ensure that the following APIs are enabled for the GCP projects used by Protect:
- BigQuery API
- BigQuery Data Policy API
- Google Cloud Data Catalog API
- Cloud Logging API