VPC Service Controls: Service Perimeters, Access Levels and Dry-Run Mode

GCP Study Hub
November 20, 2026

VPC Service Controls controls access to Google-managed APIs such as Cloud Storage and BigQuery based on the context a request comes from, not only the identity that makes it. A service perimeter protects the resources in the projects it contains. Once a project is inside a perimeter with a service restricted, calls to that service from the internet or from VPC networks in other projects are denied, even when IAM would allow them. For the Professional Cloud Network Engineer exam, the topic turns on how perimeters are scoped, how access levels let specific outside callers in, what VPC Service Controls does not filter, and how dry-run mode lets you change a perimeter safely.

Why context matters as well as identity

IAM decides whether an identity is allowed to call an API. It does not consider where the call comes from, so a leaked credential, such as a stolen OAuth token or an exported service account key, works from any network.

A service perimeter adds the missing condition. Calls to a restricted service from outside the perimeter are denied regardless of the credential, which is what makes VPC Service Controls a defense against data exfiltration with valid but misused credentials.

Perimeters are built around projects

The perimeter model is project-based, which affects how designs are scoped:

  • Perimeters contain projects, not networks, and a project can belong to only one regular perimeter.
  • A perimeter protects the resources in the projects it contains, so one perimeter around a project covers every bucket and dataset in it, whichever VPC network the workloads use.
  • VPC networks that belong to a project inside the perimeter are treated as inside it. Their VMs keep access to the restricted services with no extra rules.

Access levels and access policies

Calls from outside the perimeter are blocked unless they satisfy an access level. An Access Context Manager access level can be built from IP ranges, and it lets callers from those ranges through.

Access levels and perimeters both live in an Access Context Manager access policy, which is the organization-level container that holds them.

What VPC Service Controls does not do

VPC Service Controls protects Google APIs. Restricted services are Google APIs, not network resources, so it does not filter network traffic to VMs, including user traffic arriving at Compute Engine through a load balancer.

Cloud NGFW covers the other side of that line. Its rules filter packets in your VPC networks and never see requests that reach Google APIs over the internet from elsewhere. The two controls answer different questions, one about API access and one about network traffic.

The restricted.googleapis.com VIP complements perimeters by only serving APIs that VPC Service Controls supports.

Dry-run mode

Adding a project to an enforced perimeter starts blocking API calls that cross the new boundary right away. VPC Service Controls handles this with a dry-run configuration that runs alongside the enforced one.

When you add a project to the dry-run configuration, requests that would violate the new perimeter are still allowed, but each one is written to Cloud Logging as a dry-run violation. The result is a list of the API calls that would fail after enforcement, gathered while every workload keeps running. Once the violations are understood and fixed with ingress or egress rules, you promote the dry-run configuration to enforced.

For the Professional Cloud Network Engineer exam, we would treat dry-run as the normal path for changing a perimeter: stage the change, review the logged violations, add the ingress or egress rules they call for, and then enforce.

Our Professional Cloud Network Engineer practice exams cover VPC Service Controls alongside Google Cloud Armor and Cloud NGFW, with detailed explanations that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow