Why IAM is the new perimeter, and how to govern it
summary
Panel argues AWS makes identity the perimeter and details concrete practices: federate on‑prem identities, define persona-based roles, and automate role provisioning so devs get access without ticketing. Cites 29% of breaches from stolen credentials, warns about S3 misconfigurations and resource policies, recommends guardrails via CI/CD plus continuous compliance using Config, GuardDuty, Access Advisor and KMS, runs negative tests and auto‑destroy of noncompliant dev resources, and reports improved audit evidence and faster deployments.
AI-written summary · about
chapters (16)
- 0:00Introduction and panel setup
- 1:03Why identity is so hard
- 5:38Identity in cloud environments
- 8:30IAM as the new perimeter
- 10:42Designing IAM on AWS
- 14:16Guardrails and automation
- 20:26Security as a referee
- 24:17Enabling business with guardrails
- 27:11Validating and proving IAM
- 33:14IAM and compliance challenges
- 38:56Compliance in the cloud era
- 43:55Security champions and DevOps
- 47:27Future of IAM and automation
- 50:04Multi-account strategies
- 55:33Least privilege and upskilling
- 59:16Q&A session
related talks
31mIAM and why it is important in Cloud environments
25mGetting started with AWS Identity Services
57mA first-principles approach: AWS Identity and Access Management (IAM)
23mGetting started with identity on AWS
37mLocking Down the Security of IAM
38mEstablishing a Data Perimeter on AWS
50mTraffic safety: Auditing and enforcing IAM best practices
38mChanging Perspectives: A Deep Dive into the Security Posture of 600+ Real-World AWS Environments