Profile Cloud Storage data in a single project

This page describes how to configure Cloud Storage data discovery at the project level. If you want to profile an organization or folder, see Profile Cloud Storage data in an organization or folder.

For more information about the discovery service, see Data profiles.

Before you begin

1. Make sure the Cloud Data Loss Prevention API is enabled on your project:

   1. Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

   2. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

      Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

      Go to project selector

   3. Make sure that billing is enabled for your Google Cloud project.

   4. Enable the required API.

      Enable the API

   5. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

      Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

      Go to project selector

   6. Make sure that billing is enabled for your Google Cloud project.

   7. Enable the required API.

      Enable the API

2. Confirm that you have the IAM permissions that are required to configure data profiles at the project level.

3. You must have an inspection template in each region where you have data to be profiled. If you want to use a single template for multiple regions, you can use a template that is stored in the global region. If organizational policies prevent you from creating a global inspection template, you must set a dedicated inspection template for each region. For more information, see Data residency considerations.

   This task lets you create an inspection template in the global region only. If you need dedicated inspection templates for one or more regions, you must create those templates before performing this task.

4. You can configure Sensitive Data Protection to send notifications to Pub/Sub when certain events occur, such as when Sensitive Data Protection profiles a new bucket. If you want to use this feature, you must first create a Pub/Sub topic.

Create a scan configuration

1. Go to the Create scan configuration page.

   Go to Create scan configuration

2. Go to your project. On the toolbar, click the project selector and select your project.

The following sections provide more information about the steps in the Create scan configuration page. At the end of each section, click Continue.

Select a discovery type

Select Cloud Storage.

Select scope

Do one of the following:

• If you want to scan a single bucket in test mode, select Scan one bucket (test mode).

  The number of free bucket scans available is displayed. For each bucket, you can have only one test mode scan configuration. For more information, see Profile a single data asset in test mode.

  Fill in the details of the bucket that you want to profile.

• If you want to perform standard project-level profiling, select Scan entire project.

Manage schedules

If the default profiling frequency suits your needs, you can skip this section of the Create scan configuration page.

This section is useful if you want to make fine-grained adjustments to the profiling frequency of all your data or certain subsets of your data. It's also useful if you don't want certain buckets to ever be profiled, or you want them to be profiled once and then never again.

In this section, you create filters to specify certain subsets of your data that are of interest. You specify whether Sensitive Data Protection should profile those subsets and how often. You also specify the types of changes that should cause a buckets to be reprofiled. Finally, you specify any conditions that a bucket must meet before Sensitive Data Protection can start profiling it.

To make fine-grained adjustments to profiling frequency, follow these steps:

1. Click Add schedule.

2. In the Filters section, you define one or more filters that specify which buckets are in the schedule's scope.

   Specify at least one of the following:

   • A project ID or a regular expression that specifies one or more projects
   • A bucket name or a regular expression that specifies one or more buckets

   Regular expressions must follow the RE2 syntax.

   For example, if you want all buckets in a project to be included in the filter, enter the project ID in the Project ID field.

   If you want to add more filters, click Add filter and repeat this step.

3. Click Frequency.

4. In the Frequency section, specify whether the discovery service should profile the buckets that you selected, and if so, how often:

   • If you never want the buckets to be profiled, turn off Do profile this data.

   • If you want the buckets to be profiled at least once, leave Do profile this data on.

     In the succeeding fields in this section, you specify whether the system should reprofile your data and what events should trigger a reprofile operation. For more information, see Frequency of data profile generation.

     1. For On a schedule, specify how often you want the the buckets to be reprofiled. The buckets are reprofiled regardless of whether they underwent any changes.
     2. For When inspect template changes, specify whether you want your data to be reprofiled when the associated inspection template is updated, and if so, how often.
        Note: You specify the inspection templates to use in the Select inspection template step on this page.

        An inspection template change is detected when either of the following occurs:

        • The name of an inspection template changes in your scan configuration.
        • The updateTime of an inspection template changes.

     For example, if you set an inspection template for the us-west1 region and you update that inspection template, then only data in the us-west1 region will be reprofiled. However, if you delete that inspection template instead, then the data in us-west1 isn't reprofiled, because there's no inspection template to use to reprofile it.

