@@ -6859,21 +6859,12 @@ class PublishFindingsToCloudDataCatalog(proto.Message):
6859
6859
"""
6860
6860
6861
6861
class Deidentify (proto .Message ):
6862
- r"""Create a de-identified copy of the requested table or files.
6862
+ r"""Create a de-identified copy of a storage bucket. Only
6863
+ compatible with Cloud Storage buckets.
6863
6864
6864
6865
A TransformationDetail will be created for each transformation.
6865
6866
6866
- If any rows in BigQuery are skipped during de-identification
6867
- (transformation errors or row size exceeds BigQuery insert API
6868
- limits) they are placed in the failure output table. If the original
6869
- row exceeds the BigQuery insert API limit it will be truncated when
6870
- written to the failure output table. The failure output table can be
6871
- set in the
6872
- action.deidentify.output.big_query_output.deidentified_failure_output_table
6873
- field, if no table is set, a table will be automatically created in
6874
- the same project and dataset as the original table.
6875
-
6876
- Compatible with: Inspect
6867
+ Compatible with: Inspection of Cloud Storage
6877
6868
6878
6869
6879
6870
.. _oneof: https://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields
@@ -6884,14 +6875,76 @@ class Deidentify(proto.Message):
6884
6875
configs for structured, unstructured, and image
6885
6876
files.
6886
6877
transformation_details_storage_config (google.cloud.dlp_v2.types.TransformationDetailsStorageConfig):
6887
- Config for storing transformation details. This is separate
6888
- from the de-identified content, and contains metadata about
6889
- the successful transformations and/or failures that occurred
6890
- while de-identifying. This needs to be set in order for
6891
- users to access information about the status of each
6892
- transformation (see
6878
+ Config for storing transformation details.
6879
+
6880
+ This field specifies the configuration for storing detailed
6881
+ metadata about each transformation performed during a
6882
+ de-identification process. The metadata is stored separately
6883
+ from the de-identified content itself and provides a
6884
+ granular record of both successful transformations and any
6885
+ failures that occurred.
6886
+
6887
+ Enabling this configuration is essential for users who need
6888
+ to access comprehensive information about the status,
6889
+ outcome, and specifics of each transformation. The details
6890
+ are captured in the
6893
6891
[TransformationDetails][google.privacy.dlp.v2.TransformationDetails]
6894
- message for more information about what is noted).
6892
+ message for each operation.
6893
+
6894
+ Key use cases:
6895
+
6896
+ - **Auditing and compliance**
6897
+
6898
+ - Provides a verifiable audit trail of de-identification
6899
+ activities, which is crucial for meeting regulatory
6900
+ requirements and internal data governance policies.
6901
+ - Logs what data was transformed, what transformations
6902
+ were applied, when they occurred, and their success
6903
+ status. This helps demonstrate accountability and due
6904
+ diligence in protecting sensitive data.
6905
+
6906
+ - **Troubleshooting and debugging**
6907
+
6908
+ - Offers detailed error messages and context if a
6909
+ transformation fails. This information is useful for
6910
+ diagnosing and resolving issues in the
6911
+ de-identification pipeline.
6912
+ - Helps pinpoint the exact location and nature of
6913
+ failures, speeding up the debugging process.
6914
+
6915
+ - **Process verification and quality assurance**
6916
+
6917
+ - Allows users to confirm that de-identification rules
6918
+ and transformations were applied correctly and
6919
+ consistently across the dataset as intended.
6920
+ - Helps in verifying the effectiveness of the chosen
6921
+ de-identification strategies.
6922
+
6923
+ - **Data lineage and impact analysis**
6924
+
6925
+ - Creates a record of how data elements were modified,
6926
+ contributing to data lineage. This is useful for
6927
+ understanding the provenance of de-identified data.
6928
+ - Aids in assessing the potential impact of
6929
+ de-identification choices on downstream analytical
6930
+ processes or data usability.
6931
+
6932
+ - **Reporting and operational insights**
6933
+
6934
+ - You can analyze the metadata stored in a queryable
6935
+ BigQuery table to generate reports on transformation
6936
+ success rates, common error types, processing volumes
6937
+ (e.g., transformedBytes), and the types of
6938
+ transformations applied.
6939
+ - These insights can inform optimization of
6940
+ de-identification configurations and resource
6941
+ planning.
6942
+
6943
+ To take advantage of these benefits, set this configuration.
6944
+ The stored details include a description of the
6945
+ transformation, success or error codes, error messages, the
6946
+ number of bytes transformed, the location of the transformed
6947
+ content, and identifiers for the job and source data.
6895
6948
cloud_storage_output (str):
6896
6949
Required. User settable Cloud Storage bucket
6897
6950
and folders to store de-identified files. This
@@ -7909,6 +7962,12 @@ class DataProfileAction(proto.Message):
7909
7962
Tags the profiled resources with the
7910
7963
specified tag values.
7911
7964
7965
+ This field is a member of `oneof`_ ``action``.
7966
+ publish_to_dataplex_catalog (google.cloud.dlp_v2.types.DataProfileAction.PublishToDataplexCatalog):
7967
+ Publishes a portion of each profile to
7968
+ Dataplex Catalog with the aspect type Sensitive
7969
+ Data Protection Profile.
7970
+
7912
7971
This field is a member of `oneof`_ ``action``.
7913
7972
"""
7914
7973
@@ -8070,6 +8129,29 @@ class PublishToSecurityCommandCenter(proto.Message):
8070
8129
8071
8130
"""
8072
8131
8132
+ class PublishToDataplexCatalog (proto .Message ):
8133
+ r"""Create Dataplex Catalog aspects for profiled resources with
8134
+ the aspect type Sensitive Data Protection Profile. To learn more
8135
+ about aspects, see
8136
+ https://cloud.google.com/sensitive-data-protection/docs/add-aspects.
8137
+
8138
+ Attributes:
8139
+ lower_data_risk_to_low (bool):
8140
+ Whether creating a Dataplex Catalog aspect
8141
+ for a profiled resource should lower the risk of
8142
+ the profile for that resource. This also lowers
8143
+ the data risk of resources at the lower levels
8144
+ of the resource hierarchy. For example, reducing
8145
+ the data risk of a table data profile also
8146
+ reduces the data risk of the constituent column
8147
+ data profiles.
8148
+ """
8149
+
8150
+ lower_data_risk_to_low : bool = proto .Field (
8151
+ proto .BOOL ,
8152
+ number = 1 ,
8153
+ )
8154
+
8073
8155
class TagResources (proto .Message ):
8074
8156
r"""If set, attaches the [tags]
8075
8157
(https://cloud.google.com/resource-manager/docs/tags/tags-overview)
@@ -8203,6 +8285,12 @@ class TagValue(proto.Message):
8203
8285
oneof = "action" ,
8204
8286
message = TagResources ,
8205
8287
)
8288
+ publish_to_dataplex_catalog : PublishToDataplexCatalog = proto .Field (
8289
+ proto .MESSAGE ,
8290
+ number = 9 ,
8291
+ oneof = "action" ,
8292
+ message = PublishToDataplexCatalog ,
8293
+ )
8206
8294
8207
8295
8208
8296
class DataProfileFinding (proto .Message ):
@@ -8234,6 +8322,12 @@ class DataProfileFinding(proto.Message):
8234
8322
Where the content was found.
8235
8323
resource_visibility (google.cloud.dlp_v2.types.ResourceVisibility):
8236
8324
How broadly a resource has been shared.
8325
+ full_resource_name (str):
8326
+ The `full resource
8327
+ name <https://cloud.google.com/apis/design/resource_names#full_resource_name>`__
8328
+ of the resource profiled for this finding.
8329
+ data_source_type (google.cloud.dlp_v2.types.DataSourceType):
8330
+ The type of the resource that was profiled.
8237
8331
"""
8238
8332
8239
8333
quote : str = proto .Field (
@@ -8273,6 +8367,15 @@ class DataProfileFinding(proto.Message):
8273
8367
number = 8 ,
8274
8368
enum = "ResourceVisibility" ,
8275
8369
)
8370
+ full_resource_name : str = proto .Field (
8371
+ proto .STRING ,
8372
+ number = 9 ,
8373
+ )
8374
+ data_source_type : "DataSourceType" = proto .Field (
8375
+ proto .MESSAGE ,
8376
+ number = 10 ,
8377
+ message = "DataSourceType" ,
8378
+ )
8276
8379
8277
8380
8278
8381
class DataProfileFindingLocation (proto .Message ):
@@ -13050,7 +13153,8 @@ class FileStoreDataProfile(proto.Message):
13050
13153
The BigQuery table to which the sample
13051
13154
findings are written.
13052
13155
file_store_is_empty (bool):
13053
- The file store does not have any files.
13156
+ The file store does not have any files. If
13157
+ the profiling operation failed, this is false.
13054
13158
tags (MutableSequence[google.cloud.dlp_v2.types.Tag]):
13055
13159
The tags attached to the resource, including
13056
13160
any tags attached during profiling.
0 commit comments