Question 1
A payment application is launched with no documented attacker paths between mobile clients and the billing API. What outcome proves the design enforces the requested boundary?
Explanation
Correct Answer
A correct test must show that the threat model identifies spoofing, tampering, and privilege escalation risks for the API. The underlying reason is Structured threat modeling connects concrete attack paths to mitigations.
Incorrect Answers
The proposed evidence relates to another situation: An API's audit records omit which workload identity performed a sensitive action. Nonrepudiation and forensic requirements should be designed into data flows. The architect needs verification that the threat model identifies spoofing, tampering, and privilege escalation risks for the API.
That test would support a different case: A healthcare app is migrating to cloud and security review omits patient record export flows. Data-flow inventories must cover indirect disclosure paths not just primary APIs. The present control must instead show that the threat model identifies spoofing, tampering, and privilege escalation risks for the API.
This observation evaluates A developer exposes account recovery endpoints without considering account enumeration. Security architecture must consider what adversaries learn from interface behavior. It does not establish the required result: the threat model identifies spoofing, tampering, and privilege escalation risks for the API.