Securing repositories in a service perimeter

VPC Service Controls improves your ability to mitigate the risk of unauthorized copying or transfer of data from Google-managed services.

With VPC Service Controls, you can configure security perimeters around the resources of your Google-managed services and control the movement of data across the perimeter boundary.

Using Artifact Registry with VPC Service Controls

If you are using Artifact Registry and Google Kubernetes Engine private clusters in a project within a service perimeter, you can access container images inside the service perimeter as well as Google-provided images.

Cached Docker Hub images stored on mirror.gcr.io are not included in the service perimeter if Artifact Registry is in the perimeter and Container Registry is not in the perimeter as well.

You can access Artifact Registry using the IP addresses for the default Google APIs and services domains, or using these special IP addresses:

  • 199.36.153.4/30 (restricted.googleapis.com)
  • 199.36.153.8/30 (private.googleapis.com)

For details about these options, see Configuring Private Google Access. For an example configuration that uses 199.36.153.4/30 (restricted.googleapis.com), see the documentation for registry access with a virtual IP.

Ensure that Google Cloud services that need to access Artifact Registry are also in the service perimeter, including Binary Authorization, Container Analysis, and runtime environments such as Google Kubernetes Engine and Cloud Run. See the list of supported services for details about each service.

For general instructions to add Artifact Registry to a service perimeter, see Creating a service perimeter.

Using Container Analysis with VPC Service Controls

To learn how to add Container Analysis to your perimeter, see the securing Container Analysis in a service perimeter.