VPC 서비스 제어를 부주의하게 사용 설정하면 기존 애플리케이션에 문제가 발생할 수 있으며 서비스가 중단될 수 있습니다. 사용 설정 기간을 신중하게 계획하고, 데이터 수집, 테스트 수행, 위반 로그 분석에 필요한 시간을 충분히 확보하는 것이 좋습니다. 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-09-04(UTC)"],[],[],null,["# Configure Secure Source Manager in a VPC Service Controls perimeter\n\nThis guide shows how to use a Private Service Connect\nSecure Source Manager in a [VPC Service Controls](/vpc-service-controls/docs/overview)\nperimeter to guard against data exfiltration.\n\nThis guide is intended for network administrators, security architects, and\ncloud operations professionals who want to mitigate the risk of sensitive\ndata loss.\n\nBefore you begin\n----------------\n\n1. [Create a Private Service Connect Secure Source Manager instance](/secure-source-manager/docs/create-private-service-connect-instance).\n2. [Create a VPC Service Controls perimeter](/vpc-service-controls/docs/create-service-perimeters).\n\n### Required roles\n\n\nTo get the permissions that\nyou need to configure Secure Source Manager in a VPC Service Controls perimeter,\n\nask your administrator to grant you the\nfollowing IAM roles on the organization:\n\n- [Access Context Manager Admin role](/iam/docs/roles-permissions/accesscontextmanager#accesscontextmanager.policyAdmin) (`roles/accesscontextmanager.policyAdmin`)\n- [Project Creator](/iam/docs/roles-permissions/resourcemanager#resourcemanager.projectCreator) (`roles/resourcemanager.projectCreator`)\n\n\nFollow best practices\n---------------------\n\nCareless enablement of VPC Service Controls can cause problems with existing\napplications and could potentially cause an outage. We recommend that you plan\nenablement carefully and allow ample time to gather data, conduct tests, and\nanalyze violation logs. Make sure that stakeholders from your\nVPC Service Controls operations team and your applications team are available for\nthe task.\n\nFor more information on best practices, see\n[Best practices for enabling VPC Service Controls](/vpc-service-controls/docs/enable)\n\nAdd your project to the perimeter\n---------------------------------\n\n1. In the Google Cloud console, go to the **VPC Service Controls** page.\n\n [Go to VPC Service Controls](https://console.cloud.google.com/security/service-perimeter)\n2. On the **VPC Service Controls** page, select the perimeter you want to use\n to protect your project.\n\n3. On the **VPC Service Control enforced config detail** page, click **Edit**\n in the **resources to protect** section.\n\n4. Click **Resources to protect** and add your project ID.\n\n5. Click **Save**.\n\nAdd Secure Source Manager as a restricted service\n-------------------------------------------------\n\n1. In the Google Cloud console, go to the **VPC Service Controls** page.\n\n [Go to VPC Service Controls](https://console.cloud.google.com/security/service-perimeter)\n2. On the **VPC Service Controls** page, select the perimeter you added your\n project to.\n\n3. On the **VPC Service Control enforced config detail** page, click **Edit**\n in the **Restricted services** section.\n\n4. Click **Add services**.\n\n5. In the **Specify services to restrict** dialog, select the checkbox next to\n Secure Source Manager. You can use the filter query to locate Secure Source Manager in\n the list.\n\n6. Click **Save**.\n\nAfter you update a service perimeter, it can take up to 30 minutes for the\nchanges to propagate and take effect. During this time, the perimeter might\nblock requests with the following error message: \n\n Error 403: Request is prohibited by organization's policy.\n\nWhat's next\n-----------\n\n- Learn more about [Private Service Connect](/vpc/docs/private-service-connect).\n- Learn more about [Connecting to VMs without external IP addresses](/solutions/connecting-securely#external)."]]
