Skip to main content
RansomLeak Security Training

Every exercise is indexed by name, CWE, OWASP, MITRE ATT&CK, CIS, NIST CSF, GDPR and EU AI Act reference.

Try

Full catalogue

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

01

Cloud Infrastructure Security

9 exercises
02

Container & Image Security

8 exercises

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.