Cloud & Container Security Training
Break into a misconfigured AWS account and a privileged container, then lock both down.
17 exercises 2 courses Free, no sign-up
Cloud Infrastructure Security
9 exercises- Public Storage Buckets List a bucket with no credentials and take the customer export.
- CWE-732
- ATT&CKT1530
- CIS 3
- NIST CSFPR.DS
- Over-Permissive IAM Escalate a boring build credential into a full administrator.
- CWE-269
- ATT&CKT1098.003
- CIS 6
- NIST CSFPR.AA
- Long-Lived Access Keys Replay a key that leaked months ago and still authenticates.
- CWE-798
- ATT&CKT1552.001
- CIS 5
- NIST CSFPR.AA
- Instance Metadata Abuse Turn a URL-fetching feature into cloud credential theft.
- CWE-918
- ATT&CKT1552.005
- CIS 4
- NIST CSFPR.PS
- Cloud Network Exposure Connect straight to a production database with no application in the path.
- CWE-668
- ATT&CKT1046
- CIS 12
- NIST CSFPR.IR
- Subdomain Takeover Serve your own login page from a domain the company really owns.
- CWE-672
- ATT&CKT1584.001
- CIS 12
- NIST CSFPR.IR
- Audit Logging Gaps Investigate an incident where the trail covered one region and the intruder deleted the rest.
- CWE-778
- ATT&CKT1562.008
- CIS 8
- NIST CSFPR.PS
- Serverless Over-Privilege Drive a public function URL into an account-wide role.
- CWE-250
- ATT&CKT1552
- CIS 6
- NIST CSFPR.AA
- Multi-Account Boundaries Walk a sandbox credential into production, then put a ceiling above the account.
- CWE-1188
- ATT&CKT1078.004
- CIS 6
- NIST CSFPR.AA
Container & Image Security
8 exercises- Secrets in Image Layers Read a live token out of a layer the build tried to clean up.
- CWE-540
- ATT&CKT1552.001
- CIS 3
- NIST CSFPR.DS
- Privileged Containers Turn a shell in a container into root on the host.
- CWE-250
- ATT&CKT1611
- CIS 4
- NIST CSFPR.PS
- Exposed Docker Daemon Take a production host through an unauthenticated Docker API.
- CWE-306
- ATT&CKT1610
- CIS 4
- NIST CSFPR.PS
- Vulnerable Base Images Exploit a CVE in the OS layer nobody audits.
- CWE-1104
- ATT&CKT1190
- CIS 7
- NIST CSFID.RA
- Malicious Base Images Trace a cryptominer back to one line in a Dockerfile.
- CWE-494
- ATT&CKT1195.002
- CIS 2
- NIST CSFID.AM
- Container Registry Exposure Pull a private image, then replace the tag they deploy.
- CWE-306
- ATT&CKT1525
- CIS 6
- NIST CSFPR.AA
- Container Network Exposure A port mapping puts a production database on the internet.
- CWE-668
- ATT&CKT1046
- CIS 12
- NIST CSFPR.IR
- Minimal Container Images Cut a 412MB runtime down to what actually has to ship.
- CWE-1188
- CIS 2
- NIST CSFID.AM
The Developer Track
Application security split by attack surface. Free, hands-on, no sign-up.
-
Application Security
22 exercisesSQL Injection · Stored XSS · Server-Side Request Forgery
-
API Security
10 exercisesBroken Object Level Authorization · Mass Assignment · Excessive Data Exposure
-
Git & Repository Security
8 exercisesSecrets in Git History · Exposed .git Directory · Malicious Pull Requests
Frequently asked questions
Why do so many cloud incidents come down to identity?
Because a cloud credential is not a key to one room. It is a key to everything that credential is permitted to reach, and the cloud API can create, read and delete the infrastructure the application runs on.
A wildcard policy on a build agent, a function with an administrative role, or a role that trusts a whole account each turn a small foothold into account-wide reach without a single exploit.
Is a container a security boundary?
Not by default. Container isolation is a set of kernel features, and a deployment can switch nearly all of them off without anything looking broken.
Root inside a container is root on the host kernel, so a privileged flag plus a host mount turns code execution in a low-value service into control of the machine underneath it. The boundary is something you configure, not something you get.
Why do secrets survive after a Dockerfile deletes them?
Image layers are append-only. A credential passed into one RUN is recorded in that layer, and a later RUN that removes the file only stacks a new layer on top.
Anyone who pulls the image gets every layer, so the value is still readable. Rotation is the step that cuts access; a multi-stage build or a BuildKit secret mount is what stops it happening again.