VPC Service Controls can help you mitigate the risk of data exfiltration from CX Agent Studio. Use VPC Service Controls to create a service perimeter that protects the resources and data that you specify. For example, when you use VPC Service Controls to protect CX Agent Studio, the following artifacts cannot leave your service perimeter:
- Agent application data
- runSession requests and responses
CX Agent Studio allows interacting with other Google Cloud resources such as DLP redaction templates, BigQuery for conversation exporting, and Data Stores. These resources are in your control and must be available under the same VPC-SC perimeter as the agent application.
Limitations
The following limitations apply:
- Tools and callbacks can't send requests to arbitrary HTTP or HTTPS endpoints when VPC Service Controls is enabled, as this may risk exfiltrating data outside the VPC Service Controls perimeter. To allow outbound requests, you must either configure Service Directory for private network access for private VPC targets or add external domains to Allowed origins in your project location settings.
- Audio recordings cannot be written to Cloud Storage buckets outside the perimeter.
- Conversations cannot be written to BigQuery datasets outside the perimeter.
- Sensitive Data Protection redaction templates outside the perimeter cause failures in redacting conversation contents.
- OpenAPI tools cannot reference authentication keys using secrets that are outside the perimeter.
- Datastore tools that specify a data store outside the perimeter fail to execute.
- Flow-based agents that specify an agent resource outside the perimeter fail when called.
- Attempting to import an agent application from a Cloud Storage bucket outside the perimeter fails.
- Attempting to export an agent application to a Cloud Storage bucket outside the perimeter fails.
Service perimeter creation
When you create a service perimeter,
include both CX Agent Studio (ces.googleapis.com) and
CX Insights (contactcenterinsights.googleapis.com)
as protected services.
Include any services that you want to restrict (for example,
storage.googleapis.com, bigquery.googleapis.com) under the
Restricted services pane.
For more information about creating a service perimeter, see Creating a service perimeter in the VPC Service Controls documentation.
VPC Service Controls documentation for optional dependencies:
Allow external endpoints using Allowed origins
When VPC Service Controls is enabled, tools and callbacks that call
external HTTP or HTTPS URLs without using Service Directory are
blocked with a 403 error unless you add each external origin (including any
external OAuth token endpoints) to Allowed origins for your project and
location.
To view and update Allowed origins, grant the
Gemini Enterprise for Customer Experience Security Settings Editor predefined Identity and Access Management role
(roles/ces.securitySettingsEditor), or a custom role with
ces.securitySettings.get and ces.securitySettings.update (also included
in roles/ces.admin). Enter exact origins with the scheme, domain, and
optional port (for example, https://api.example.com or
https://api.example.com:8443), with no URL paths, trailing slashes, or
wildcards.
You can configure Allowed origins in the console or using the REST API:
- Console: Open the CX Agent Studio console, select your project and location, click the settings icon, add each origin under Allowed origins, and click Save (see Project location settings).
- REST API: Call
projects.locations.updateSecuritySettingsto updateendpointControlPolicy.allowedOriginson the project location'sSecuritySettingsresource.
Using Service Directory for private network access
CX Agent Studio integrates with Service Directory private network access, so it can connect to OpenAPI tools targets inside your VPC network. This keeps the traffic within the Google Cloud network and enforces Identity and Access Management and VPC Service Controls.
To set up a tool targeting a private network:
Follow Service Directory private network configuration to configure your VPC network and Service Directory endpoint.
The Customer Engagement Suite Service Agent service account with the following address must exist for your agent project:
service-agent-project-number@gcp-sa-ces.iam.gserviceaccount.com
Grant the following roles to Customer Engagement Suite Service Agent service account in the project where your Service Directory is located:
servicedirectory.viewerservicedirectory.pscAuthorizedService
Additionally, if your Service Directory is in a different project than your agent application, you also need to grant the
servicedirectory.viewerrole to the Customer Engagement Suite Service Agent account in the project that hosts your agent application.Provide Service Directory service along with the URL and optional authentication information when creating the tool. This field is available in the advanced settings for the tool.
To troubleshoot issues, you can set up a private uptime check to check that your Service Directory is correctly configured.