feat(dlp): update the api

#### dlp:v2 The following keys were added: - schemas.GooglePrivacyDlpV2DataProfileAction.properties.publishToChronicle.$ref (Total Keys: 1) - schemas.GooglePrivacyDlpV2DataProfileAction.properties.publishToScc.$ref (Total Keys: 1) - schemas.GooglePrivacyDlpV2PublishToChronicle (Total Keys: 2) - schemas.GooglePrivacyDlpV2PublishToSecurityCommandCenter (Total Keys: 2)
googleapis · Sep 10, 2024 · 8d4b2d2 · 8d4b2d2
1 parent 88a5b5f
commit 8d4b2d2
Show file tree

Hide file tree

Showing 7 changed files with 133 additions and 1 deletion.
diff --git a/docs/dyn/dlp_v2.organizations.locations.discoveryConfigs.html b/docs/dyn/dlp_v2.organizations.locations.discoveryConfigs.html
@@ -138,6 +138,10 @@ <h3>Method Details</h3>
           },
           &quot;topic&quot;: &quot;A String&quot;, # Cloud Pub/Sub topic to send notifications to. Format is projects/{project}/topics/{topic}.
         },
+        &quot;publishToChronicle&quot;: { # Message expressing intention to publish to Google Security Operations. # Publishes generated data profiles to Google Security Operations. For more information, see [Use Sensitive Data Protection data in context-aware analytics](https://cloud.google.com/chronicle/docs/detection/usecase-dlp-high-risk-user-download).
+        },
+        &quot;publishToScc&quot;: { # If set, a summary finding will be created/updated in SCC for each profile. # Publishes findings to SCC for each data profile.
+        },
         &quot;tagResources&quot;: { # If set, attaches the [tags] (https://cloud.google.com/resource-manager/docs/tags/tags-overview) provided to profiled resources. Tags support [access control](https://cloud.google.com/iam/docs/tags-access-control). You can conditionally grant or deny access to a resource based on whether the resource has a specific tag. # Tags the profiled resources with the specified tag values.
           &quot;lowerDataRiskToLow&quot;: True or False, # Whether applying a tag to a resource should lower the risk of the profile for that resource. For example, in conjunction with an [IAM deny policy](https://cloud.google.com/iam/docs/deny-overview), you can deny all principals a permission if a tag value is present, mitigating the risk of the resource. This also lowers the data risk of resources at the lower levels of the resource hierarchy. For example, reducing the data risk of a table data profile also reduces the data risk of the constituent column data profiles.
           &quot;profileGenerationsToTag&quot;: [ # The profile generations for which the tag should be attached to resources. If you attach a tag to only new profiles, then if the sensitivity score of a profile subsequently changes, its tag doesn&#x27;t change. By default, this field includes only new profiles. To include both new and updated profiles for tagging, this field should explicitly include both `PROFILE_GENERATION_NEW` and `PROFILE_GENERATION_UPDATE`.
@@ -374,6 +378,10 @@ <h3>Method Details</h3>
         },
         &quot;topic&quot;: &quot;A String&quot;, # Cloud Pub/Sub topic to send notifications to. Format is projects/{project}/topics/{topic}.
       },
+      &quot;publishToChronicle&quot;: { # Message expressing intention to publish to Google Security Operations. # Publishes generated data profiles to Google Security Operations. For more information, see [Use Sensitive Data Protection data in context-aware analytics](https://cloud.google.com/chronicle/docs/detection/usecase-dlp-high-risk-user-download).
+      },
+      &quot;publishToScc&quot;: { # If set, a summary finding will be created/updated in SCC for each profile. # Publishes findings to SCC for each data profile.
+      },
       &quot;tagResources&quot;: { # If set, attaches the [tags] (https://cloud.google.com/resource-manager/docs/tags/tags-overview) provided to profiled resources. Tags support [access control](https://cloud.google.com/iam/docs/tags-access-control). You can conditionally grant or deny access to a resource based on whether the resource has a specific tag. # Tags the profiled resources with the specified tag values.
         &quot;lowerDataRiskToLow&quot;: True or False, # Whether applying a tag to a resource should lower the risk of the profile for that resource. For example, in conjunction with an [IAM deny policy](https://cloud.google.com/iam/docs/deny-overview), you can deny all principals a permission if a tag value is present, mitigating the risk of the resource. This also lowers the data risk of resources at the lower levels of the resource hierarchy. For example, reducing the data risk of a table data profile also reduces the data risk of the constituent column data profiles.
         &quot;profileGenerationsToTag&quot;: [ # The profile generations for which the tag should be attached to resources. If you attach a tag to only new profiles, then if the sensitivity score of a profile subsequently changes, its tag doesn&#x27;t change. By default, this field includes only new profiles. To include both new and updated profiles for tagging, this field should explicitly include both `PROFILE_GENERATION_NEW` and `PROFILE_GENERATION_UPDATE`.
@@ -634,6 +642,10 @@ <h3>Method Details</h3>
         },
         &quot;topic&quot;: &quot;A String&quot;, # Cloud Pub/Sub topic to send notifications to. Format is projects/{project}/topics/{topic}.
       },
