Cloud Data Loss Prevention (Cloud DLP) kini menjadi bagian dari Sensitive Data Protection. Nama API tetap sama: Cloud Data Loss Prevention API (DLP API). Untuk informasi tentang layanan yang membentuk Perlindungan Data Sensitif, lihat Ringkasan Perlindungan Data Sensitif.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Menjadwalkan pemindaian inspeksi Sensitive Data Protection
Pelajari cara membuat pemicu tugas baru menggunakan Perlindungan Data Sensitif di konsolGoogle Cloud .
Pemicu tugas adalah peristiwa yang mengotomatiskan tugas Sensitive Data Protection untuk memindai repositori penyimpanan (Cloud Storage, BigQuery, dan Firestore dalam mode Datastore (Datastore)). Google Cloud
Untuk mengikuti panduan langkah demi langkah tugas ini langsung di
Google Cloud konsol, klik Pandu saya:
Sign in to your Google Cloud account. If you're new to
Google Cloud,
create an account to evaluate how our products perform in
real-world scenarios. New customers also get $300 in free credits to
run, test, and deploy workloads.
In the Google Cloud console, on the project selector page,
select or create a Google Cloud project.
Di bagian berikut, Anda akan mengonfigurasi dan membuat pemicu tugas untuk
set data publik BigQuery yang berisi
alamat jalan stasiun penyewaan sepeda di suatu kota.
Saat pemicu tugas ini berjalan, Perlindungan Data Sensitif akan memindai sekitar 700 byte data. Anda dapat memeriksa data penyimpanan hingga 1 GB per bulan tanpa biaya. Untuk mengetahui informasi selengkapnya tentang harga, lihat Harga tugas pemeriksaan penyimpanan.
Pilih data input
Di bagian Sensitive Data Protection di konsol Google Cloud , buka
halaman Create job or job trigger.
Untuk mengonfigurasi data input, lakukan hal berikut:
Di bagian Name, tentukan opsi berikut:
Untuk Job ID, masukkan quickstart-job-trigger.
Biarkan Lokasi resource ditetapkan ke Global (wilayah mana pun).
Dalam daftar Storage type, pilih BigQuery, lalu
tentukan opsi berikut:
Untuk Project ID, masukkan bigquery-public-data.
Untuk Dataset ID, masukkan austin_bikeshare.
Untuk ID Tabel, masukkan bikeshare_stations.
Di kolom Maximum number of rows, masukkan 10.
Klik Lanjutkan.
Mengonfigurasi parameter deteksi
Untuk mengonfigurasi deteksi, lakukan hal berikut:
Di bagian InfoTypes, klik Kelola infoTypes.
Di panel InfoTypes, pilih STREET_ADDRESS.
Untuk menutup panel infoTypes, klik Selesai.
Di bagian Nilai minimum keyakinan, pilih Mungkin dari daftar
Kemungkinan.
Nilai Mungkin sudah cukup untuk sebagian besar tujuan. Jika Anda sering mendapatkan kecocokan yang terlalu luas saat menggunakan pemicu tugas ini, pilih nilai minimum keyakinan yang lebih tinggi. Jika Anda mendapatkan terlalu sedikit kecocokan, pilih nilai ambang batas keyakinan yang lebih rendah.
Klik Lanjutkan.
Menambahkan tindakan setelah pemindaian
Klik tombol Beri tahu melalui email.
Klik Lanjutkan.
Setel jadwal
Di daftar Rentang waktu atau jadwal, pilih Buat pemicu untuk menjalankan
tugas pada jadwal berkala.
Di daftar Picu pengulangan pemindaian, pilih Setiap minggu.
Klik Lanjutkan.
Meninjau dan membuat pemicu tugas
Setelah meninjau ringkasan setelan tugas berformat JSON yang baru saja
Anda tentukan, lakukan hal berikut:
Klik Buat.
Di dialog Konfirmasi pembuatan tugas atau pemicu tugas, klik
Konfirmasi pembuatan.
Tunggu satu menit agar Sensitive Data Protection membuat pemicu tugas.
Menjalankan pemicu tugas dan melihat hasilnya
Untuk memicu tugas secara langsung, lakukan langkah berikut:
Di halaman Detail pemicu, klik Jalankan sekarang.
Operasi ini mungkin memerlukan waktu beberapa saat untuk diselesaikan.
Setelah tugas yang Anda buat dijalankan satu kali, lakukan hal berikut:
Di bagian Triggered jobs, pilih ID tugas dari tugas yang dipicu
di kolom Job ID.
Di halaman Detail tugas, lihat hasil tugas.
Pembersihan
Agar akun Google Cloud Anda tidak dikenai biaya untuk
resource yang digunakan pada halaman ini, ikuti langkah-langkah berikut.
Menghapus project
Cara termudah untuk menghilangkan penagihan adalah dengan menghapus project yang Anda
buat untuk tutorial.
Untuk menghapus project:
In the Google Cloud console, go to the Manage resources page.
[[["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,["# Quickstart: Schedule a Sensitive Data Protection inspection scan\n\nSchedule a Sensitive Data Protection inspection scan\n====================================================\n\nLearn how to create a new job trigger using Sensitive Data Protection in the\nGoogle Cloud console.\n\nJob triggers are events that automate running Sensitive Data Protection jobs to\nscan Google Cloud storage repositories (Cloud Storage, BigQuery, and\nFirestore in Datastore mode (Datastore)).\n\n*** ** * ** ***\n\nTo follow step-by-step guidance for this task directly in the\nGoogle Cloud console, click **Guide me**:\n\n[Guide me](https://console.cloud.google.com/freetrial?redirectPath=/?walkthrough_id=dlp--quickstart-create-job-trigger)\n\n*** ** * ** ***\n\nBefore you begin\n----------------\n\nSign in to your Google Cloud account. If you're new to Google Cloud, [create an account](https://console.cloud.google.com/freetrial) to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.\n\nIn the Google Cloud console, on the project selector page,\nselect or create a Google Cloud project.\n| **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n[Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n\n\n[Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n\nEnable the Sensitive Data Protection API.\n\n\n[Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=dlp.googleapis.com) \nIn the Google Cloud console, on the project selector page,\nselect or create a Google Cloud project.\n| **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n[Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n\n\n[Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n\nEnable the Sensitive Data Protection API.\n\n\n[Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=dlp.googleapis.com)\n1.\n\n\n Enable the Sensitive Data Protection API.\n\n\n [Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=dlp.googleapis.com)\n\nCreate a job trigger\n--------------------\n\nIn the following sections, you configure and create a job trigger for a\n[BigQuery public dataset](/bigquery/public-data) that contains\nthe street addresses of bike share stations in a city.\n\nWhen this job trigger runs, Sensitive Data Protection scans around 700 bytes of\ndata. You can inspect up to 1 GB of storage data per month free of charge. For\nmore information about pricing, see [Storage inspection job\npricing](/sensitive-data-protection/pricing#storage-pricing).\n\n### Choose input data\n\n1. In the Sensitive Data Protection section of the Google Cloud console, go\n to the **Create job or job trigger** page.\n\n [Go to Create job or job trigger](https://console.cloud.google.com/security/sensitive-data-protection/create/job;source=7)\n2. To configure input data, do the following:\n\n 1. In the **Name** section, define the following options:\n\n - For **Job ID** , enter `quickstart-job-trigger`.\n\n - Keep **Resource location** set to **Global (any region)**.\n\n 2. In the **Storage type** list, select **BigQuery**, and then\n define the following options:\n\n - For **Project ID** , enter `bigquery-public-data`.\n\n - For **Dataset ID** , enter `austin_bikeshare`.\n\n - For **Table ID** , enter `bikeshare_stations`.\n\n 3. In the **Maximum number of rows** field, enter `10`.\n\n3. Click **Continue**.\n\n### Configure detection parameters\n\n1. To configure detection, do the following:\n\n 1. In the **InfoTypes** section, click **Manage infoTypes**.\n\n 2. In the **InfoTypes** pane, select **STREET_ADDRESS**.\n\n 3. To close the **infoTypes** pane, click **Done**.\n\n 4. In the **Confidence threshold** section, select **Possible** from the\n **Likelihood** list.\n\n The value **Possible** is sufficient for most purposes. If you routinely\n get matches that are too broad when you use this job trigger, select a\n higher confidence threshold value. If you get too few matches, select a\n lower confidence threshold value.\n2. Click **Continue**.\n\n### Add post-scan actions\n\n1. Click the **Notify by email** toggle.\n\n2. Click **Continue**.\n\n### Set a schedule\n\n1. In the **Time span or schedule** list, select **Create a trigger to run the\n job on a periodic schedule**.\n\n | **Important:** Selecting **Create a trigger to run the job on a periodic\n | schedule** is what makes a job into a job trigger. If you don't specify a schedule, you create a single job that runs only once.\n2. In the **Trigger scan repeats** list, select **Weekly**.\n\n3. Click **Continue**.\n\n### Review and create the job trigger\n\nAfter you review the JSON-formatted summary of the job settings you just\nspecified, do the following:\n\n1. Click **Create**.\n\n2. In the **Confirm job or job trigger create** dialog, click\n **Confirm create**.\n\n Allow a minute for Sensitive Data Protection to create the job trigger.\n\nRun the job trigger and view results\n------------------------------------\n\nTo trigger a job immediately, do the following:\n\n1. On the **Trigger details** page, click **Run now**.\n\n This operation might take some time to complete.\n2. After the job that you created runs once, do the following:\n\n 1. In the **Triggered jobs** section, select the job ID of the triggered job\n in the **Job ID** column.\n\n 2. On the **Job details** page, view the job results.\n\nClean up\n--------\n\n\nTo avoid incurring charges to your Google Cloud account for\nthe resources used on this page, follow these steps.\n\n### Delete the project\n\n\nThe easiest way to eliminate billing is to delete the project that you\ncreated for the tutorial.\n\nTo delete the project:\n\n| **Caution** : Deleting a project has the following effects:\n|\n| - **Everything in the project is deleted.** If you used an existing project for the tasks in this document, when you delete it, you also delete any other work you've done in the project.\n| - **Custom project IDs are lost.** When you created this project, you might have created a custom project ID that you want to use in the future. To preserve the URLs that use the project ID, such as an `appspot.com` URL, delete selected resources inside the project instead of deleting the whole project.\n|\n|\n| If you plan to explore multiple architectures, tutorials, or quickstarts, reusing projects\n| can help you avoid exceeding project quota limits.\n1. In the Google Cloud console, go to the **Manage resources** page.\n\n [Go to Manage resources](https://console.cloud.google.com/iam-admin/projects)\n2. In the project list, select the project that you want to delete, and then click **Delete**.\n3. In the dialog, type the project ID, and then click **Shut down** to delete the project.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n### Delete the job trigger\n\nIf you created the job trigger in an existing project and you no longer need\nthe job trigger, follow these steps:\n\n1. In the Google Cloud console, go to the Sensitive Data Protection page.\n\n [Go to Sensitive Data Protection](https://console.cloud.google.com/security/sensitive-data-protection;source=7)\n2. If necessary, select the project in which you created a job trigger from the\n Google Cloud console toolbar.\n\n3. Click the **Inspection** tab, and then click the **Job triggers** tab. The\n Google Cloud console displays a list of all the job triggers for the\n current project.\n\n4. In the **Actions** column for the job trigger you want to delete, click the\n trigger actions menu (more_vert),\n click **Delete** , and then click **Confirm**.\n\nWhat's next\n-----------\n\n- Learn more about [creating and scheduling Sensitive Data Protection inspection\n jobs](/sensitive-data-protection/docs/creating-job-triggers).\n\n- Learn more about [creating Sensitive Data Protection inspection\n templates](/sensitive-data-protection/docs/creating-templates-inspect).\n\n- To add actions you want Sensitive Data Protection to take after a trigger job\n completes, see [Add actions](/sensitive-data-protection/docs/creating-job-triggers#add-actions).\n\n- To specify the types of sensitive data you want to scan for, see [Configure\n detection](/sensitive-data-protection/docs/creating-job-triggers#configure-detection).\n\n- To create a BigQuery dataset in a project, see [Creating\n datasets](/bigquery/docs/datasets)."]]
