Labs / Cloud Security

Cloud SecurityThe medal for finishing it

Road 25 of 33

Cloud Security

How a cloud estate is broken into and what holds it safe: a leaked access key kept to least privilege, and the instance metadata service an SSRF turns against the very app that trusts it.

2 groups · 5 labs · builds on Night Watch

Start this road

Data left in the open: buckets, keys & code

Cloud storage and the keys and code that open it.

  1. 01 The bucket that answered to everyone A customer-data bucket left public beside the one that should be, found and locked from the outside.
  2. 02 A deploy key that could read everything A CI key scoped to `*`, caught over-reaching into the orders bucket and cut back to least privilege.
  3. 03 Catch it in the code A Terraform-style change declares a public bucket and a plaintext password; both are caught, fixed and applied.

Stealing a workload's keys

An SSRF and an injection that read a workload's own role credentials.

  1. 01 The address only the app could reach An SSRF in a link-preview app reads the instance role's keys from the metadata service, and then the path is cut.
  2. 02 The greeting that read its own keys A serverless function lets the caller supply its greeting template, which reads the role credentials out of its environment.

What its labs use

Concepts

Commands

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Sign in with Google or email to start.

Start this lab