Analytics Hub Vpc Service Controls Linked Views

What the VPC Service Controls Configuration Is

VPC Service Controls allows organizations to establish fine-grained security perimeters around Google Cloud resources, including BigQuery Analytics Hub, to prevent data exfiltration. When BigQuery queries span multiple perimeters across caller projects, linked datasets, and underlying source datasets containing base tables, specific directional ingress and egress rules must be defined to bridge perimeter boundaries.

How It Meets the Requirements

When an analyst queries a view in a linked dataset where the view, caller, and base tables are distributed across separate perimeters:

• Caller Project (Project R): Requires an egress rule targeting Project L (to submit query requests against the linked dataset) and an egress rule targeting Project V (to read data processed from the underlying base tables).
• Linked Dataset Project (Project L): Requires an ingress rule allowing access from Project R (to receive the query execution request) and an egress rule targeting Project V (to resolve and reference the base tables).
• Base Table Source Project (Project V): Requires an egress rule targeting Project L (to return table schema metadata) and an ingress rule allowing access from Project R (to permit the query engine in the caller context to process the underlying data).

Key Advantages

• Precision Access Control: Enables cross-project, cross-perimeter Analytics Hub data sharing without dismantling perimeter boundaries.
• Prevents Exfiltration: Limits communication pathways strictly between designated calling, linking, and storage projects.
• Maintains Source Data Control: Leaves source table ownership intact in Project V while allowing Project L to serve as an analytics projection.

Why This Is Optimal

This configuration accurately aligns with the multi-perimeter architecture rules required by Analytics Hub when views and underlying base tables reside in separate projects and service perimeters.