Security, Identity - Back to the Drawing Board?
summary
Claims that public cloud risk centers on lack of transparency and a shifted trust boundary, with the perimeter “melted” and controls needing to sit next to data; developers write code in two days but internal deployment takes ~30 days and security testing a week, so automation and self-service are required. Proposes a risk-based model with pre-approved patterns and baked-in controls, recommends OAuth for externalized authz and standards like SAML/SPML and CloudAudit-style realtime auditing.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:40Security
- 4:15Controls portability
- 7:20Other risks
- 8:30Identity
- 9:56Access Control
- 12:43Cloud Computing
- 14:18RiskBased Approach
- 18:57Leveraging Standards
- 21:45QA
related talks
48mControlling Clouds: Beyond Safety
46mHow to Adapt to Security Changes in Cloud SaaS Transformation
26mCloud Security Lessons
31mSeeing Through the Fog - Navigating the Security Landscape of a Cloud-First World
39mManaging Trust Between Multiple Clouds and Non-human Identities Without Passwords
43mSecurity By Design
49mArchitecting Security for Regulated Workloads in Hybrid Cloud
24mCracking the Code of Cloud Security