Top 4 Threat modeling Interview Questions
Browse 4 real-world technical and behavioral interview questions about Threat modeling. Review scenarios, edge cases, and architectural best practices.
You are accepting webhooks from two hundred partners. Threat model the ingestion pipeline - what are you actually defending against, and what does the endpoint have to do before it trusts a payload?
The endpoint is an unauthenticated internet-facing entry point that writes to your core systems, so treat every field as attacker-controlled. Verify an HMAC over the raw body in constant time, reject stale timestamps, deduplicate on event id, bound the body size, and hand off to a queue rather than processing inline.
Walk me through applying STRIDE to the boundary where our order service calls the payments service over the network.
A STRIDE threat modeling example works best at one boundary, such as order service to payments service: test spoofing, tampering, repudiation, information disclosure, denial of service and elevation of privilege, then attach one concrete mitigation to each.
You've run a threat model and found real issues, but engineering leadership says the roadmap has no room this quarter. How do you get the fixes prioritised?
Translate each finding from security language into the same terms the roadmap is already prioritised by — a concrete failure scenario, its business cost, and the cheapest point in the system's lifecycle to fix it — rather than asking for time on the strength of the threat model alone.
How do you know when a threat model has gone stale, and how would you catch it before an incident does?
A threat model goes stale when architecture, trust boundaries, dependencies, data flows or abuse assumptions change. The fix is event-driven review triggers in design and delivery workflows, not a calendar reminder that ignores real system change.