Mengaktifkan dan menggunakan Notebook Security Scanner
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Anda dapat mengaktifkan dan menggunakan Notebook Security Scanner
untuk mendeteksi kerentanan dalam paket Python yang digunakan di
notebook Colab Enterprise (file dengan ekstensi nama file ipynb)
dan menyelesaikan temuan kerentanan paket tersebut.
Setelah Anda mengaktifkan Pemindai Keamanan Notebook, pemindai ini akan memindai notebook Colab Enterprise sekali setiap 24 jam dan memublikasikan temuan kerentanan paket ke halaman Temuan Security Command Center.
Anda dapat menggunakan Pemindai Keamanan Notebook untuk notebook Colab Enterprise yang dibuat di wilayah berikut: us-central1, us-east4, us-west1, dan europe-west4.
Mengaktifkan Notebook Security Scanner
Anda dapat mengaktifkan Pemindai Keamanan Notebook di tingkat organisasi
atau tingkat project.
Cara Anda mengaktifkan Notebook Security Scanner bergantung pada apakah Security Command Center perlu diaktifkan untuk organisasi atau project Anda, atau pada paket Security Command Center yang diaktifkan untuk organisasi atau project Anda.
Bergantung pada kasus penggunaan Anda, ikuti petunjuk di bagian yang sesuai:
Meninjau dan menyelesaikan temuan kerentanan paket
Setelah Anda mengaktifkan Pemindai Keamanan Notebook, Pemindai Keamanan Notebook akan memindai notebook Colab Enterprise (file dengan ekstensi nama file ipynb) di project atau organisasi Anda setiap 24 jam untuk mendeteksi kerentanan dalam paket Python dan memublikasikan temuan ini ke halaman Temuan Security Command Center. Untuk notebook Colab Enterprise yang baru dibuat, temuan kerentanan paket mungkin memerlukan waktu maksimal empat jam untuk muncul di halaman Temuan Security Command Center.
Untuk meninjau temuan kerentanan paket di Security Command Center, ikuti langkah-langkah berikut:
Di konsol Google Cloud , buka halaman Temuan Security Command Center.
[[["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."],[],[],null,["# Enable and use Notebook Security Scanner\n\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n|\n| **Note:** This feature is available with either the\n| [Enterprise or Premium tier](/security-command-center/docs/service-tiers) of Security Command Center.\n\nYou can enable and use Notebook Security Scanner\nto detect vulnerabilities in Python packages that are used in\nColab Enterprise notebooks (files with the `ipynb` filename extension)\nand resolve those package vulnerability findings.\n\nAfter you enable Notebook Security Scanner, it scans Colab Enterprise\nnotebooks once in every 24 hours and publishes the package vulnerability findings\nto the Security Command Center **Findings** page.\n\nYou can use Notebook Security Scanner for Colab Enterprise notebooks\nthat are created in the following regions: `us-central1`, `us-east4`, `us-west1`,\nand `europe-west4`.\n\nEnable Notebook Security Scanner\n--------------------------------\n\nYou can enable Notebook Security Scanner at the organization level\nor project level.\n\nThe way you enable Notebook Security Scanner depends on whether\nSecurity Command Center needs to be activated for your organization or project, or on\nthe Security Command Center tier that is activated for your organization or project.\nDepending on your use case, follow the instructions in the appropriate section: \n\n### New activation Premium tier\n\nIf your organization doesn't have Security Command Center,\nthen activate Security Command Center Premium tier for your organization or project,\nand enable Notebook Security Scanner.\n\n1. In the Google Cloud console, go to the Security Command Center page.\n\n [Go to Security Command Center](https://console.cloud.google.com/security/command-center/config/services)\n2. In the resource selector, select your organization or project.\n3. Click **Get Security Command Center**.\n4. Select the **Premium** tier, and click **Next**.\n5. For **Notebook Security Scanner** , select **Enable** from the list, and click **Next**.\n6. Select **Grant roles automatically** , and then click **Grant roles**.\n7. After the service account is provisioned, click **Next**.\n8. To complete the activation process, click **Finish**.\n\n### New activation Enterprise tier\n\nIf your organization doesn't have Security Command Center,\nthen [activate Security Command Center Enterprise tier](/security-command-center/docs/activate-enterprise-tier#activate-the-security-command-center-enterprise-tier) for your organization,\nand enable Notebook Security Scanner.\n\n### Existing Premium or Enterprise tier\n\nIf the Security Command Center Premium or Enterprise tier is activated for your\norganization or project, then enable Notebook Security Scanner.\n\n1. In the Google Cloud console, go to the Security Command Center page.\n\n [Go to Security Command Center](https://console.cloud.google.com/security/command-center/config/services)\n2. Click **settingsSettings**.\n3. In the **Notebook Security Scanner** card, click **Manage settings**.\n4. For your project, select **Enable** from the **Notebook Security Scanner** column.\n\nReview and resolve package vulnerability findings\n-------------------------------------------------\n\nAfter you enable Notebook Security Scanner, Notebook Security Scanner\nscans the Colab Enterprise notebooks (files with the `ipynb` filename extension)\nin your project or organization every 24 hours to detect vulnerabilities in\nPython packages and publishes these findings to the Security Command Center\n**Findings** page. For a newly created Colab Enterprise\nnotebook, the package vulnerability findings might take a maximum of four hours\nto appear in the Security Command Center **Findings** page.\n\nTo review package vulnerability findings in Security Command Center, follow these\nsteps:\n\n1. In the Google Cloud console, go to the Security Command Center **Findings** page.\n\n [Go to Findings](https://console.cloud.google.com/security/command-center/findingsv2)\n2. In the resource selector, select your organization or project.\n\n3. In the **Quick filters** section, go to the **Source display name** subsection,\n and then select **Notebook Security Scanner**.\n\n The **Findings query results** panel shows only the\n package vulnerability findings of Notebook Security Scanner.\n4. To view details of a specific finding, click the finding name in the\n **Category** column. The finding details panel expands to display a summary\n of the finding details.\n\n | **Note:** There might be some vulnerabilities published with packages and versions which might not be present in the notebook. This is because, for the Python packages that are being installed without versions in unexecuted code cells, Notebook Security Scanner assumes the latest package version according to the [Python Package Index (PyPI)](https://pypi.org/) and publishes any vulnerabilities.\n5. To resolve a package vulnerability finding, follow the steps mentioned in the\n **Next steps** section of the finding.\n\n In some cases, a fix for a package vulnerability might not be available.\n In such cases, we recommend that you use alternative Python packages.\n\nWhat's next\n-----------\n\n- [View package vulnerability findings](/security-command-center/docs/view-python-package-vulnerabilities)."]]
