Identity and Access Management (IAM)
An IAM decision binds a principal, action, resource and conditions; a wildcard in any dimension expands blast radius.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
A role allows broad actions/resources, can be assumed by too many principals, or is never reviewed after temporary escalation.
The important question is not “what is Identity and Access Management (IAM)?” but “which assumption let untrusted data or an over-scoped identity cross authenticated identity → authorized cloud api action?” Trace the decision at the boundary, then constrain what can happen after the first control fails.
Design the control in layers
Start with the control closest to the interpretation or privilege boundary: Scope actions, resources and trust relationships Then add a control that reduces blast radius and telemetry that proves the decision was enforced.
The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.
| Prevent | Detect | Recover |
|---|---|---|
| Scope actions, resources and trust relationships · Separate deployment, runtime and break-glass roles · Review effective access and unused permissions | Denied calls, unusual role assumptions and sensitive API actions | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: Cloud resources and the control-plane actions that change them.
- Boundary: Authenticated identity → authorized cloud API action
- Primary control: Scope actions, resources and trust relationships
- Detection signal: Denied calls, unusual role assumptions and sensitive API actions
- Always ask what limits damage when the primary control fails.
IAM Policy Boundary
Change the system and observe which assumption moves.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: Someone who obtains a human, service, CI or agent identity.
- 2A role allows broad actions/resources, can be assumed by too many principals, or is never reviewed after temporary escalation.
- 3The weak or missing boundary control is crossed: Authenticated identity → authorized cloud API action
- 4Impact: Everything the effective policy permits, often across many resource types.
- Everything the effective policy permits, often across many resource types.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Scope actions, resources and trust relationships
- • Separate deployment, runtime and break-glass roles
- • Review effective access and unused permissions
- • Denied calls, unusual role assumptions and sensitive API actions
- • Contain the affected identity or component.
- • Scope access from audit evidence.
- • Fix the boundary and add a regression test.
- • Misconfiguration and new access paths can bypass the intended control.
- • A privileged insider or compromised control plane may still reach the asset.