Your goal: design file sharing that enterprise clients would trust, with every control tied
to an asset and a path, a signal when prevention misses, a cost, and an order.
How this works (about 30 minutes)
- Marcus asks one design question about a made-up company, Harborline, and goes deep on it. Ask
him what you want to know about the clients, the product, the team and what exists today. He
answers one line at a time and won't volunteer.
- Lots of follow-ups, 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 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
- Scope before controls: who shares what with whom, what clients ask for, what exists today
- Assets ranked, including the ones that reach everything
- Attack paths with an attacker, an entry and a route, at the boundaries where trust changes
- Layered controls per path: prevent, detect and respond, each with its cost
- An order you can defend, and a call when a control hurts the clients
- SALT out loud: Scope, Assets, Layers, Trade-offs; answers that land in a minute or two
Tips
- Take Security Coach · Secure Design (SALT) first.
- Ask Marcus what exists today before you design over it.