Sensitive data in the cloud? You can’t do that!
summary
Argues that sensitive medical data is safe in major clouds and demonstrates concrete controls: Azure Key Vault for keys, SQL Server TDE and client‑side encryption, blob encryption in preview, virtual networks and VPN/Direct Connect for private links, and role lockdown so few admins have access. Cites scalability and cost wins — Danish rail case scales from ~50k to 5M users for about $30 — notes privacy risk from US legal access and recommends separating identifiers into a separate encrypted DB and keeping keys off‑site.
AI-written summary · about
chapters (18)
- 0:00Start
- 3:19Actually, you can!
- 4:24So what is the problem?
- 6:44The insecure cloud is a myth
- 9:25Indirectly identifiable
- 13:34Traditional thinking
- 15:10How is the cloud different?
- 22:25Data in use
- 27:30Data in transit
- 30:47Data at rest
- 33:48The government
- 35:34The cloud is safer than running locally
- 39:22What does the law say?
- 41:18If you are still uncertain
- 43:40Another example
- 44:35Securing your application
- 46:40If you're not on Azure
- 47:42In summary
related talks
01h 59mDeep Dive Workshop – Data Security and Data Protection
01h 59mDeep Dive Workshop – Data Security and Data Protection
39mdev.privacy: GDPR in a nutshell
47mManaging your Secrets in a Cloud Environment
34mDesigning Secure Applications in the Cloud
27mKeynote - Sovereign Cloud Definitions, Drivers, and Solutions
01h 09mCloud Safeguarding: View from Cloud Providers
32mNew Developments in Cloud Technology and Data Security For Practitioners