混合方法是一组异步 API 方法，可让您扫描从几乎任何来源发送的数据的敏感信息并将其存储在 Google Cloud中。混合方法与内容方法的类似之处在于因为您要检查的数据包含在一个或多个检查请求中；但是，与内容方法不同的是，混合方法不会在 API 响应中返回检查结果。相反，检查结果在服务器端以异步方式进行处理，结果按标签形式存储，方式类似于存储方法。
如需启用混合检查，请使用 dlpJobs 资源创建 Sensitive Data Protection 作业。每项混合作业都作为代管式服务运行，旨在监听检查请求，并执行 Sensitive Data Protection 操作（例如保存或发布发现结果）。除了这些可选操作之外，Sensitive Data Protection 还会创建并存储作业详情，包括作业状态、扫描的字节数以及每个 infoType 的发现结果摘要。您可以在 Google Cloud 控制台中使用 DLP API 或 Sensitive Data Protection 管理作业。
您可以配置发现功能，以扫描存储在 Google Cloud BigQuery、Cloud SQL、Cloud Storage 和 Vertex AI 等系统中的数据。如果您已启用 Security Command Center Enterprise，还可以使用 Sensitive Data Protection 扫描其他云提供商的数据。
您可以指定希望 Sensitive Data Protection 在每次发现扫描后执行的操作。例如，您可以将扫描结果发送到其他Google Cloud 服务（例如 Security Command Center 和 Google Security Operations），以提高组织数据安全状况的可见性。您可以配置发现服务来标记已分析的资源，以便自动授予或拒绝对这些资源的 IAM 访问权限。您还可以将数据剖析文件导出到 BigQuery。您可以将导出的个人资料关联到 Looker，以查看预先生成的报告。您还可以创建自己的自定义查询和报告。
如需启用发现功能，请创建 DiscoveryConfig 资源。发现功能会根据您在发现配置中设置的范围和频率运行。如需了解 Sensitive Data Protection 将生成的分析结果存储在何处，请参阅数据驻留注意事项。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Method types\n\nSensitive Data Protection includes different types of methods that you can use to\ninspect, transform (*de-identify*), discover, and classify data. Using these\nmethods, you can scan data both on and off Google Cloud and optimize the\nbehavior of Sensitive Data Protection for different types of workloads.\n\nSensitive Data Protection provides the following method types:\n\n- [Content methods](#content-methods)\n- [Storage methods](#storage-methods)\n- [Hybrid methods](#hybrid-methods)\n- [Discovery methods](#discovery-methods)\n\nInspection and de-identification methods\n----------------------------------------\n\nThis section describes the methods that you can use to locate and, optionally,\nde-identify each piece of data that matches an [information\ntype](/sensitive-data-protection/docs/infotypes-reference) listed in your your [inspection\nconfiguration](/sensitive-data-protection/docs/reference/rest/v2/InspectConfig).\n\n### Content methods\n\n*Content methods* are synchronous, stateless methods. The data to be inspected\nor transformed is sent directly in the request to the DLP API.\nSensitive Data Protection inspection findings or transformed data is returned in\nthe API response. Request data is encrypted in transit and is not stored.\n\nTo learn more, explore the REST API reference for content methods:\n\n- [`content.inspect`](/sensitive-data-protection/docs/reference/rest/v2/projects.content/inspect)\n- [`content.deidentify`](/sensitive-data-protection/docs/reference/rest/v2/projects.content/deidentify)\n- [`content.reidentify`](/sensitive-data-protection/docs/reference/rest/v2/projects.content/reidentify)\n- [`image.redact`](/sensitive-data-protection/docs/reference/rest/v2/projects.image/redact)\n\n### Storage methods\n\n*Storage methods* are designed to inspect data stored on Google Cloud in systems\nlike [Cloud Storage](/storage), [BigQuery](/bigquery), and\n[Firestore in Datastore mode (Datastore)](/datastore). To enable storage inspection, you create a\nSensitive Data Protection job using the\n[`dlpJobs`](/sensitive-data-protection/docs/reference/rest/v2/projects.dlpJobs)\nresource. Each job runs as a managed service to inspect data and then perform\n[Sensitive Data Protection actions](/sensitive-data-protection/docs/concepts-actions) such as save or publish findings. In\naddition to these optional actions, Sensitive Data Protection creates and stores\ndetails about the job including job status, bytes scanned, and summary findings\nper infoType. You can manage jobs using the DLP API or\nSensitive Data Protection in the [Google Cloud console](https://console.cloud.google.com/security/sensitive-data-protection).\n\nTo learn more, explore the REST API reference for the\n[`projects.dlpJobs`](/sensitive-data-protection/docs/reference/rest/v2/projects.dlpJobs) resource. You specify the\nstorage details in the\n[`StorageConfig`](/sensitive-data-protection/docs/reference/rest/v2/InspectJobConfig#storageconfig) object.\n\n### Hybrid methods\n\n*Hybrid methods* are a set of asynchronous API methods that allow you to scan\npayloads of data sent from virtually any source for sensitive information and\nstore the findings in Google Cloud. Hybrid methods are similar to\n[content methods](#content-methods) in that the data you want to inspect is\nincluded in one or more inspection requests; however, unlike\n[content methods](#content-methods), *hybrid methods* do not return inspection\nresults in the API response. Instead, inspection results are processed\nserver-side asynchronously and results are tabulated and stored in a\nmanner similar to [storage methods](#storage-methods).\n\nTo enable hybrid inspection, you create a Sensitive Data Protection job using the\n[`dlpJobs`](/sensitive-data-protection/docs/reference/rest/v2/projects.dlpJobs)\nresource. Each *hybrid* job runs as a managed service to listen for inspection\nrequests and performs [Sensitive Data Protection actions](/sensitive-data-protection/docs/concepts-actions) such as\nsave or publish findings. In addition to these optional actions,\nSensitive Data Protection creates and stores details about the job including job\nstatus, bytes scanned, and summary findings per infoType. You can manage jobs\nusing the DLP API or Sensitive Data Protection in the\n[Google Cloud console](https://console.cloud.google.com/security/sensitive-data-protection).\n\nTo learn more, explore the REST API reference for the\n[`projects.dlpJobs`](/sensitive-data-protection/docs/reference/rest/v2/projects.dlpJobs) resource. You specify the\ndata source in the `hybridOptions` field of the\n[`StorageConfig`](/sensitive-data-protection/docs/reference/rest/v2/InspectJobConfig#storageconfig) object.\n\nDiscovery methods\n-----------------\n\n*Discovery methods* allow you to configure [sensitive data\ndiscovery](/sensitive-data-protection/docs/data-profiles) to generate *data profiles*. Data\nprofiles provide insights to help you determine where sensitive data reside in\nyour organization, what kind of sensitive data you are storing, and whether that\ndata has access controls in place.\n\nYou can configure discovery to scan data stored on Google Cloud in systems like\nBigQuery, Cloud SQL, Cloud Storage, and Vertex AI. If you\nhave a Security Command Center Enterprise activation, you can also use\nSensitive Data Protection to scan data from other cloud providers.\n\nYou can specify actions that you want Sensitive Data Protection to perform after\neach discovery scan. For example, you can send scan results to other\nGoogle Cloud services---like Security Command Center and\nGoogle Security Operations---to increase your visibility into your\norganization's data security posture. You can configure the discovery service to\ntag your profiled resources to automatically grant or deny IAM\naccess to those resources. You can also export the data profiles to\nBigQuery. You can connect the exported profiles to Looker to\n[view the premade\nreport](/sensitive-data-protection/docs/analyze-data-profiles#use_a_premade_report). You can\nalso create your own custom queries and reports.\n\nTo enable discovery, you create a\n[`DiscoveryConfig`](/sensitive-data-protection/docs/reference/rest/v2/organizations.locations.discoveryConfigs)\nresource. Discovery runs based on the scope and frequency that you set in the\ndiscovery configuration. For information about where Sensitive Data Protection\nstores the generated profiles, see [Data residency\nconsiderations](/sensitive-data-protection/docs/data-profiles#data-residency).\n\nYou can manage the discovery configurations, data profiles, and Cloud SQL\nconnections using the DLP API or the\n[Google Cloud console](https://console.cloud.google.com/security/sensitive-data-protection).\n\nTo learn more, explore the REST API reference for the following:\n\n- Discovery configurations\n\n - [`organizations.locations.discoveryConfigs`](/sensitive-data-protection/docs/reference/rest/v2/organizations.locations.discoveryConfigs)\n - [`projects.locations.discoveryConfigs`](/sensitive-data-protection/docs/reference/rest/v2/projects.locations.discoveryConfigs)\n- Connections\n\n Connections are relevant only to [discovery for\n Cloud SQL](/sensitive-data-protection/docs/data-profiles#cloud-sql).\n - [`organizations.locations.connections`](/sensitive-data-protection/docs/reference/rest/v2/organizations.locations.connections)\n - [`projects.locations.connections`](/sensitive-data-protection/docs/reference/rest/v2/projects.locations.connections)\n- Data profiles\n\n - [`organizations.locations.projectDataProfiles`](/sensitive-data-protection/docs/reference/rest/v2/organizations.locations.projectDataProfiles)\n - [`projects.locations.projectDataProfiles`](/sensitive-data-protection/docs/reference/rest/v2/projects.locations.projectDataProfiles)\n - [`organizations.locations.fileStoreDataProfiles`](/sensitive-data-protection/docs/reference/rest/v2/organizations.locations.fileStoreDataProfiles)\n - [`projects.locations.fileStoreDataProfiles`](/sensitive-data-protection/docs/reference/rest/v2/projects.locations.fileStoreDataProfiles)\n - [`organizations.locations.tableDataProfiles`](/sensitive-data-protection/docs/reference/rest/v2/organizations.locations.tableDataProfiles)\n - [`projects.locations.tableDataProfiles`](/sensitive-data-protection/docs/reference/rest/v2/projects.locations.tableDataProfiles)\n - [`organizations.locations.columnDataProfiles`](/sensitive-data-protection/docs/reference/rest/v2/organizations.locations.columnDataProfiles)\n - [`projects.locations.columnDataProfiles`](/sensitive-data-protection/docs/reference/rest/v2/projects.locations.columnDataProfiles)\n\nWhat's next\n-----------\n\n- Read the how-to guides to get started with inspecting text and images for sensitive data, as well as redacting sensitive data from text and images:\n - [Inspecting text for sensitive data](/sensitive-data-protection/docs/inspecting-text)\n - [Inspecting structured text for sensitive\n data](/sensitive-data-protection/docs/inspecting-structured-text)\n - [Inspecting images for sensitive data](/sensitive-data-protection/docs/inspecting-images)\n - [Redacting sensitive data from\n images](/sensitive-data-protection/docs/redacting-sensitive-data-images)\n - [De-identifying sensitive data](/sensitive-data-protection/docs/deidentify-sensitive-data)\n- For more information about inspecting storage and how to use actions, see [Inspecting storage and databases for sensitive\n data](/sensitive-data-protection/docs/inspecting-storage).\n- For more information about sensitive data discovery, see [Data\n profiles](/sensitive-data-protection/docs/data-profiles)\n- Review [pricing](/sensitive-data-protection/pricing)."]]