5. Optional: Click Conditions.

   In the Conditions section, you specify any conditions that the buckets—defined in your filters—must meet before Sensitive Data Protection profiles them.

   If needed, set the following:

   • Minimum conditions: If you want to delay profiling of a bucket until it reaches a certain age, turn on this option. Then, enter the minimum duration.

   • Bucket attribute conditions: By default, Sensitive Data Protection doesn't scan buckets that have Autoclass enabled. If you want to scan those buckets, click Scan buckets with Autoclass enabled.

     Caution: When scanned, Autoclass-enabled objects that are in colder storage classes move to the Standard storage class.

   • Object attribute conditions: By default, Sensitive Data Protection scans only objects that are in the Standard storage class. If you want to scan objects in other storage classes, select those storage classes individually or click Scan all objects regardless of the attribute.

   • Time condition: If you don't want old buckets to ever be profiled, turn on this option. Then, use the date picker to select a date and time. Any bucket created on or before your selected timestamp is excluded from profiling.

   Example conditions

   Suppose that you have the following configuration:

   • Minimum conditions

     • Minimum duration: 24 hours

   • Bucket attribute conditions

     • None selected

   • Object attribute conditions

     • Scan objects with the Standard storage class
     • Scan objects with the Nearline storage class

   • Time condition

     • Timestamp: 05/4/22, 11:59 PM

   In this case, Sensitive Data Protection excludes any bucket that was created on or before May 4, 2022, 11:59 PM. Among the buckets that were created after that date and time, Sensitive Data Protection profiles only the buckets that are at least 24 hours old and have Autoclass disabled. Within those buckets, Sensitive Data Protection profiles only the objects that are in the Standard and Nearline storage classes.

6. Click Done.

7. If you want to add more schedules, click Add schedule and repeat the previous steps.

8. To reorder the schedules according to priority, use the up and down arrows. For example, if the filters in two different schedules match the same bucket, the schedule higher on the priority list takes precedence.

   The last schedule in the list is always the one labeled Default schedule. This default schedule covers the buckets in your project that don't match any of the schedules that you created. This default schedule follows the system default profiling frequency.

9. If you want to adjust the default schedule, click Edit schedule, and adjust the settings as needed.

Select inspection template

Depending on how you want to provide an inspection configuration, choose one of the following options. Regardless of which option you choose, Sensitive Data Protection scans your data in the region where that data is stored. That is, your data doesn't leave its region of origin.

Option 1: Create an inspection template

Choose this option if you want to create a new inspection template in the global region.

1. Click Create new inspection template.

2. Optional: To modify the default selection of infoTypes, click Manage infoTypes.

   For more information about how to manage built-in and custom infoTypes in this section, see Manage infoTypes through the Google Cloud console.

   You must have at least one infoType selected to continue.

3. Optional: Configure the inspection template further by adding rulesets and setting a confidence threshold. For more information, see Configure detection.

   When Sensitive Data Protection creates the scan configuration, it stores this new inspection template in the global region.

Option 2: Use an existing inspection template

Choose this option if you have existing inspection templates that you want to use.

1. Click Select existing inspection template.

2. Enter the full resource name of the inspection template that you want to use. The Region field is automatically populated with the name of the region where your inspection template is stored.

   The inspection template you enter must be in the same region as the data to be profiled. To respect data residency, Sensitive Data Protection doesn't use an inspection template outside the region where that template is stored.

   To find the full resource name of an inspection template, follow these steps:

   1. Go to your inspection templates list. This page opens on a separate tab.

      Go to inspection templates

   2. Switch to the project that contains the inspection template that you want to use.

   3. On the Templates tab, click the template ID of the template that you want to use.

   4. On the page that opens, copy the full resource name of the template. The full resource name follows this format:

      projects/PROJECT_ID/locations/REGION/inspectTemplates/TEMPLATE_ID

   5. On the Create scan configuration page, in the Template name field, paste the full resource name of the template.

3. If you have data in another region, and you have an inspection template that you want to use for that region, follow these steps:

   1. Click Add inspection template.
   2. Enter the inspection template's full resource name.

   Repeat these steps for each region where you have a dedicated inspection template.

4. Optional: Add an inspection template that's stored in the global region. Sensitive Data Protection automatically uses that template for data in regions where you don't have a dedicated inspection template.

   Caution: If you don't include an inspection template that's stored in the global region, Sensitive Data Protection can't profile data in regions that don't have a dedicated inspection template. For more information, see Data residency considerations.

Add actions

In the following sections, you specify actions that you want Sensitive Data Protection to take after it generates the data profiles.

For information about how other Google Cloud services may charge you for configuring actions, see Pricing for exporting data profiles.

Publish to Security Command Center

This action lets you send the calculated data risk and sensitivity levels of data profiles to Security Command Center.

Security Command Center is Google Cloud's centralized vulnerability and threat reporting service. You can use findings from data profiles when you triage and develop response plans for your vulnerability and threat findings in Security Command Center.

Note: If you enable this feature, you can also configure Security Command Center to automatically prioritize resources for the attack path simulation feature according to the calculated sensitivity of the data that the resources contain. For more information, see Set resource priority values automatically by data sensitivity.

Before you can use this action, Security Command Center must be activated at the organization level. Turning on Security Command Center at the organization level enables the flow of findings from integrated services like Sensitive Data Protection. Sensitive Data Protection works with Security Command Center in all service tiers.

If Security Command Center isn't activated at the organization level, Sensitive Data Protection findings won't appear in Security Command Center. For more information, see Check the activation level of Security Command Center.

To send the results of your data profiles to Security Command Center, make sure the Publish to Security Command Center option is turned on.

