IAM and why it is important in Cloud environments
summary
Explains concrete guardrails: using AWS Organizations and service control policies (SCPs) plus tagging and multi-account design to limit blast radius, plus Vault for secrets and GuardDuty for detection. Shows SSO/IAM consolidation and IGA-driven provisioning that automates onboarding/offboarding, including a migration that flipped 50,000 Office 365 users and consolidated ~800 apps. Reports operational wins: audit effort drops from several people each quarter to two people in a week, and remote scale moves from 75 to 150,000 users using SASE/CASB/ZTNA identity controls.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:51Challenges
- 8:08What Are the Four Pillars That We We Identify as Part of Im an Im Program
- 12:15Maintaining Your Compliance Objectives
- 15:30Access Management
related talks
01h 02mWhy IAM is the new perimeter, and how to govern it
25mGetting started with AWS Identity Services
23mGetting started with identity on AWS
12mIAM and Privileged Access Foundations for Secure ML Platforms
34mScaling access with AWS IAM Identity Center, feat.
21mSecuring hundreds of AWS accounts for streamlined governance
58mCreate enterprise-wide preventive guardrails
35mIdentity and Access Management for the Decade Ahead