Your goal: show Marcus how you think, so your report can tell you where to spend your time.
How this works (about 20 minutes)
- Three short parts: a networking question, a hands-on investigation on a Linux server, and a
prioritisation call you then explain to a non-security VP.
- In part two, ask Marcus for what you'd look at; he gives one fact at a time. The details are
made up for the exercise. Anything else, assume and say so.
- A shared notepad is available. If you want it, ask Marcus to open it.
- No hints and no scores during the call. Your report comes after.
What scores well
- Explaining how things work underneath, and saying plainly what you don't know
- Naming who attacks, what they want and the path they take
- Controls in layers: prevent, detect, respond, each with its cost
- Ranking by impact and likelihood in context, not by a scanner's number
- Leading with the decision, in plain words for the listener
Tips
- Think out loud; there is no pass or fail here.
- Take it again at the end of the course (Security Diagnostic · Re-take) to see what moved.