Tools / Microsoft Threat Modeling Tool (TMT) Interview questions
How do you handle threats marked "Not Applicable" during an audit?
An auditor should expect to find a specific, substantive justification attached to every Not Applicable threat, not just the bare state label sitting there on its own.
The discipline is to always fill in the Justification field with the concrete reason that STRIDE category doesn't apply to that particular element - for example, "this store is read-only static content served from a CDN, so there's no write path for Tampering to exploit" - because a state with no reasoning attached is functionally indistinguishable from someone marking a real risk as dismissed just to make the report look cleaner. Verifying that every Not Applicable entry has a real, specific justification (rather than a generic one copy-pasted across many threats) is exactly what that part of an audit is trying to catch.
More Related questions...