AWS · Identity · Intermediate Security Engineering
AWS Intermediate Identity Track
A practical L2 learning path for AWS identity engineers: effective permissions, explicit deny, permission boundaries, SCP guardrails, resource policies, and public access risk reasoning.
Overview
This track gives learners the intermediate reasoning layer between AWS IAM basics and Principal-level identity attack-path modeling.
Concept Deep Dives
Use these expandable windows for quick study, mentoring, and executive explanation.
Why does L2 exist?
L2 is the reasoning layer between vocabulary and advanced attack-path modeling. A learner should understand how permissions are evaluated before studying cross-account, PassRole, or role chaining paths.
What is effective permission?
Effective permission is the final authority a principal actually has after identity policies, resource policies, boundaries, session policies, SCPs, and explicit denies are evaluated together.
How should students study this track?
- Start with the current L2 LAB.
- Use the visual model to reason through allow and deny paths.
- Then move into the L3 Principal Identity Track.
What should executives understand?
Identity risk is often created by permission composition, not a single bad setting. L2 explains why cloud authorization must be reviewed as a decision system.
Current LAB
The first active L2 LAB teaches IAM policy evaluation and effective-permission reasoning.
Executive Study Guide
The AWS L2 Authorization Model guide summarizes the six-lab intermediate curriculum into one executive, mentor, and student-facing learning artifact.
Coming Next
These planned L2 LABs expand the intermediate identity lane without jumping directly into L3 Principal scenarios.
Learning Ladder
The L2 Intermediate track is the bridge between foundational vocabulary and Principal LAB reasoning.
L1: AWS IAM Basics
↓
L2: AWS Intermediate Identity Track
├── AWS IAM Policy Evaluation
├── AWS Permission Boundary Basics
├── AWS SCP Guardrail Reasoning
├── AWS Resource Policy Evaluation
├── AWS S3 Public Access Risk
├── AWS KMS Key Policy Evaluation
├── AWS Secrets Manager Access Evaluation
├── AWS Lambda Execution Role Risk
└── AWS CloudTrail Detection Reasoning
↓
L3: AWS Principal Identity Track
├── Cross-Account Role Escalation
├── iam:PassRole Privilege Escalation
└── Role Chaining Escalation
Governance Boundary
This track is educational, read-only, and deterministic.
Runtime = source of truth
OPA = decision authority
Aegis = bounded intelligence
Frontend = rendering only
- Does not exploit AWS
- Does not mutate infrastructure
- Does not deploy live resources
- Does not issue runtime tokens
- Does not create runtime sessions
- Does not override OPA