GCP BigQuery - Access Management¶
Access Management¶
| Topic | Detail |
|---|---|
| Integration methodology | Privacera PolicySync |
| Access Tools | JDBC |
| Supported User Identities | GCP IAM, SAML |
Supported Access Management Features¶
| Feature | Supported | Native | Using SecureView |
|---|---|---|---|
 Dataset Access Control | Yes | Yes | N/A |
| Table Access Control | Yes | Yes | Yes |
| View Access Control | Yes | Yes | Yes |
| Column Access Control | Yes | Yes | Yes |
| Row Access Control | Yes | Yes | Yes |
| Column Data Masking 1 | Yes | Yes | Yes |
| Centralized Access Audit | Yes | N/A | N/A |
Limitations¶
- To use resource-based data masking, you must enable Secure View. BigQuery's native mode only supports tag-based data masking.
- When using Security Zones, configure the Security Zone only at the project level (e.g.,
test_project-12345) to ensure consistent enforcement across all tagged resources within the project.
- Prev topic: Overview
- Next topic: Prerequisites
-
Note: BigQuery Native mode supported only tag based column masking and resource based Column Masking is not supported. ↩