Sensitive Data Protection: MEDICAL_ID now includes MEDICAL_RECORD_NUMBER
privacygovernancegcpengineer
patch
Sensitive Data Protection has updated its MEDICAL_ID infoType to include MEDICAL_RECORD_NUMBER findings. This change affects users including MEDICAL_ID in their InspectConfig, providing more comprehensive scan results. A legacy option is available for 90 days, allowing for a gradual transition.
Enhancements (1) ›
- Sensitive Data Protection
If you leave InfoType.version unset or set it to stable when including the MEDICAL_ID infoType in your InspectConfig , Sensitive Data Protection will now include MEDICAL_RECORD_NUMBER findings as type MEDICAL_ID in the scan results. You can still use the old functionality by setting InfoType.version to legacy for the next 90 days.
Read the original announcement →
https://docs.cloud.google.com/release-notes#July_13_2026
Related releases
- Cloud Build now supports updating access tokens for Bitbucket and GitLab connections Google Cloud release notes ·
- Looker Update Brings AI Data Agents, In-Database Analytic Models, and CI Enhancements Google Cloud release notes ·
- Gemini Enterprise adds new data stores and actions in preview Google Cloud release notes ·
- Google Cloud Developer Connect Insights & VPC SC Support Now GA Google Cloud release notes ·
- GCP Application Integration Updates Authorization for Integration Runs Google Cloud release notes ·
- Compute Engine now offers LVM and EUS images for Red Hat Enterprise Linux Google Cloud release notes ·