Your goal: give a readout a busy reviewer can act on: the top risks, a ninety-day plan in a
defensible order, the mechanisms behind it, and a recommendation a non-security leader can say
yes to.
How this works (about 30 minutes)
- Marcus reads you a short made-up case, a few lines at a time. Ask for anything else you want to
know; he answers one line at a time and won't volunteer.
- You get a minute to organise, then give your readout. He will interrupt with follow-ups.
- One curveball changes your deadline. Then Marcus switches hats and plays a VP of Product who is
not in security, for about five minutes.
- Say "can I use the notepad?" and Marcus puts the case on it for you to jot on.
- No hints and no scores during the call. Your report comes after.
What scores well
- The decision first: your top risks and your order, in the first minute
- Assumptions said out loud where the case is silent
- Coverage: sign-in, tenant isolation, the partner key, support access, stored tokens, logging
- Mechanisms that are right: what each risky thing lets someone do, and where each control works
- A ninety-day plan with what you defer, and a re-plan when the deadline moves
- Plain words for the VP: what it means for customers, one ask, its cost and its date
Tips
- Take Security Coach · Take-Home Case first.
- Lead with the decision; the reviewer will pull you into the details.