For more information, see Publish data profiles to Security Command Center.

Save data profile copies to BigQuery

Turning on Save data profile copies to BigQuery lets you keep a saved copy or history of all of your generated profiles. Doing so can be useful for creating audit reports and visualizing data profiles. You can also load this information into other systems.

Also, this option lets you see all of your data profiles in a single view, regardless of which region your data resides in. If you turn off this option, you can still view the data profiles in the Google Cloud console. However, in the Google Cloud console, you select one region at a time, and see only the data profiles for that region.

Note: When Sensitive Data Protection fails to profile a bucket, it periodically retries. To minimize noise in the exported data, Sensitive Data Protection exports only the successfully generated profiles to BigQuery.

To export copies of the data profiles to a BigQuery table, follow these steps:

1. Turn on Save data profile copies to BigQuery.

2. Enter the details of the BigQuery table where you want to save the data profiles:

   • For Project ID, enter the ID of an existing project where you want data profiles to be exported to.

   • For Dataset ID, enter the name of an existing dataset in the project where you want data profiles to be exported to.

   • For Table ID, enter a name for the BigQuery table where data profiles will be exported to. If you haven't created this table, Sensitive Data Protection automatically creates it for you using the name you provide.

Sensitive Data Protection starts exporting profiles from the time you turn on this option. Profiles that were generated before you turned on exporting aren't saved to BigQuery.

Note: The service agent associated with your project must have write access on the output table.

Publish to Pub/Sub

Turning on Publish to Pub/Sub lets you take programmatic actions based on profiling results. You can use Pub/Sub notifications to develop a workflow for catching and remediating findings with significant data risk or sensitivity.

To send notifications to a Pub/Sub topic, follow these steps:

1. Turn on Publish to Pub/Sub.

   A list of options appears. Each option describes an event that causes Sensitive Data Protection to send a notification to Pub/Sub.

2. Select the events that should trigger a Pub/Sub notification.

If you select Send a Pub/Sub notification each time a profile is updated, Sensitive Data Protection sends a notification when there's a change in the following file store metrics:

• Data risk
• Sensitivity
• File extensions scanned
• File extensions seen
• InfoTypes
• Public

3. For each event you select, follow these steps:

   1. Enter the name of the topic. The name must be in the following format:

      projects/PROJECT_ID/topics/TOPIC_ID
      

      Replace the following:

      • PROJECT_ID: the ID of the project associated with the Pub/Sub topic.
      • TOPIC_ID: the ID of the Pub/Sub topic.

   2. Specify whether to include the full bucket profile in the notification, or just the full resource name of the bucket that was profiled.

   3. Set the minimum data risk and sensitivity levels that must be met for Sensitive Data Protection to send a notification.

   4. Specify whether only one or both of the data risk and sensitivity conditions must be met. For example, if you choose AND, then both the data risk and the sensitivity conditions must be met before Sensitive Data Protection sends a notification.

Note: The service agent associated with your project must have publishing access on the Pub/Sub topic. An example of a role that has publishing access is the Pub/Sub Publisher role (roles/pubsub.publisher). If there are configuration or permission issues with the Pub/Sub topic, Sensitive Data Protection retries sending the Pub/Sub notification for up to two weeks. After two weeks, the notification is discarded.

Set location to store configuration

Click the Resource location list, and select the region where you want to store this scan configuration. All scan configurations that you later create will also be stored in this location.

Where you choose to store your scan configuration doesn't affect the data to be scanned. Also, it doesn't affect where the data profiles are stored. Your data is scanned in the same region where that data is stored. For more information, see Data residency considerations.

Note: If you already have an existing scan configuration, you can't change the value set in this field. All scan configurations are stored in the same location. If you want to change the location of all your scan configurations, you must delete them, recreate them, and store them in the new location.

Review and create

1. If you want to make sure that profiling doesn't start automatically after you create the scan configuration, select Create scan in paused mode.

   This option is useful in the following cases:

   • You opted to save data profiles to BigQuery, and you want to make sure the service agent has write access to your output table.
   • You configured Pub/Sub notifications and you want to grant publishing access to the service agent.

2. Review your settings and click Create.

   Sensitive Data Protection creates the scan configuration and adds it to the discovery scan configurations list.

To view or manage your scan configurations, see Manage scan configurations.

Note: We regularly improve our detection algorithm. If we find that your organization or project would benefit from a new improvement that we implement, we might automatically regenerate your data profiles and redo the actions in your scan configuration. You won't incur Sensitive Data Protection charges for this operation. However, because we will redo the actions, you might incur charges for your use of other Google Cloud services. For example, if you configured Sensitive Data Protection to save the data profiles to BigQuery, you might incur BigQuery charges.

What's next

Learn how to estimate the cost of profiling data in a single project.

Learn how to manage data profiles.

Learn how to manage scan configurations.

Learn how to receive and parse Pub/Sub messages published by the data profiler.

Learn how to troubleshoot issues with data profiles.