+      &quot;publishToChronicle&quot;: { # Message expressing intention to publish to Google Security Operations. # Publishes generated data profiles to Google Security Operations. For more information, see [Use Sensitive Data Protection data in context-aware analytics](https://cloud.google.com/chronicle/docs/detection/usecase-dlp-high-risk-user-download).
+      },
+      &quot;publishToScc&quot;: { # If set, a summary finding will be created/updated in SCC for each profile. # Publishes findings to SCC for each data profile.
+      },
       &quot;tagResources&quot;: { # If set, attaches the [tags] (https://cloud.google.com/resource-manager/docs/tags/tags-overview) provided to profiled resources. Tags support [access control](https://cloud.google.com/iam/docs/tags-access-control). You can conditionally grant or deny access to a resource based on whether the resource has a specific tag. # Tags the profiled resources with the specified tag values.
         &quot;lowerDataRiskToLow&quot;: True or False, # Whether applying a tag to a resource should lower the risk of the profile for that resource. For example, in conjunction with an [IAM deny policy](https://cloud.google.com/iam/docs/deny-overview), you can deny all principals a permission if a tag value is present, mitigating the risk of the resource. This also lowers the data risk of resources at the lower levels of the resource hierarchy. For example, reducing the data risk of a table data profile also reduces the data risk of the constituent column data profiles.
         &quot;profileGenerationsToTag&quot;: [ # The profile generations for which the tag should be attached to resources. If you attach a tag to only new profiles, then if the sensitivity score of a profile subsequently changes, its tag doesn&#x27;t change. By default, this field includes only new profiles. To include both new and updated profiles for tagging, this field should explicitly include both `PROFILE_GENERATION_NEW` and `PROFILE_GENERATION_UPDATE`.
@@ -881,6 +893,10 @@ <h3>Method Details</h3>
             },
             &quot;topic&quot;: &quot;A String&quot;, # Cloud Pub/Sub topic to send notifications to. Format is projects/{project}/topics/{topic}.
           },
+          &quot;publishToChronicle&quot;: { # Message expressing intention to publish to Google Security Operations. # Publishes generated data profiles to Google Security Operations. For more information, see [Use Sensitive Data Protection data in context-aware analytics](https://cloud.google.com/chronicle/docs/detection/usecase-dlp-high-risk-user-download).
+          },
+          &quot;publishToScc&quot;: { # If set, a summary finding will be created/updated in SCC for each profile. # Publishes findings to SCC for each data profile.
+          },
           &quot;tagResources&quot;: { # If set, attaches the [tags] (https://cloud.google.com/resource-manager/docs/tags/tags-overview) provided to profiled resources. Tags support [access control](https://cloud.google.com/iam/docs/tags-access-control). You can conditionally grant or deny access to a resource based on whether the resource has a specific tag. # Tags the profiled resources with the specified tag values.
             &quot;lowerDataRiskToLow&quot;: True or False, # Whether applying a tag to a resource should lower the risk of the profile for that resource. For example, in conjunction with an [IAM deny policy](https://cloud.google.com/iam/docs/deny-overview), you can deny all principals a permission if a tag value is present, mitigating the risk of the resource. This also lowers the data risk of resources at the lower levels of the resource hierarchy. For example, reducing the data risk of a table data profile also reduces the data risk of the constituent column data profiles.
             &quot;profileGenerationsToTag&quot;: [ # The profile generations for which the tag should be attached to resources. If you attach a tag to only new profiles, then if the sensitivity score of a profile subsequently changes, its tag doesn&#x27;t change. By default, this field includes only new profiles. To include both new and updated profiles for tagging, this field should explicitly include both `PROFILE_GENERATION_NEW` and `PROFILE_GENERATION_UPDATE`.
@@ -1136,6 +1152,10 @@ <h3>Method Details</h3>
           },
           &quot;topic&quot;: &quot;A String&quot;, # Cloud Pub/Sub topic to send notifications to. Format is projects/{project}/topics/{topic}.
         },
