Architecting a secure cloud framework
summary
Cloud security focuses on concrete controls: use CSPM scans across multi‑cloud estates and SIEMs like Splunk/Sentinel for correlation, enforce Landing zones that auto‑hook monitoring and identity, apply guardrail policies to block deployments outside approved regions, and enable MFA (about 85% of breaches stop with MFA). Treat API protection and logging as mandatory after incidents like Optus, rotate secrets (GitHub 24‑month limit), and automate remediation for hygiene gaps rather than relying on ad‑hoc on‑prem tools.
AI-written summary · about
chapters (38)
- 0:00Introduction
- 0:26Agenda
- 1:38Who am I
- 2:48Highlevel principles
- 3:36We suck
- 4:17What happened
- 5:22What has changed
- 5:34Hybrid environments
- 6:22Changing processes architectures
- 8:30Threat landscape
- 13:22Multicloud threats
- 14:40API attacks
- 15:36Capabilities
- 17:36Shared responsibility
- 18:51Changing roles
- 19:16The human side
- 20:29Adoption models
- 20:41Modernising
- 22:18What cant do it
- 24:20Devsecops
- 26:55Antipatterns
- 30:02What do you do
- 30:24Best practices
- 30:38Industry standards
- 31:27Landing zones
- 32:24Compliance
- 33:52Azure Policy
- 36:38Capabilities you should know
- 37:17Identity
- 39:30Passwords
- 41:11Connectivity
- 42:05Encryption
- 42:32API Protection
- 43:18Logging Monitoring
- 43:56Examples of Logging
- 44:26Posture Management
- 48:11Summary
- 49:25Outro
related talks
16mSecuring your Cloud infrastructure: a first baseline
31mA Comprehensive Approach to Cloud Security Posture Management
58mCloud Attack Surface Management
43mWalking on Broken Clouds
29mSecuring the Cloud: Multi-Layered Protection for Enterprises
01h 09mCloud Safeguarding: View from Cloud Providers
46mHow to Adapt to Security Changes in Cloud SaaS Transformation
26mCloud Security Lessons