Skip to content
AS
08 / Security Engineering2026

Cloud Attack-Path & IAM Lab

An intentionally misconfigured AWS and container range for documenting privilege escalation chains and validating Terraform remediation.

AWS IAMTerraformKubernetesCloudTrail
Case file
Role
Solo build — research, engineering, documentation, release
Status
Active build
Year
2026
Position
08 of 13
Case 08 / cloud-redteam-rangeArchitecture · Evidence · Signal

01 — Context

The problem worth solving.

Cloud security controls are easier to validate when every misconfiguration has a reachable attack path and a measurable fix.

02 — Approach

How it was built.

  1. 01

    Model IAM role chaining, SSRF-to-IMDSv2, Lambda over-privilege, and container breakout paths.

  2. 02

    Enumerate attack graphs from identity and network relationships.

  3. 03

    Write Terraform and OPA guardrails plus CloudTrail detections for each chain.

03 — Architecture

The shape of the system.

01Target

Multi-account AWS and containerised services with deliberate trust failures.

02Attack graph

Identity, network, metadata, and workload relationships mapped to reachable privilege.

03Control

Terraform baselines, OPA policies, and CloudTrail detections.

04 — Evidence

Receipts, not adjectives.

AWScloud target
IAMattack surface
OPApolicy control

05 — Hiring signal

“Connects offensive cloud paths to deployable guardrails instead of isolated findings.”

Ships working systemsDocuments the methodExplains the trade-offsKeeps evidence attached

06 — What's next

Still being built.

Add multi-account lateral movement scenarios and automated remediation tests.