Sensitive Data Protection is a managed service that automatically finds, classifies, and protects sensitive information across Google Cloud. It uses over 150 built-in detectors called infoTypes to identify patterns like credit card numbers and personally identifiable information (PII) in both structured databases and unstructured files.
The service scans data stored in BigQuery and Cloud Storage to create data profiles that show where sensitive information lives. Key features include data profiling that generates metrics about tables and columns, on-demand inspection that finds specific sensitive instances, and risk analysis that calculates how likely it is that individuals could be identified from a dataset.
To protect data during use, the service applies de-identification techniques that transform sensitive values into safe formats. Tokenization replaces sensitive data with a unique placeholder that can sometimes be reversed. Format-preserving encryption encrypts data while keeping the original character length, which helps when data must work with older systems. Bucketing replaces specific values with ranges to hide individual identities while still allowing statistical analysis.
Organizations combine Sensitive Data Protection with VPC Service Controls and Identity and Access Management (IAM) to create a complete security architecture. Templates allow administrators to apply consistent protection rules across multiple projects, reducing human error and helping meet global regulatory requirements.
Google Cloud encrypts all customer data at rest by default using the AES-256 algorithm, which is one of the strongest encryption standards available. For commercial data like credit card numbers and PII, organizations often need additional control beyond this default protection to meet strict compliance standards.
Cloud Key Management Service (KMS) lets organizations create, store, and manage cryptographic keys in the cloud. Cloud HSM provides hardware-backed key protection that meets FIPS 140-2 Level 3 standards, which is required by many financial and healthcare regulations. Together, these services allow businesses to generate secure keys, rotate keys automatically to limit exposure, and destroy keys securely when they are no longer needed.
Customer-Managed Encryption Keys (CMEK) give organizations administrative control over their data encryption. With CMEK, a company decides when and how keys encrypt or decrypt information in services like BigQuery and Cloud Storage. This approach satisfies regulations that require customers to hold independent control over their own encryption keys.
Data also needs protection while moving through networks. VPC Service Controls create security perimeters around sensitive resources to prevent data from being copied or transferred to unauthorized locations. This multi-layered strategy helps businesses comply with data residency and data sovereignty laws that require certain information to remain in specific geographic regions.
Protecting commercial data starts with classifying what is sensitive, such as credit card numbers and PII. Sensitive Data Protection tags and tokenizes this information before storage, ensuring the right security rules apply to the most sensitive assets. This classification process directly supports compliance with standards like PCI-DSS that require protecting cardholder data.
VPC Service Controls create a security perimeter around Google Cloud services to prevent data exfiltration, which is the unauthorized transfer of data out of your environment. Within this perimeter, IAM enforces the principle of least privilege, giving users only the access they need to do their jobs. When these tools work together, they isolate sensitive data from the public internet and reduce the attack surface.
Organizations must maintain complete audit trails to demonstrate compliance with global standards. Cloud Logging and Cloud Audit Logs record every action taken within the environment, providing evidence for regulatory auditors. Security Command Center offers centralized threat detection, Cloud Monitoring tracks system health, and VPC Flow Logs record network traffic patterns. Reviewing these logs regularly is required for maintaining continuous compliance in commercial environments.
Organizing resources into a clear hierarchy helps reduce the scope of audits. By grouping sensitive projects into specific Folders, organizations can apply strict policies to just those areas rather than the entire organization. This segmentation isolates the Cardholder Data Environment from non-sensitive systems, which saves time and lowers the cost of maintaining compliance certifications.
Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
Sensitive Data Protection is a managed service that automatically finds, classifies, and protects sensitive information across Google Cloud. It uses over 150 built-in detectors called infoTypes to identify patterns like credit card numbers and PII in structured databases and unstructured files, and it applies de-identification techniques to transform sensitive values into safe formats.
Beyond the default AES-256 encryption at rest, organizations can use Cloud Key Management Service (KMS) and Cloud HSM for hardware-backed key protection meeting FIPS 140-2 Level 3 standards. Customer-Managed Encryption Keys (CMEK) give organizations administrative control over when and how keys encrypt or decrypt data in services like BigQuery and Cloud Storage.
VPC Service Controls create a security perimeter around Google Cloud services to prevent data exfiltration, while IAM enforces the principle of least privilege within that perimeter. This combination isolates sensitive data from the public internet and reduces the attack surface.
Use Format-Preserving Encryption (FPE-FFX) for credit card numbers, fixed-size bucketing for customer age, and an infoType inspection transformation with character masking for support notes.
Use Cryptographic Hashing (HMAC-SHA-256) for credit card numbers, primitive character masking for customer age, and replacement transformations for support notes.
Use BigQuery Dynamic Data Masking policy tags for credit card numbers, Cloud KMS envelope encryption for customer age, and Data Catalog column tagging for support notes.
Use Deterministic Encryption (DE) with AES-SIV for credit card numbers, date shifting for customer age, and cryptographic hashing for support notes.
An enterprise is designing an automated data ingestion pipeline to process transaction records before storing them in BigQuery for analytics. The incoming records include sensitive commercial and personally identifiable information (PII) with the following specific requirements:
Which combination of Sensitive Data Protection (Cloud DLP) de-identification transformations should the cloud architect specify in the de-identification template?