Sensitive data protection Scan Configuration

[dharmendramis]

Hi, I have created a scan configuration and it profiles the big query tables and updated the profile inspection into big query dataset.table. the frequency I set up as daily for schema changes, table changes. I have added new table with PII data, however the scan did not perform any actions on the new table and there is no option to manually run the scan configuration. How does this scan configuration on any table added or schema changes?

Thanks, DM

[caryna]

Hi @dharmendramis ,

Welcome to the Google Cloud Community!

It seems you’ve set up a scan configuration to analyze BigQuery tables for sensitive data, but the scan hasn’t detected or analyzed a new table containing PII data. You also looked for a way to manually trigger the scan, but couldn’t find an option.

Here are some possible solutions to address the issue:

1. Filter Section: Check and update the filter settings in your scan configuration to clearly define which tables or data should be included or excluded. Make sure to add the newly created table to the list of tables to be scanned.

2. Frequency Section: Review and adjust your schema and table change settings as follows:

• Types of Schema Changes: Specify which schema modifications should prompt a re-profile operation. Choose from options like new columns or removed columns.
• Table Change Frequency: Determine how often Sensitive Data Protection should check for changes in the selected tables since their last profiling.

3. Condition Section: Verify the time and minimum conditions you’ve established to ensure they align with your requirements. Below is the example condition.

• Sensitive Data Protection will exclude tables created on or before May 4, 2022, at 11:59 PM. For tables created after this timestamp, the protection will apply only if the tables meet the following criteria: they must have at least 10 rows or be at least 24 hours old.

4. Observe and be patient, as BigQuery may have resource limits that can delay the scan, especially if you’re processing a very large table.

For additional details, refer to the scan configuration documentation.

Currently, manual triggering of the scan configuration is not supported; it only runs according to your scheduled settings. If you need a manual option, you can submit a feature request. While we cannot predict when this feature might be added, we recommend checking the issue tracker for the latest updates.

If the issue persists, please contact Google Cloud Support. When reaching out, include detailed information and relevant screenshots of the errors you’ve encountered. This will assist them in diagnosing and resolving your issue more efficiently.

I hope the above information is helpful.