Question 90
At fictional Ironside University, a software-security team is conducting a security incident follow-up assessment without placing confidential information in build artifacts. The case observation is: A user-story backlog states that a portal must be secure but has no testable authorization or logging acceptance conditions. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?
Explanation
Writer-proposed answer: B (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
Security requirements should be testable design constraints integrated with feature requirements early in the SDLC. Stories include concrete access scenarios, negative tests, log expectations, and reviewed completion evidence.
Incorrect Answers
This response concerns secure design decision records. Here, a user-story backlog states that a portal must be secure but has no testable authorization or logging acceptance conditions. The confirming evidence is: Stories include concrete access scenarios, negative tests, log expectations, and reviewed completion evidence.
Focusing on development security ownership would leave this problem unresolved: A user-story backlog states that a portal must be secure but has no testable authorization or logging acceptance conditions.
Risk based secure design gates concerns another aspect of the problem. Security requirements should be testable design constraints integrated with feature requirements early in the SDLC.