VPC 서비스 제어를 사용하면 Dialogflow에서 데이터 무단 반출 위험을 완화할 수 있습니다.
VPC 서비스 제어를 사용하여 지정한 리소스 및 데이터를 보호하는 서비스 경계를 만듭니다.
예를 들어 VPC 서비스 제어를 사용하여 Dialogflow를 보호하면 다음 아티팩트는 서비스 경계를 벗어날 수 없습니다.
에이전트 데이터
인텐트 요청 및 응답 인식
제한사항
다음과 같은 제한사항이 적용됩니다.
웹훅을 사용하여 에이전트와 동일한 서비스 경계 내에서 Cloud 함수나 Cloud Run 엔드포인트에 직접 연결할 수 있습니다.
서비스 경계를 만들 때 Dialogflow(dialogflow.googleapis.com)를 보호된 서비스로 포함합니다.
Dialogflow를 작동시키기 위해 추가 서비스를 포함할 필요는 없습니다.
그러나 Dialogflow는 경계 외부의 리소스(예: 경계 외부에 있는 Cloud Storage 버킷에 있는 파일)에 연결할 수 없습니다.
서비스 경계를 만드는 방법에 대한 자세한 내용은 VPC 서비스 제어 문서의 서비스 경계 만들기를 참조하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-03-04(UTC)"],[[["\u003cp\u003eVPC Service Controls helps prevent data exfiltration from Dialogflow by creating a service perimeter that protects specified resources and data.\u003c/p\u003e\n"],["\u003cp\u003eWithin a service perimeter protecting Dialogflow, agent data, and detect intent requests and responses are secured and cannot leave.\u003c/p\u003e\n"],["\u003cp\u003eWebhooks within the same service perimeter can connect to Cloud Functions or Cloud Run, and webhooks can connect to services using Service Directory private network access.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating a service perimeter, include Dialogflow (\u003ccode\u003edialogflow.googleapis.com\u003c/code\u003e) as a protected service, but other services are optional for its core functionality.\u003c/p\u003e\n"],["\u003cp\u003eDialogflow cannot access resources outside the defined service perimeter, such as files in an external Cloud Storage bucket.\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/cx/docs/concept/integration) let third-party applications directly connect to Agents regardless of if the Agent is within a service perimeter.\n- Webhooks can be used to directly connect to a Cloud Function or Cloud Run endpoint within the same service perimeter as the Agent\n- Webhooks can be used to connect to services integrated with [Service Directory private network access](/dialogflow/cx/docs/concept/webhook#sd)\n\nAny other type of webhook service is not supported and will be 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."]]
