Designing Secure Applications in the Cloud
summary
Three concrete patterns for cloud safety: the gatekeeper pattern validates and sanitizes public requests before calling a private service to prevent injection or accidental deletes; the valet key (SAS token) issues time‑limited tokens (example: Azure Blob SAS with a 10‑minute write permission) so clients upload without full creds; the federated identity offloads auth to providers like Azure AD or social logins. Also recommends MFA, just‑in‑time access, STRIDE threat modeling, remove unused VMs, and instrumented monitoring.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:43Benefits of the Cloud
- 3:14Responsibility
- 10:34Security Checklist
- 15:31Gatekeeper Pattern
- 17:57Valky Pattern
- 21:39Federated Identity Pattern
- 25:11MultiFactor Authentication
- 27:48Reduce Attack Surface
- 30:19Threat Modeling
related talks
27mDesigning Secure Applications in the Cloud
21mDesigning Secure APIs in the Cloud
01h 02mLock That Sh*t Down! Auth Security Patterns for Apps, APIs, and Infra
50mArchitecting a secure cloud framework
41mSecurity Patterns for Microservice Architectures
25mSecurity, Identity - Back to the Drawing Board?
47m8 Cloud Design Patterns you ought to know.
16mSecuring your Cloud infrastructure: a first baseline