Chaos to Control: Automating the Identity Life Cycle in the Cloud
summary
Cloud identity lifecycle automation that actually works: use Workday as the source of truth, trigger Azure Functions or Logic Apps to provision Entra ID accounts, assign RBAC roles, and use PIM/JIT for time-limited elevation. Citeable numbers: Verizon says 65% of breaches involve stolen credentials, IBM reports $4.8M average credential breach cost (2025) and automated security finds breaches 105 days faster, and Gartner finds 90% of cloud permissions unused (2023). Automate 90/90 disable/delete windows, remove empty groups, and flag idle resources and licenses.
AI-written summary · about
chapters (11)
- 0:00Identity automation intro
- 1:11What is identity lifecycle
- 3:36Manual identity crisis
- 7:26Automation for security
- 8:09Cloud identity creation
- 9:55SSO for local accounts
- 13:02RBAC and JIT permissions
- 15:09Automated identity reviews
- 17:16Identity deletion cleanup
- 19:42Key takeaways
- 21:04Q&A
related talks
56mEmerging threats against cloud application identities and what you should do about it
31mLog In Through the Front Door: Automating Defense Against...
45mApplying Past Lessons for Intel-Driven Identity Threat Detection
12mIdentity and permissions concerns to watch out for
36mIAM Confused: Decoding 8 Real World Cloud Identity Breaches
40mManaging Access Entitlements & Their Lifecycle in a Multi-Cloud Environment
23mAccess is the New Breach: Observability Must Start with Identity
25mSecurity, Identity - Back to the Drawing Board?