请考虑此示例:项目 A 在 us-west1 和 us-west2 区域中具有表。如果您在 us-west1 区域查看项目数据分析文件,则会看到项目 A 的数据分析文件。它仅包含从 us-west1 区域中项目 A 的表中收集的指标。如果您切换到 us-west2 区域,则有项目 A 的另一个数据剖析文件可用。它仅显示与 us-west2 区域中项目 A 的表相关的数据。
[[["易于理解","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,["# Manage data profiles\n\nThis section describes how to perform operations on the data profiles that are\ngenerated by the Sensitive Data Protection discovery service.\n\nFor more information about the discovery service, see\n[Data profiles](/sensitive-data-protection/docs/data-profiles).\n\nBefore you begin\n----------------\n\nConfirm that you have the IAM permissions that\nare required to work with\nscan configurations and data profiles at the [organization](/sensitive-data-protection/docs/data-profiles#permissions-to-view-configs-profiles-org) or [project](/sensitive-data-protection/docs/data-profiles#permissions-to-view-configs-profiles-project) level.\n\nView the data profiles\n----------------------\n\nTo respect [data residency](/sensitive-data-protection/docs/data-profiles#data-residency),\nSensitive Data Protection doesn't combine profiles that reside in different\nregions. Consequently, in the Google Cloud console, you can only see data\nprofiles for the region that you select.\n\nIf you want to create or view reports that combine data profiles across regions\ninto a single view, [export your data\nprofiles](/sensitive-data-protection/docs/profile-org-folder#save-to-bq) to\nBigQuery. This feature lets you query the data profiles in\nBigQuery and generate a [premade\nreport](/sensitive-data-protection/docs/analyze-data-profiles) in\nLooker.\n\nTo view the data profiles in the Google Cloud console, follow these steps:\n\n1. Go to the Sensitive Data Protection discovery profiles page.\n\n [Go to Discovery profiles](https://console.cloud.google.com/security/sensitive-data-protection/dataprofiles/profiles;source=7)\n2. Make sure you're viewing the correct organization or project:\n\n - If you generated the data profiles through an organization-level or folder-level scan, then view the organization.\n - If you generated the data profiles using a project-level scan, then view the proper project.\n\n To switch to a different view, on the toolbar, click the\n arrow_drop_down project selector.\n Then, select the organization or project that you want to view.\n\n Data profiles generated through a project-level scan only appear in the\n project view and are not combined with the results of organization-level or\n folder-level scans. Conversely, data profiles generated through an\n organization-level or folder-level scan only appear in the organization view.\n3. In the **Location** list, select the region that contains the data profiles\n that you want to view. Each data profile is stored in the same region as the\n data it pertains to.\n\nThe page loads the data profiles. On this page, you can view\ndata profiles at various levels.\n\n### Projects view\n\nOn the **Projects** tab, each project that has data that was\nscanned in your selected region represents one data profile.\n\nThe following image shows a list of project data profiles. Click the image to\nenlarge it.\n\n\u003cbr /\u003e\n\n[](/static/sensitive-data-protection/docs/images/project-data-profiles_2x.png)\n\n\u003cbr /\u003e\n\nEach project data profile is an aggregation of the metrics gathered from\ndata assets that meet both of the following criteria:\n\n- Data assets that belong to that project.\n- Data assets that reside in the selected region in the Google Cloud console.\n\nThus, it's possible to have two or more data profiles for the\nsame project---one for each region. Those project data profiles\ncan have different risk and sensitivity levels.\n\nConsider this example: Project A has tables in the `us-west1` and `us-west2`\nregions. If you view your project data profiles in the `us-west1` region, there\nis a data profile for Project A. It includes only the metrics gathered from\nProject A's tables in the `us-west1` region. If you switch to the `us-west2`\nregion, another data profile for Project A is available. It shows only data that\nis related to Project A's tables in the `us-west2` region.\n\nFor more information about the metrics gathered in project data profiles, see\n[Project-level data profiles](/sensitive-data-protection/docs/metrics-reference#project-data-profile).\n\n### Tables view\n\nOn the **Tables** tab, each table that was scanned in your\nselected region represents one data profile.\n\nThe following image shows a list of table data profiles. Click the image to\nenlarge it.\n\n\u003cbr /\u003e\n\n[](/static/sensitive-data-protection/docs/images/table-data-profiles_2x.png)\n\n\u003cbr /\u003e\n\n- To view the details of a table data profile, click anywhere in its row.\n Alternatively, click more_vert **Actions**\n \\\u003e **View details** . The details view also shows the\n [column-level](#columns-view) data profiles for the table.\n\n- To go back to the **Tables** tab from the columns view, click arrow_back **Sensitive Data Discovery: Table profile details**.\n\nFor more information on the metrics gathered in table data profiles, see\n[Table-level data profiles](/sensitive-data-protection/docs/metrics-reference#table-data-profile).\n\n### Columns view\n\nWhen you click a table data profile in the **Tables**\ntab, the columns view appears. In this view, each column of a table that\nwas scanned in your selected region represents one data profile.\n\nThe following image shows a list of column data profiles. Click the image to\nenlarge it.\n\n\u003cbr /\u003e\n\n[](/static/sensitive-data-protection/docs/images/column-data-profiles_2x.png)\n\n\u003cbr /\u003e\n\nTo view the profile details of a particular column, click\nmore_vert **Actions**\nand then click **View details**.\n\n- To go back to the **Tables** tab from the columns view, click arrow_back **Sensitive Data Discovery: Table profile details**.\n\n\u003cbr /\u003e\n\n| **Note:** If you delete a column from a table and that table is reprofiled, no [column data profile](/sensitive-data-protection/docs/metrics-reference#column-data-profile) is generated for the deleted column. If you want to keep a history of past data profiles---for example, for auditing purposes---[configure the profiler to export\n| data profiles to BigQuery](/sensitive-data-protection/docs/profile-org-folder#save-to-bq).\n\n\u003cbr /\u003e\n\nFor more information on the metrics gathered in column data profiles, see\n[Column-level data profiles](/sensitive-data-protection/docs/metrics-reference#column-data-profile).\n\n### File stores view\n\nOn the **File stores** tab, each file store that was scanned in\nyour selected region represents one data profile. Sensitive Data Protection uses the term *file store* to\nrefer to a file storage bucket or container.\n\n- To view the details of a file store data profile, click anywhere in its row.\n Alternatively, click more_vert **Actions**\n \\\u003e **View details**.\n\n- To go back to the **File stores** tab, click arrow_back **Sensitive Data Discovery: File\n store profile details**.\n\nFor more information on the metrics gathered in file store data profiles, see\n[File store data profiles](/sensitive-data-protection/docs/metrics-reference#file-store-data-profile).\n\nForce a reprofile operation\n---------------------------\n\nTo force a reprofile operation on a data asset, you delete the asset's table\ndata profile or file store data profile. If the data asset is in the scope of an\nactive scan configuration, the data asset is reprofiled automatically.\nOtherwise, you must create a scan configuration that includes the data asset.\n| **Note:** Sensitive Data Protection uses the term *file store* to refer to a file storage bucket or container.\n\nMultiple data profiles are regenerated when you reprofile your data:\n\n- Reprofiling a table causes the table data profile, column data profiles, and project data profile to be regenerated.\n- Reprofiling a file store causes the file store data profile and project data profile to be regenerated.\n\nYou might perform this task in the following situations:\n\n- You want to reprofile your data without first introducing a change in it.\n- You want to reprofile your data before the next scheduled discovery scan.\n\nTo reprofile a data asset, follow these steps:\n\n1. [View the details](#view_the_data_profiles) of the table data profile or file store data profile that you want to regenerate.\n2. Click **Delete**.\n3. Review the confirmation message that appears, and click **Delete**. The data profile is deleted.\n4. If no active scan configuration includes the table or file store, [create\n one](/sensitive-data-protection/docs/manage-scan-configurations#create).\n\nPerform a deep inspection on a BigQuery table or Cloud Storage bucket\n---------------------------------------------------------------------\n\nIf you profiled a BigQuery table or Cloud Storage bucket and\nyou want to learn more about the data asset's contents, you can perform a deep\ninspection.\n\nTo inspect a data asset that was profiled, follow these steps:\n\n1. [View the details](#view_the_data_profiles) of the data profile.\n2. Click add_box **Create inspection job**.\n3. Fill in the details of the inspection job that you want to perform. For more information on filling in this form, see [Inspect Google Cloud storage and\n databases for sensitive\n data](/sensitive-data-protection/docs/inspecting-storage).\n\nWhat's next\n-----------\n\n- Learn how to [manage scan configurations](/sensitive-data-protection/docs/manage-scan-configurations).\n- Learn how to [analyze the data profiles](/sensitive-data-protection/docs/analyze-data-profiles)."]]