Cloud Data Loss Prevention (Cloud DLP) is now a part of Sensitive Data Protection. The API name remains the same: Cloud Data Loss Prevention API (DLP API). For information about the services that make up Sensitive Data Protection, see Sensitive Data Protection overview.
Stay organized with collections
Save and categorize content based on your preferences.
If you only want to profile a single data resource, you can do so by creating
a project-level scan configuration.
Supported resources
The following resource types are supported:
BigQuery table
Cloud SQL table
Cloud Storage bucket
Vertex AI dataset
Amazon S3 bucket
Azure Blob Storage container
Differences between profiling a single data resource and standard profiling
Single-resource profiling differs from standard profiling in the following ways:
Single-resource profiling is available only in project view.
A single-resource discovery configuration lets you profile only one data
resource. You can't add schedules to the configuration, but you can edit the
catch-all schedule. You can't add filters to the schedule.
You can create many single-resource discovery configurations for different
data resources in a project. For each data resource, you can have only one
single-resource discovery configuration.
Create a single-resource discovery configuration
To create a single-resource discovery configuration, see the instructions for
the data that you want to profile:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Profile a single data resource\n\nIf you only want to profile a single data resource, you can do so by creating a project-level scan configuration.\n\n\u003cbr /\u003e\n\nSupported resources\n-------------------\n\nThe following resource types are supported:\n\n- BigQuery table\n- Cloud SQL table\n- Cloud Storage bucket\n- Vertex AI dataset\n- Amazon S3 bucket\n- Azure Blob Storage container\n\nDifferences between profiling a single data resource and standard profiling\n---------------------------------------------------------------------------\n\nSingle-resource profiling differs from standard profiling in the following ways:\n\n- Single-resource profiling is available only in project view.\n- A single-resource discovery configuration lets you profile only one data resource. You can't add schedules to the configuration, but you can edit the catch-all schedule. You can't add filters to the schedule.\n- You can create many single-resource discovery configurations for different data resources in a project. For each data resource, you can have only one single-resource discovery configuration.\n\nCreate a single-resource discovery configuration\n------------------------------------------------\n\nTo create a single-resource discovery configuration, see the instructions for\nthe data that you want to profile:\n\n- [Profile BigQuery data in a single\n project](/sensitive-data-protection/docs/profile-project)\n- [Profile Cloud SQL data in a single\n project](/sensitive-data-protection/docs/profile-project-cloud-sql)\n- [Profile Cloud Storage data in a single\n project](/sensitive-data-protection/docs/profile-project-cloud-storage)\n- [Profile Vertex AI data in a single\n project](/sensitive-data-protection/docs/profile-project-vertex-ai)\n- [Discovery for Amazon S3\n data](/sensitive-data-protection/docs/profile-amazon-s3)\n\nWhen you're prompted to select the scope of the scan, select the single-resource\noption, and then enter the details of the resource.\n\nProfile regeneration\n--------------------\n\n\nSensitive Data Protection reprofiles data as described in [Frequency of data profile\ngeneration](/sensitive-data-protection/docs/data-profiles#scan-frequency). You can customize the profiling frequency in your scan configuration by [creating a schedule](/sensitive-data-protection/docs/profile-org-folder#manage-schedules).\nTo force the discovery service to reprofile your data, see [Force a reprofile\noperation](/sensitive-data-protection/docs/manage-data-profiles#force-reprofile)."]]