Stay organized with collections
Save and categorize content based on your preferences.
VPC Service Controls
can help you mitigate the risk of data exfiltration from Dialogflow.
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 Dialogflow,
the following artifacts cannot leave your service perimeter:
Agent data
Detect intent requests and responses
Limitations
The following limitations apply:
Integrations let third-party applications
directly connect to Agents regardless of if the Agent is within a service
perimeter.
When VPC Service Controls is enabled, webhook
calls are blocked.
Service perimeter creation
When you create a service perimeter,
include Dialogflow (dialogflow.googleapis.com) as a protected service.
You aren't required to include any additional services
for Dialogflow to function.
However, Dialogflow won't be able to reach resources outside the perimeter,
such as files in a Cloud Storage bucket that is outside the perimeter.
For more information about creating a service perimeter, see
Creating a service perimeter
in the VPC Service Controls documentation.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eVPC Service Controls helps prevent data exfiltration from Dialogflow by creating a service perimeter.\u003c/p\u003e\n"],["\u003cp\u003eWhen protecting Dialogflow with VPC Service Controls, agent data and detect intent requests/responses cannot leave the defined service perimeter.\u003c/p\u003e\n"],["\u003cp\u003eService Directory is not supported when using VPC Service Controls with Dialogflow, and webhook calls are blocked.\u003c/p\u003e\n"],["\u003cp\u003eTo create a service perimeter for Dialogflow, you must include \u003ccode\u003edialogflow.googleapis.com\u003c/code\u003e as a protected service.\u003c/p\u003e\n"],["\u003cp\u003eDialogflow will be unable to access resources outside of the defined service perimeter.\u003c/p\u003e\n"]]],[],null,["# Using VPC Service Controls\n\n[VPC Service Controls](/vpc-service-controls/docs/overview)\ncan help you mitigate the risk of data exfiltration from Dialogflow.\nUse VPC Service Controls to create a *service perimeter*\nthat protects the resources and data that you specify.\nFor example, when you use VPC Service Controls to protect Dialogflow,\nthe following artifacts cannot leave your service perimeter:\n\n- Agent data\n- Detect intent requests and responses\n\nLimitations\n-----------\n\nThe following limitations apply:\n\n- [Integrations](/dialogflow/es/docs/integrations) let third-party applications directly connect to Agents regardless of if the Agent is within a service perimeter.\n- [Service Directory](/service-directory/docs/private-network-access-overview) is not supported.\n- When VPC Service Controls is enabled, [webhook](/dialogflow/es/docs/fulfillment-webhook) calls are blocked.\n\nService perimeter creation\n--------------------------\n\nWhen you create a service perimeter,\ninclude Dialogflow (`dialogflow.googleapis.com`) as a protected service.\nYou aren't required to include any additional services\nfor Dialogflow to function.\nHowever, Dialogflow won't be able to reach resources outside the perimeter,\nsuch as files in a Cloud Storage bucket that is outside the perimeter.\n\nFor more information about creating a service perimeter, see\n[Creating a service perimeter](/vpc-service-controls/docs/create-service-perimeters)\nin the VPC Service Controls documentation."]]
