The system will create a new dataset and table for you if none are
are provided. The dataset will be named
sensitive_data_protection_discovery and table will be named
discovery_profiles. This table will be placed in the same project as
the container project running the scan. After the first profile is
generated and the dataset and table are created, the discovery scan
configuration will be updated with the dataset and table names.
Data is inserted using streaming
insert
and so data may be in the buffer for a period of time after the
profile has finished.
The Pub/Sub notification is sent before the streaming buffer is
guaranteed to be written, so data may not be instantly
visible to queries by the time your topic receives the Pub/Sub
notification.
The best practice is to use the same table for an entire organization
so that you can take advantage of the provided Looker
reports.
If you use VPC Service Controls to define security perimeters, then
you must use a separate table for each boundary.
The system will create a new dataset and table for you if none are
are provided. The dataset will be named
sensitive_data_protection_discovery and table will be named
discovery_profiles. This table will be placed in the same project as
the container project running the scan. After the first profile is
generated and the dataset and table are created, the discovery scan
configuration will be updated with the dataset and table names.
Data is inserted using streaming
insert
and so data may be in the buffer for a period of time after the
profile has finished.
The Pub/Sub notification is sent before the streaming buffer is
guaranteed to be written, so data may not be instantly
visible to queries by the time your topic receives the Pub/Sub
notification.
The best practice is to use the same table for an entire organization
so that you can take advantage of the provided Looker
reports.
If you use VPC Service Controls to define security perimeters, then
you must use a separate table for each boundary.
The system will create a new dataset and table for you if none are
are provided. The dataset will be named
sensitive_data_protection_discovery and table will be named
discovery_profiles. This table will be placed in the same project as
the container project running the scan. After the first profile is
generated and the dataset and table are created, the discovery scan
configuration will be updated with the dataset and table names.
Data is inserted using streaming
insert
and so data may be in the buffer for a period of time after the
profile has finished.
The Pub/Sub notification is sent before the streaming buffer is
guaranteed to be written, so data may not be instantly
visible to queries by the time your topic receives the Pub/Sub
notification.
The best practice is to use the same table for an entire organization
so that you can take advantage of the provided Looker
reports.
If you use VPC Service Controls to define security perimeters, then
you must use a separate table for each boundary.
[[["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-03-05 UTC."],[],[]]
