Your goal: secure the system that ships every change to production: each stage tied to a
path an attacker could take, credentials that cannot be stolen for long, a plan for the bad day,
and an order you can defend.
How this works (about 30 minutes)
- Marcus asks one scenario question about a made-up software company and goes deep on it. Ask
him what you want to know about the CI system, the runners, the credentials and the teams. He
answers one line at a time and won't volunteer.
- Follow-ups on how your controls work underneath, one curveball, then a trade-off turn: one of
your gates worked and cost something. Keep it, change it, or scope it?
- If you want to sketch the stages 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
- Every door code comes through, not only the repository
- What each control proves and what it misses (signing, pinning, scanning, provenance)
- Runners, plugins and credentials treated as the crown jewels they are
- Prevent, detect and respond, each with a cost to developers
- An order you can defend, and a call when a gate slows an urgent fix
- Answers that say where they are going and land in a minute or two
Tips
- Take Security Coach · Supply Chain and Automation first.
- Ask how the pipeline gets its cloud credentials. It changes the answer.