Question 500
At fictional Ironside University, a software-security team is conducting a planned system modernization within the approved release and rollback constraints. The case observation is: A financial-transfer feature passes normal happy-path tests but has no negative tests for changing a recipient after approval. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?
Explanation
Writer-proposed answer: D (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
Security testing must exercise forbidden state transitions and business invariants, not only intended workflow success. Tests confirm an approval is bound to the exact beneficiary and amount and cannot be replayed after edits.
Incorrect Answers
This response concerns fuzzing parser boundaries. Here, a financial-transfer feature passes normal happy-path tests but has no negative tests for changing a recipient after approval. The confirming evidence is: Tests confirm an approval is bound to the exact beneficiary and amount and cannot be replayed after edits.
Vulnerability severity context concerns a different operational mechanism. Security testing must exercise forbidden state transitions and business invariants, not only intended workflow success.
Focusing on sast and dast interpretation would leave this problem unresolved: A financial-transfer feature passes normal happy-path tests but has no negative tests for changing a recipient after approval.