Designing for Privacy in AWS
summary
A real HR SaaS on AWS gets redesigned for privacy using the Norwegian Data Protection Authority checklist, ISO certification and AWS well‑architected reviews; implementation uses STRIDE risk analysis, Terraform/CloudFormation, IAM roles with short‑lived creds, secrets in parameter store or Secrets Manager, KMS customer keys, S3 object versioning, CloudTrail/CloudWatch and Elasticsearch logging, Shield/CloudFront and semantic security groups. A pilot light DR with a Stockholm read replica exists but an attempted encrypted RDS restore fails—DR tests are mandatory. Permission tests use personas and scenarios.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:28Real-world privacy-focused HR application story
- 3:56Privacy by Design principles
- 5:41Norwegian DPA checklist
- 7:49Privacy implementation prerequisites
- 13:58Confidentiality in AWS
- 19:43Encryption strategies
- 23:39Prevent privilege escalation
- 24:02Ensure data integrity
- 27:14AWS access control models
- 30:03Data availability strategies
- 34:01Incident management plan
- 34:22High availability and DR
- 37:15Backup and compliance rules
- 39:23Audit trails in AWS
- 41:51Compliance documentation
- 43:54Key takeaways
- 44:58Q&A
related talks
18mSecuring PHI in the cloud: Best practices in AWS environments
19mSecuring your AWS environment with automated DSPM
53mAchieving End-to-end Security on AWS
48mManaging Security on AWS
55mPlan and deploy your own security architecture based on the AWS SRA
58mUsing AWS data protection services for innovation and automation
38mEstablishing a Data Perimeter on AWS
39mPerils of the cloud