content メソッドを使用してデータを処理する場合、データは Google Cloudに保存されません。リクエスト構成とペイロードはメモリ内で同期的に処理され、キャッシュに保存されません。
ストレージ メソッド
ストレージ メソッドは、BigQuery テーブルや Cloud Storage バケットなどの Google Cloudデータを検査できる非同期オペレーションです。 Google Cloudで所有しているリソースと同様に、データの保存、アクセス、保護の方法を制御できます。機密データの保護は、データが存在するリージョンと同じリージョンでデータを処理し、そのリージョンに検査ジョブを保存します。
検査ジョブには、設定した構成の詳細と結果の概要が含まれます。機密データの保護が保存する結果の概要には、検査されたデータと、機密情報を含む実際の文字列（機密データの保護では引用とも呼ばれる）は含まれません。ジョブ（結果の概要を含む）は Google Cloud コンソールで、または DLP API を介して削除できます。
ハイブリッド メソッドは、 Google Cloudの外部に保存されているデータを含め、どこに保存されているデータでも検査できる非同期オペレーションです。検査ジョブでは、機密データの保護がデータを処理する場所と、ジョブを保存する場所を指定します。
検査ジョブには、設定した構成の詳細と結果の概要が含まれます。機密データの保護が保存する結果の概要には、検査されたデータと、機密情報を含む実際の文字列（機密データの保護では引用とも呼ばれる）は含まれません。ジョブ（結果の概要を含む）は Google Cloud コンソールで、または DLP API を介して削除できます。
[[["わかりやすい","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,["# Sensitive Data Protection data security\n\nThis topic provides information about Sensitive Data Protection and data security,\nincluding certifications, compliance (including GDPR), and encryption. For\nadditional information about data security and Google Cloud, see [Google Cloud\nSecurity](/security).\n\nCertifications\n--------------\n\nSensitive Data Protection meets various certifications and compliance standards,\nincluding the following. This is not an exhaustive list.\n\n- [ISO/IEC 27001](/security/compliance/iso-27001)\n- [ISO/IEC 27017:2015](/security/compliance/iso-27017)\n- [ISO/IEC 27018:2014](/security/compliance/iso-27018)\n- [Payment Card Industry Data Security Standard (PCI\n DSS)](/security/compliance/pci-dss)\n- [HIPAA business associate agreement\n (BAA)](/security/compliance/hipaa#covered-products)\n- [Multi-Tier Cloud Security (MTCS) Singapore Standard (SS)\n 584](/security/compliance/mtcs)\n\nFor more information about the compliance offerings that Google Cloud\nservices satisfy, see [Compliance resource center](/security/compliance).\n\nGDPR\n----\n\nCompliance with the European Union General Data Protection Regulation (GDPR) is\na top priority for Google Cloud and our customers.\n\nWhile Sensitive Data Protection offers several built-in [infoType\ndetectors](/sensitive-data-protection/docs/concepts-infotypes) that may be applicable to GDPR\ncompliance, you may need to [build your own custom infoType\ndetectors](/sensitive-data-protection/docs/creating-custom-infotypes), and should test thoroughly to\nensure that the tool fits your specific needs.\n\nYou are encouraged to read the [Google Cloud and GDPR\noverview](/security/gdpr) to learn more about the available resources for GDPR\ncompliance with Google Cloud.\n\nEncryption\n----------\n\nFor information about encryption in transit and Google Cloud services, see\n[Encryption in Transit in Google Cloud](/security/encryption-in-transit).\n\nFor information about encryption at rest and Google Cloud services, see\n[Encryption at Rest in\nGoogle Cloud](/security/encryption/default-encryption).\n\nHow data is stored\n------------------\n\nSensitive Data Protection processes and stores your data depending on\nthe [service method](/sensitive-data-protection/docs/concepts-method-types) that you use.\n\n### Content methods\n\nWhen you use [`content`\nmethods](/sensitive-data-protection/docs/concepts-method-types#content-methods) to process your data,\nyour data isn't stored on Google Cloud. Your request configuration and\npayload are processed synchronously in memory and are not cached.\n\n### Storage methods\n\nStorage methods are asynchronous operations that let you inspect Google Cloud\ndata, such as data in BigQuery tables and Cloud Storage\nbuckets. You control how that data is stored, accessed, and protected, just like\nany resource that you own in Google Cloud.\nSensitive Data Protection processes your data in the same region where it\nresides and stores the inspection job in that region.\n\n\nThe inspection job includes the configuration details that you set and the\nresult summary. The [result summary](/sensitive-data-protection/docs/reference/rest/v2/projects.dlpJobs#result)\nthat\nSensitive Data Protection stores doesn't include any of the inspected data\nand the actual strings containing the sensitive information (also called\n*quotes* in\nSensitive Data Protection). You can delete the job, including the result\nsummary, [through the\nGoogle Cloud console](/sensitive-data-protection/docs/creating-job-triggers#delete-job) or [through\nthe\nDLP API](/sensitive-data-protection/docs/reference/rest/v2/projects.locations.dlpJobs/delete).\n\n\u003cbr /\u003e\n\nWhen configuring your inspection job, you can instruct\nSensitive Data Protection to export the findings to a BigQuery\ntable of your choice. Depending on your settings, the quotes can be included in\nthe exported findings. You own the BigQuery table and control how\nit's stored, accessed, and protected.\n\n\u003cbr /\u003e\n\n### Hybrid methods\n\nHybrid methods are asynchronous operations that let you inspect data that is\nstored anywhere, including data stored outside Google Cloud. In your\ninspection job, you specify where you want Sensitive Data Protection to\nprocess the data and save the job.\n\n\nThe inspection job includes the configuration details that you set and the\nresult summary. The [result summary](/sensitive-data-protection/docs/reference/rest/v2/projects.dlpJobs#result)\nthat\nSensitive Data Protection stores doesn't include any of the inspected data\nand the actual strings containing the sensitive information (also called\n*quotes* in\nSensitive Data Protection). You can delete the job, including the result\nsummary, [through the\nGoogle Cloud console](/sensitive-data-protection/docs/creating-job-triggers#delete-job) or [through\nthe\nDLP API](/sensitive-data-protection/docs/reference/rest/v2/projects.locations.dlpJobs/delete).\n\n\u003cbr /\u003e\n\nWhen configuring your inspection job, you can instruct\nSensitive Data Protection to export the findings to a BigQuery\ntable of your choice. Depending on your settings, the quotes can be included in\nthe exported findings. You own the BigQuery table and control how\nit's stored, accessed, and protected.\n\n\u003cbr /\u003e\n\n### Discovery\n\nSensitive Data Protection processes your data assets in the region or\nmulti-region where they reside and stores the generated data profiles in the\nsame region or multi-region. For more information about how the\ndiscovery service supports data residency requirements, see [Data\nresidency considerations](/sensitive-data-protection/docs/data-profiles#data-residency).\n\n### How custom infoTypes are stored\n\nYou create a [custom infoType](/sensitive-data-protection/docs/creating-custom-infotypes) by\nspecifying a regular expression or a list of terms (words and phrases) that you\nwant to scan for. You can provide the terms by listing them directly in the\nSensitive Data Protection request. Alternatively, you can reference a\nBigQuery table or a Cloud Storage file or folder containing\nthe list of terms.\n\nThe terms that make up a custom infoType are potentially sensitive. They are\nstored depending on how you provide them to Sensitive Data Protection:\n\n- If you list the terms directly in a [content\n method](#content-methods), then the data is processed synchronously in memory and isn't stored or cached.\n- If you list the terms directly in an inspection job, then the terms are saved with the inspection job. For more information about how inspection jobs are stored, see [Storage methods](#storage-methods) and [Hybrid\n methods](#hybrid-methods).\n- If you list the terms directly in an inspection template, then the terms are saved with the inspection template. The inspection template is stored in the region that you set when creating the template. You can delete an inspection template [through the\n Google Cloud console](/sensitive-data-protection/docs/creating-templates-inspect#delete_inspection_templates) or [through the\n DLP API](/sensitive-data-protection/docs/reference/rest/v2/projects.locations.inspectTemplates/delete).\n- If you store the terms in a BigQuery table or Cloud Storage file or folder, then you control how they are stored, accessed, and protected, just like any resource that you own in Google Cloud.\n\nPrivacy\n-------\n\nFor information about how Google Cloud protects your privacy, see [Privacy\nResource Center](https://cloud.google.com/privacy).\n\nNext steps\n----------\n\nFor information about the security measures in place for Google's Cloud\nServices, please see the [Google Cloud Security](/security) page."]]
