Beberapa produk dan fitur sedang dalam proses penggantian nama. Fitur playbook dan alur generatif juga dimigrasikan ke satu konsol gabungan. Lihat detailnya.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Setelan keamanan digunakan untuk mengonfigurasi penyamaran data dan retensi data.
Misalnya, setelan ini mengontrol cara data disamarkan di
Logging Cloud
dan logging interaksi yang digunakan oleh
Histori percakapan.
Setelan keamanan ditetapkan di tingkat project. Jika pengguna diberi akses ke agen dalam project, mereka dapat melihat setelan Keamanan tingkat project. Untuk memperbarui setelan Keamanan tingkat project, pengguna harus memiliki izin dialogflow.securitySettings..
Tabel berikut memberikan deskripsi ringkasan setelan.
Untuk informasi selengkapnya tentang setelan, lihat
referensi SecuritySettings RPC.
Setelan keamanan
Deskripsi
redaction_strategy
Strategi yang digunakan untuk penyamaran.
redaction_scope
Tempat penyamaran data diterapkan.
inspect_template
Nama template pemeriksaan DLP. Tidak ada biaya tambahan saat menggunakan DLP di Agen Percakapan (Dialogflow CX).
deidentify_template
Nama template de-identifikasi DLP. Tidak ada biaya tambahan saat menggunakan DLP di Agen Percakapan (Dialogflow CX).
purge_data_types
Data yang akan dihapus saat penghapusan permanen retensi data dipicu.
retention_window_days
Jumlah hari data disimpan.
Beberapa setelan keamanan dapat dikonfigurasi di setiap
lokasi.
Setiap agen dapat menentukan setelan keamanan yang akan diterapkan, dan setiap setelan dapat diterapkan ke beberapa agen dalam project dan lokasi yang sama.
Untuk mengetahui informasi selengkapnya tentang cara data diterapkan di berbagai tingkat, lihat
tingkat penerapan data.
Jika tidak ada setelan keamanan yang ditentukan di agen,
tidak ada penyamaran yang akan diterapkan.
Membuat resource setelan keamanan
Untuk membuat resource setelan keamanan di lokasi tertentu:
[[["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-18 UTC."],[[["\u003cp\u003eSecurity settings at the project level configure data redaction and retention for data in Cloud Logging and Conversation history, with access and updates requiring specific Dialogflow permissions.\u003c/p\u003e\n"],["\u003cp\u003eThese settings include various options like redaction strategy and scope, DLP inspect and deidentify templates, data purge types, and the number of days data is retained.\u003c/p\u003e\n"],["\u003cp\u003eMultiple security settings can be configured per location, applied to one or more agents within the same project and location, while not specifying a setting results in no redaction.\u003c/p\u003e\n"],["\u003cp\u003eSecurity settings can be managed through the Dialogflow CX console or via API methods, allowing for the creation of new settings or the application of existing settings to agents.\u003c/p\u003e\n"],["\u003cp\u003eA default template is used if DLP is not defined, which could be unreliable at identifying certain types of data; therefore it is recommended that users create their own DLP template.\u003c/p\u003e\n"]]],[],null,["# Security settings are used to configure data redaction and data retention.\nFor example, these settings control how data is redacted in\n[Cloud logging](/dialogflow/cx/docs/concept/logging)\nand interaction logging used by\n[Conversation history](/dialogflow/cx/docs/concept/conversation-history).\n\nSecurity settings are set at the project level. If a user is granted [access](/dialogflow/cx/docs/concept/access-control#df-console) to an agent in a project, they can view project-level Security settings. To update project-level Security settings, a user should have the [dialogflow.securitySettings. permission](/iam/docs/understanding-roles#dialogflow.aamAdmin).\n| **Note:** For other redaction options, see [parameter redaction](/dialogflow/cx/docs/concept/parameter#redact).\n\nThe following table provides summary descriptions of the settings.\nFor more information on the settings, see the\n[RPC SecuritySettings reference](/dialogflow/cx/docs/reference/rpc/google.cloud.dialogflow.cx.v3#google.cloud.dialogflow.cx.v3.SecuritySettings).\n\nMultiple security settings can be configured in each\n[location](/dialogflow/cx/docs/concept/region).\nEach agent can specify the security settings to apply, and each setting can be\napplied to multiple agents in the same project and location.\nFor more information about how data is applied at varying levels, see the\n[data application levels](/dialogflow/cx/docs/concept/data-level).\n\nIf no security settings are specified in an agent,\nno redaction will be applied.\n\nCreate a security settings resource\n-----------------------------------\n\nTo create a security settings resource in a particular location: \n\n### Console\n\n1. Open the [Dialogflow CX console](https://dialogflow.cloud.google.com/cx/projects).\n2. Choose your Google Cloud project.\n3. Select your agent.\n4. Click **Agent Settings**.\n5. Click the **Security** tab.\n6. Click **Manage Security Settings**. The CCAI console opens in a new tab.\n7. Click **Create Security Settings** in the CCAI console.\n8. Enter security settings configuration.\n9. Click **Create**.\n\n### API\n\nSee the `create` method for the `SecuritySettings` type.\n\n\nGo to the SecuritySettings API reference \n**Select a protocol and version for the SecuritySettings reference:**\n\nClose\n\n\u003cbr /\u003e\n\nSpecify a security setting in agent\n-----------------------------------\n\nTo specify a security setting in agent: \n\n### Console\n\n1. Open the [Dialogflow CX console](https://dialogflow.cloud.google.com/cx/projects).\n2. Choose your Google Cloud project.\n3. Select your agent.\n4. Click **Agent Settings**.\n5. Click the **Security** tab.\n6. Select the settings in **Security settings** drop down menu.\n7. Click **Save**.\n\n### API\n\nSee the `patch/update` methods for the `Agent` type.\n\n\nGo to the Agent API reference \n**Select a protocol and version for the Agent reference:**\n\nClose\n\n\u003cbr /\u003e\n\n| **Note:** If the DLP inspect template is not defined, a default template is used. The default template only has some of the [infoType detectors](/sensitive-data-protection/docs/concepts-infotypes) enabled and may be unreliable for identifying and removing the types as per the end-users requirement. Hence, it is recommended to always [create](https://console.cloud.google.com/security/dlp/create/template) a DLP template whenever possible.\n| **Note:** It may take hours for updates on these settings to propagate to all the related components and take effect."]]
