This document describes how you can use Data Security Posture Management (DSPM).
If you're on the Security Command Center Standard tier, limited DSPM features are available.
DSPM enablement
Because DSPM is being shut down, you can no longer enable DSPM for an organization that doesn't already use it. If DSPM is already enabled for your organization, it remains available until the shutdown date, and the information in this document continues to apply.
For more information about Security Command Center tiers, see Security Command Center service tiers.
To protect additional resources with DSPM, enable discovery for those resources (Premium and Enterprise tiers only).
When DSPM was enabled for your organization, the following services were also enabled (Premium and Enterprise tiers only):
- Compliance Manager to create, apply, and manage data security frameworks and cloud controls.
- Sensitive Data Protection to use data sensitivity signals for default data risk assessment.
- Event Threat Detection (part of Security Command Center) at the organization level to use the data access governance cloud control and the data flow governance cloud control.
- AI Protection to help secure the lifecycle of your AI workloads (Security Command Center Enterprise tier only).
The Data Security and Privacy Essentials framework was applied to the organization automatically (Premium and Enterprise tiers only).
(Premium and Enterprise tiers only) The DSPM service
agent (service-org-ORGANIZATION_ID@gcp-sa-dspm-hpsa.) was created when
DSPM was enabled.
For information about the DSPM Identity and Access Management roles, see Identity and Access Management for organization-level activations.
Downgrading from the Premium or Enterprise tiers to the Standard tier
When you downgrade from the Premium or Enterprise tier to the Standard tier, your DSPM capabilities are affected as follows:
- Frameworks removed: Deployed DSPM frameworks that depend on Premium or Enterprise features are removed.
- Feature access lost: You lose access to advanced data security controls and custom data frameworks.
- Reverts to basic: DSPM uses the basic data security checks included in the Security Essentials framework.
- Findings become inactive: All findings previously generated by Premium or Enterprise tier frameworks become inactive. The only findings that remain available are those from the Security Essentials framework.
If you upgrade back to the Premium or Enterprise tier after downgrading to the Standard tier, framework deployments removed during the downgrade cannot be automatically recovered. You must manually re-deploy these frameworks and rebuild associated configurations.
DSPM support for VPC Service Controls perimeters
When you enable DSPM in an organization that includes VPC Service Controls perimeters, consider the following:
Review the limitations for Security Command Center.
You can't use a perimeter to help protect DSPM resources because all resources are at the organization level. To manage DSPM permissions, use IAM.
Because DSPM is enabled at the organization level, it can't detect data risks and violations within a service perimeter. To permit access, complete the following:
Make sure that you have the required roles to configure VPC Service Controls at the organization level.
Configure the following ingress rule:
- ingressFrom: identities: - serviceAccount: DSPM_SA_EMAIL_ADDRESS sources: - accessLevel: "*" ingressTo: operations: "*" resources: "*"Replace DSPM_SA_EMAIL_ADDRESS with the email address of the DSPM service agent (
service-org-ORGANIZATION_ID@gcp-sa-dspm-hpsa.).The required IAM roles for the service agent are granted when you enable DSPM, and determine which operations the service agent can perform.
For more information about ingress rules, see Configuring ingress and egress policies.
Create custom data security frameworks
If required, copy the Data security and privacy essentials framework and customize it to meet your data security and compliance requirements. For instructions, see Apply a framework.
Deploy advanced data security cloud controls
If required, add the advanced data security cloud controls to custom frameworks. These controls require additional configuration before you can deploy them. For instructions on deploying cloud controls and frameworks, see Apply a framework.
You can deploy frameworks that include advanced data security cloud controls to your organization, folders, projects, and App Hub applications in folders configured for application management. To deploy the advanced data security cloud controls against applications, the framework can only include these controls. You must select the app-enabled folder and the application that you want the cloud controls to monitor. Applications in host projects or a single-project boundary aren't supported.
Consider the following:
Review the information for each advanced data security cloud control for limitations.
Complete the tasks for each rule, as described in the following table.
Rule Additional configuration Data access governance cloud control - Enable Data
Access audit logs for Cloud Storage and
Agent Platform (where applicable in your environment).
Set the data access permission type to
DATA_READ. Enable the data access logs at the organization level or project level, depending on where you apply the Data access governance cloud control.Verify that only authorized principals are exempted from audit logging. Principals exempted from audit logging are also exempted from DSPM.
- Add one or more allowed principals (up to a maximum of 200
principals), using one of the following formats:
- For a user,
principal://goog/subject/USER_EMAIL_ADDRESSExample:
principal://goog/subject/alex@example.com - For a group,
principalSet://goog/group/GROUP_EMAIL_ADDRESSExample:
principalSet://goog/group/my-group@example.com
- For a user,
Data flow governance cloud control Enable Data Access audit logs for Cloud Storage and Agent Platform (where applicable in your environment).
Set the data access permission type to
DATA_READ. Enable the data access logs at the organization level or project level, depending on where you apply the Data access governance cloud control.Verify that only authorized principals are exempted from audit logging. Principals exempted from audit logging are also exempted from DSPM.
- Specify allowed countries using the country codes that are defined in the Unicode Common Locale Data Repository (CLDR).
Data protection and key governance cloud control Enable CMEK in BigQuery and Agent Platform. Data deletion cloud controls Set the retention periods. For example, to set a 90 day retention period in seconds, set the retention period to 777600.- Enable Data
Access audit logs for Cloud Storage and
Agent Platform (where applicable in your environment).