Securing PHI in the cloud: Best practices in AWS environments
summary
Lists concrete controls and outcomes: enforce SSO MFA and least privilege via IAM roles and service accounts, use per-client KMS keys and rotate them, put S3 buckets behind deny-then-allow bucket policies and versioning, put secrets in Secrets Manager and use instance roles not passwords, Workspaces as non-downloadable dev desktops to inspect PHI, query S3 with Athena as read-only against read replicas, manage infra with Terraform using variables for evolving roles, and rely on cross-region AWS Backup restores when deletions happen.
AI-written summary · about
chapters (11)
- 0:00PHI in AWS introduction
- 1:55Regulatory landscape and AWS services
- 2:39Authentication and access basics
- 4:04Securing S3 for PHI
- 6:14RDS and secrets management
- 7:58Safe data access with AWS WorkSpaces
- 10:27Querying PHI securely with Athena
- 12:35EKS security best practices
- 13:58Logging and backup strategies
- 14:59Incident response preparedness
- 16:26Q&A
related talks
48mDesigning for Privacy in AWS
50mCloud Security: How to Defend Healthcare Data in the Cloud
39mPerils of the cloud
01h 02mStrong security made simple: Putting all the pieces together
55mUsers and their data: Modern access and audit patterns on AWS
44mGuardrails in the Cloud
34mSecurity best practices for End User Computing Services
28mYour journey to temporary credentials in the cloud