# VPC Service Controls perimeter

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

A Google Cloud boundary around projects and supported services that controls data egress and ingress across it, independent of IAM. Requests that cross the perimeter in violation are denied, or only logged in dry run mode. It guards against data leaving a protected set of services.

## An example, sourced

Google documents that with VPC Service Controls it can be difficult to determine the impact on your environment when a service perimeter is created or modified, and describes dry run mode as the answer. In dry run mode, "requests that violate the perimeter policy are not denied, only logged," and the logs can be analyzed to change the configuration. Google also says it recommends using VPC Service Controls and IAM together for defense in depth.

## Why it matters here

A perimeter is the data-exfiltration guardrail on Google Cloud, separate from IAM. Run it in dry run first, because a new perimeter can block legitimate cross-project access. A perimeter protects against data leaving the boundary, which IAM alone does not. Run dry run first, since a new perimeter can block legitimate cross-project access.

## Related pages

- [Principal access boundary: meaning and an example](/glossary/principal-access-boundary/)
- [Guardrail: meaning and an example](/glossary/guardrail/)
- [Preventive control: meaning and an example](/glossary/preventive-control/)
- [All of them](/glossary/)

## Sources

- https://cloud.google.com/vpc-service-controls/docs/dry-run-mode (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/glossary/vpc-service-controls-perimeter/