+        &quot;publishToChronicle&quot;: { # Message expressing intention to publish to Google Security Operations. # Publishes generated data profiles to Google Security Operations. For more information, see [Use Sensitive Data Protection data in context-aware analytics](https://cloud.google.com/chronicle/docs/detection/usecase-dlp-high-risk-user-download).
+        },
+        &quot;publishToScc&quot;: { # If set, a summary finding will be created/updated in SCC for each profile. # Publishes findings to SCC for each data profile.
+        },
         &quot;tagResources&quot;: { # If set, attaches the [tags] (https://cloud.google.com/resource-manager/docs/tags/tags-overview) provided to profiled resources. Tags support [access control](https://cloud.google.com/iam/docs/tags-access-control). You can conditionally grant or deny access to a resource based on whether the resource has a specific tag. # Tags the profiled resources with the specified tag values.
           &quot;lowerDataRiskToLow&quot;: True or False, # Whether applying a tag to a resource should lower the risk of the profile for that resource. For example, in conjunction with an [IAM deny policy](https://cloud.google.com/iam/docs/deny-overview), you can deny all principals a permission if a tag value is present, mitigating the risk of the resource. This also lowers the data risk of resources at the lower levels of the resource hierarchy. For example, reducing the data risk of a table data profile also reduces the data risk of the constituent column data profiles.
           &quot;profileGenerationsToTag&quot;: [ # The profile generations for which the tag should be attached to resources. If you attach a tag to only new profiles, then if the sensitivity score of a profile subsequently changes, its tag doesn&#x27;t change. By default, this field includes only new profiles. To include both new and updated profiles for tagging, this field should explicitly include both `PROFILE_GENERATION_NEW` and `PROFILE_GENERATION_UPDATE`.
@@ -1373,6 +1393,10 @@ <h3>Method Details</h3>
         },
         &quot;topic&quot;: &quot;A String&quot;, # Cloud Pub/Sub topic to send notifications to. Format is projects/{project}/topics/{topic}.
       },
+      &quot;publishToChronicle&quot;: { # Message expressing intention to publish to Google Security Operations. # Publishes generated data profiles to Google Security Operations. For more information, see [Use Sensitive Data Protection data in context-aware analytics](https://cloud.google.com/chronicle/docs/detection/usecase-dlp-high-risk-user-download).
+      },
+      &quot;publishToScc&quot;: { # If set, a summary finding will be created/updated in SCC for each profile. # Publishes findings to SCC for each data profile.
+      },
       &quot;tagResources&quot;: { # If set, attaches the [tags] (https://cloud.google.com/resource-manager/docs/tags/tags-overview) provided to profiled resources. Tags support [access control](https://cloud.google.com/iam/docs/tags-access-control). You can conditionally grant or deny access to a resource based on whether the resource has a specific tag. # Tags the profiled resources with the specified tag values.
         &quot;lowerDataRiskToLow&quot;: True or False, # Whether applying a tag to a resource should lower the risk of the profile for that resource. For example, in conjunction with an [IAM deny policy](https://cloud.google.com/iam/docs/deny-overview), you can deny all principals a permission if a tag value is present, mitigating the risk of the resource. This also lowers the data risk of resources at the lower levels of the resource hierarchy. For example, reducing the data risk of a table data profile also reduces the data risk of the constituent column data profiles.
         &quot;profileGenerationsToTag&quot;: [ # The profile generations for which the tag should be attached to resources. If you attach a tag to only new profiles, then if the sensitivity score of a profile subsequently changes, its tag doesn&#x27;t change. By default, this field includes only new profiles. To include both new and updated profiles for tagging, this field should explicitly include both `PROFILE_GENERATION_NEW` and `PROFILE_GENERATION_UPDATE`.