Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Kontrol Layanan VPC meningkatkan kemampuan Anda untuk mengurangi risiko penyalinan atau transfer data tanpa izin dari layanan yang dikelola Google.
Dengan Kontrol Layanan VPC, Anda dapat mengonfigurasi perimeter keamanan di sekitar resource layanan yang dikelola Google dan mengontrol pergerakan data di seluruh batas perimeter.
Menggunakan Analisis Artefak dengan Kontrol Layanan VPC
Kontrol Layanan VPC memberikan dukungan untuk Analisis Artefak.
Bergantung pada pipeline, Anda mungkin perlu menambahkan beberapa layanan lain ke perimeter layanan. Untuk mempelajari lebih lanjut, lihat
Produk dan batasan yang didukung.
Untuk mengetahui petunjuk umum tentang cara menambahkan Artifact Analysis ke perimeter layanan, lihat Membuat perimeter layanan.
Pastikan layanan lain yang Anda gunakan dengan Artifact Analysis juga berada dalam perimeter, termasuk: Google Cloud
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 UTC."],[[["\u003cp\u003eVPC Service Controls enhances security by preventing unauthorized data transfer from Google-managed services.\u003c/p\u003e\n"],["\u003cp\u003eSecurity perimeters can be configured around resources using VPC Service Controls to manage data movement across these boundaries.\u003c/p\u003e\n"],["\u003cp\u003eVPC Service Controls supports Artifact Analysis, and other services used in conjunction may need to be added to the service perimeter.\u003c/p\u003e\n"],["\u003cp\u003eArtifact Registry, Container Registry, and Binary Authorization should also be included in the perimeter when used with Artifact Analysis.\u003c/p\u003e\n"],["\u003cp\u003eContainer registry will be shut down March 18, 2025 and should not be used, with Artifact registry being the new default.\u003c/p\u003e\n"]]],[],null,["# Protect Artifact Analysis in a service perimeter\n\n[VPC Service Controls](/vpc-service-controls/docs/overview) improves your\nability to mitigate the risk of unauthorized copying or transfer of data\nfrom Google-managed services.\n\nWith VPC Service Controls, you can configure security perimeters around the\nresources of your Google-managed services and control the movement of data\nacross the perimeter boundary.\n\nUse Artifact Analysis with VPC Service Controls\n-----------------------------------------------\n\nVPC Service Controls provides support for Artifact Analysis.\nDepending on your pipeline, it might require adding some other services to\nyour service perimeter. To learn more, see\n[Supported products and limitations](/vpc-service-controls/docs/supported-products?#table_artifact-analysis).\n\nFor general instructions to add Artifact Analysis to a service\nperimeter, see [Creating a service perimeter](/vpc-service-controls/docs/create-service-perimeters).\n\nEnsure that other Google Cloud services that you use with\nArtifact Analysis are also in the perimeter, including:\n\n- [Artifact Registry](/artifact-registry/docs/securing-with-vpc-sc)\n- [Binary Authorization](/binary-authorization/docs/securing-with-vpcsc)\n\n| **Caution:** Container Registry is deprecated. Effective March 18, 2025,\n| Container Registry is shut down, and writing images to Container Registry is unavailable. For\n| details on the deprecation and how to migrate to Artifact Registry, see\n| [Container Registry deprecation](/container-registry/docs/deprecations/container-registry-deprecation)."]]
