Your goal: secure a cluster and the code that builds it, with every control tied to a step of
an attack path, a signal when prevention misses, a cost, and an order.
How this works (about 30 minutes)
- Marcus asks one scenario question about a made-up online retailer and goes deep on it. Ask him
what you want to know about the cluster, the images, the Terraform and the teams. He answers one
line at a time and won't volunteer.
- Lots of follow-ups on how things work underneath, one curveball, then a trade-off turn: one of
your controls worked and cost something. Keep it, change it, or scope it?
- If you want to sketch the path or jot, say "can I use the notepad?" and Marcus puts it up.
- No hints and no scores during the call. Your report comes after.
What scores well
- The asset and the attack path before any control: what an attacker wants and how they move
- How it works underneath: tokens, roles, admission, the plan, the state file
- Build, deploy and run for the cluster; laptop, merge, apply and drift for the Terraform
- Prevent, detect and respond, each with its cost
- An order you can defend, and a call when a control hurts the teams
- Answers that say where they are going and land in a minute or two
Tips
- Take Security Coach · Cloud and Containers first.
- Ask Marcus how pods get their credentials. It changes the answer.