The YAML file was wrong. One field name was typed incorrectly, and the cluster’s access control cracked open like a door left ajar. In that gap sat Protected Health Information, exposed to anyone who found the trail. Kubernetes does not forgive such mistakes.
Kubernetes access to PHI is a security and compliance challenge with no margin for error. HIPAA requires strict controls. That means every ServiceAccount, Role, and RoleBinding must match least privilege principles. One wrong wildcard can grant broad access to secrets, patient records, or logs containing PHI.
Access control in Kubernetes relies on RBAC policies and network segmentation. Use Kubernetes namespaces to isolate workloads handling PHI from those that do not. Enforce API server authentication with short-lived tokens or client certificates. Rotate credentials often. Audit the API server logs for suspicious access patterns.
Encrypt PHI at rest with Kubernetes secrets backed by a secure KMS. Enforce TLS for all in-cluster and external traffic. Never store unencrypted PHI in ConfigMaps, environment variables, or plain-text files. If an application requires PHI, define roles granting only the exact API verbs it needs—get, list, watch—and only on the required resource types.