Basic IAM gets people and services their first permissions. The harder problem is keeping those permissions from growing: in most cloud accounts, access piles up over time until one compromised role can reach far more than it ever should have. This module is about putting limits around permissions and spotting the paths attackers use to climb higher.
Permission boundaries cap the most an identity can ever be granted, even if a broader policy is attached later. Service control policies (SCPs) do the same across whole accounts in an organization. To predict what a request will actually be allowed to do, you need to understand policy evaluation: how identity policies, boundaries, SCPs, and explicit denies combine into one decision.
Then the attacker's view: privilege escalation techniques, where a small, innocent-looking permission such as editing a policy or passing a role is enough to become an administrator. The examples use AWS, and the same thinking applies on Azure and Google Cloud. Watch the lessons in order, then continue on to Network Security & Segmentation.
What problem permission boundaries solve, how they work alongside identity policies, and their pros and cons.
How SCPs set organization-wide limits on the permissions available to the accounts under them.
How AWS combines identity-based and resource-based policies, permission boundaries, and SCPs into a single allow or deny decision.
The fundamentals of IAM telemetry and publicly known privilege escalation techniques, shown from the defender's point of view.