Service perimeter around managed services
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Service perimeter around managed services is a Google Cloud guardrail written in vPC Service Controls. A service perimeter creates a security boundary that blocks, by default, communication from inside the perimeter to Google Cloud services across it, such as copying data to a Cloud Storage bucket outside the perimeter.
More data exfiltration guardrails ยท About VPC Service Controls
gcloud access-context-manager perimeters create NAME \
--title=TITLE \
--resources=RESOURCES \
--restricted-services=RESTRICTED-SERVICES \
--ingress-policies=INGRESS-FILENAME.yaml \
--egress-policies=EGRESS-FILENAME.yaml \
[--access-levels=LEVELS] \
[--enable-vpc-accessible-services] \
[--vpc-allowed-services=ACCESSIBLE-SERVICES] \
--policy=POLICY_NAME
gcloud access-context-manager perimeters \
dry-run create ProdPerimeter --perimeter-title="Production Perimeter" \
--perimeter-type="regular" \
--perimeter-resources=projects/12345,projects/67890 \
--perimeter-restricted-services=storage.googleapis.com,bigquery.googleapis.com \
--perimeter-ingress-policies=ingress.yaml \
--perimeter-egress-policies=egress.yaml \
--policy=330193482019
- Blocks
- A service perimeter creates a security boundary that blocks, by default, communication from inside the perimeter to Google Cloud services across it, such as copying data to a Cloud Storage bucket outside the perimeter.
- Breaks
- Google documents that a VM in a VPC network inside the perimeter cannot reach Cloud Storage buckets outside it, and that ingress or egress rules are needed for any cross-perimeter access. (source)
- Test before applying
- Google documents dry run mode for perimeters: requests that violate the perimeter policy are logged and not denied. (source)
- Mechanism
- VPC Service Controls (service perimeters): Google Cloud managed services and the projects in the perimeter; Google says it does not block access to third-party APIs or services on the internet.
- Taken from
- provider documentation, provider documentation
What the source says
"Enforced perimeters actively prevent access to protected services." (read 10 Nov 2026).
On what it breaks: "VPC Service Controls doesn't allow a VM within a VPC network that is inside a service perimeter to access Cloud Storage buckets that are outside the perimeter."
Related guardrails
- Deny AWS RAM sharing with external accountsAWS, Service control policies (SCPs), data exfiltration
- Block public sharing of EBS snapshots (declarative policy)AWS, Declarative policies, data exfiltration
- Storage SAS tokens should adhere to 7 day maximum validityAzure, Azure Policy (built-in definitions), data exfiltration
- Domain restricted sharingGoogle Cloud, Organization Policy Service (managed and legacy constraints), data exfiltration
- Allowed destinations for exporting resourcesGoogle Cloud, Organization Policy Service (managed and legacy constraints), data exfiltration
- Custom constraint limiting IAM role grants to organization membersGoogle Cloud, Custom organization policy constraints, data exfiltration
Related pages
- Allowed destinations for exporting resources (Google Cloud Organization Policy Service)
- Custom constraint limiting IAM role grants to organization members (Google Cloud Custom organization policy constraints)
- Principal access boundary limiting the resources principals can access (Google Cloud Principal access boundary (PAB) policies)
Sources
- Service perimeter around managed services, read 10 Nov 2026
- What it breaks, read 10 Nov 2026
- How to test it first, read 10 Nov 2026
Last reviewed 16 Nov 2026.