Configure VPC Service Controls for ULL Packet Mirroring
VPC Service Controls provides security for Ultra Low Latency (ULL) Packet Mirroring to help reduce the risk of data theft when traffic or data moves between different network environments or organizations. You can use VPC Service Controls to place projects containing ULL Packet Mirroring resources inside service perimeters.
This page describes how to configure VPC Service Controls for
ULL Packet Mirroring collector resources (UllMirroringCollector).
For more information, see Components of ULL Packet Mirroring.
Before you begin, review the Overview of VPC Service Controls.
Before you begin
- Verify that you have the required Identity and Access Management (IAM) roles to administer VPC Service Controls. For more information, see IAM roles for administering VPC Service Controls.
- Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
-
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
Roles required to select or create a project
- Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
-
Create a project: To create a project, you need the Project Creator role
(
roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.createpermission. Learn how to grant roles.
-
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
Roles required to select or create a project
- Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
-
Create a project: To create a project, you need the Project Creator role
(
roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.createpermission. Learn how to grant roles.
Enable the Network Security API, if it is not already enabled.
Roles required to enable APIs
To enable APIs, you need the
serviceusage.services.enablepermission. If you created the project, then you likely already have this permission through the Owner role (roles/owner). Otherwise, you can get this permission through the Service Usage Admin role (roles/serviceusage.serviceUsageAdmin). Learn how to grant roles.- Verify that you have the required IAM roles to manage ULL Packet Mirroring resources. For more information, see Set up Packet Mirroring for ULL VPC networks.
Overview of perimeter rules for ULL Packet Mirroring
Perimeter rules for ULL Packet Mirroring act as security guardrails to control
communication between isolated Virtual Private Cloud (VPC) environments while
allowing specific, necessary traffic. Depending on your deployment topology, you
might need to configure VPC Service Controls egress rules and ingress rules
to allow communication between your collector project and the exchange
operator's engine project when managing ULL Packet Mirroring collectors
(UllMirroringCollector).
To protect ULL Packet Mirroring resources, add the Network Security API
(networksecurity.googleapis.com) to the list of restricted services within
your collector service perimeter.
The following table summarizes the required VPC Service Controls configuration for each deployment scenario:
| Scenario | Topology | Required VPC Service Controls configuration |
|---|---|---|
| Create collector in a different project (same service perimeter) | Different project, same perimeter | No additional rules are required because both projects belong to the same service perimeter. |
| Create collector in a different project (separate service perimeter) | Different project, separate perimeters | Add bidirectional egress rules between the engine project and the collector project for networksecurity.googleapis.com. |
Add APIs to the service perimeter
To protect ULL Packet Mirroring resources within a service perimeter, add the Network Security API to the list of restricted services.
Google Cloud console
In the Google Cloud console, go to the VPC Service Controls page.
In the table, click the name of the service perimeter that you want to modify.
Click Edit.
On the Edit service perimeter page, click Restricted services and then Add services.
Select Network security API (
networksecurity.googleapis.com).Click Add selected services and then click Save.
gcloud
To add restricted services to an existing service perimeter, use the
gcloud access-context-manager perimeters update command:
gcloud access-context-manager perimeters update PERIMETER_NAME \
--policy=POLICY_ID \
--add-restricted-services=networksecurity.googleapis.com
Replace the following:
PERIMETER_NAME: the name of the service perimeter.POLICY_ID: the ID of your organization's access policy.
Configure egress rules for cross-perimeter collectors
Configure a collector-to-engine egress rule on your service perimeter to allow
the UllMirroringCollector resource to connect to the UllMirroringEngine in
the exchange operator's engine project.
Before you create the UllMirroringCollector resource, verify that your
exchange operator has completed the following steps in the engine project and
service perimeter:
- Granted the
roles/networksecurity.ullMirroringEngineUserIAM role on the engine project to the caller, such as your user account or service account. - Configured an egress rule in the engine service perimeter that allows
traffic to your collector project
(
projects/COLLECTOR_PROJECT_NUMBER). - If you create the collector from outside the engine service perimeter,
configured an ingress rule in that perimeter to allow the caller and source
environment (
projects/CALLER_PROJECT_NUMBER).
Configure egress from collector perimeter to engine project
Add the following egress policy to the collector service perimeter:
egressPolicies:
- egressFrom:
# Optional: To allow all users or service accounts, you can replace the
# identities list with identityType: ANY_IDENTITY,
# ANY_USER_ACCOUNT, or ANY_SERVICE_ACCOUNT.
identities:
- PRINCIPAL_IDENTIFIER
egressTo:
operations:
- serviceName: networksecurity.googleapis.com
methodSelectors:
- method: '*'
# Optional: The compute.googleapis.com service is required only if you
# restrict the Compute Engine API in your perimeter.
- serviceName: compute.googleapis.com
methodSelectors:
- method: RegionForwardingRulesService.Get
resources:
- projects/ENGINE_PROJECT_NUMBER
title: Allow egress to engine project for ULL mirroring
Replace the following:
PRINCIPAL_IDENTIFIER: the identity that initiates the collector creation request. For information about supported identities and their identifier formats, see Supported identities for ingress and egress rules.ENGINE_PROJECT_NUMBER: the project number of the project that hosts theUllMirroringEngine.
Configure ingress rules for callers
You can create a UllMirroringCollector resource from outside the service
perimeters, such as from a separate project or an external network. When
you send this request, VPC Service Controls evaluates both the collector
project (parent) and the engine project (engine) in a single API call.
Both the collector service perimeter and the engine service perimeter must have
ingress rules that allow the caller and source environment. If
either perimeter lacks a matching ingress rule, the request fails with a
403 SECURITY_POLICY_VIOLATED error.
Configure ingress to the collector perimeter
Add the following ingress policy to the collector service perimeter to allow the external caller:
ingressPolicies:
- ingressFrom:
# Optional: To allow all users or service accounts, you can replace the
# identities list below with identityType: ANY_IDENTITY,
# ANY_USER_ACCOUNT, or ANY_SERVICE_ACCOUNT.
identities:
- PRINCIPAL_IDENTIFIER
sources:
- resource: projects/CALLER_PROJECT_NUMBER
ingressTo:
operations:
- serviceName: networksecurity.googleapis.com
methodSelectors:
- method: '*'
# Optional: The compute.googleapis.com service is required only if you
# restrict the Compute Engine API in your perimeter.
- serviceName: compute.googleapis.com
methodSelectors:
- method: RegionForwardingRulesService.Get
resources:
- projects/COLLECTOR_PROJECT_NUMBER
title: Allow external caller into collector perimeter
Replace the following:
PRINCIPAL_IDENTIFIER: the identity that initiates the collector creation request. For information about supported identities and their identifier formats, see Supported identities for ingress and egress rules.CALLER_PROJECT_NUMBER: the project number of the project from which the caller originates.COLLECTOR_PROJECT_NUMBER: the project number of the project that hosts theUllMirroringCollector.
Create and manage access levels
To permit external access to protected resources inside a perimeter, you can use access levels. Access levels apply only to requests for protected resources coming from outside the service perimeter.
For more information, see Allowing access to protected resources from outside a perimeter.
Troubleshoot perimeter violations
If creating a UllMirroringCollector fails with a 403
SECURITY_POLICY_VIOLATED error, inspect the VPC Service Controls audit logs
in Cloud Logging to identify which perimeter blocked the request:
- Violation on the collector or engine perimeter (
ingressViolationsorNETWORK_NOT_IN_SAME_SERVICE_PERIMETER): verify that both perimeters have ingress rules that allow your identity (principalEmail) and source project or access level. - Violation between the collector and engine projects (
egressViolationsorRESOURCES_NOT_IN_SAME_SERVICE_PERIMETER): verify that both perimeters have bidirectional egress rules fornetworksecurity.googleapis.com. Compute Engine API restriction (
RESOURCES_NOT_IN_SAME_SERVICE_PERIMETER): if an audit log showsserviceNameascompute.googleapis.comandmethodascompute.v1.RegionForwardingRulesService.Get, your perimeter restricts Compute Engine APIs. Verify that your egress and ingress rules include theRegionForwardingRulesService.Getmethod selector.
For more information about diagnosing access denials with unique IDs or troubleshooting tokens in the VPC Service Controls violation analyzer, see Access the violation analyzer.