Question 110
At fictional Jasperhill Museum, a software-security team is conducting a regulated data-protection review while protecting cross-tenant boundaries. The case observation is: A release process treats all security checks as a single final approval even when high-risk payments features receive the same scrutiny as a static help page. 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
Risk-based security integrates assurance where design decisions are still changeable instead of relying on late blanket review. High-risk changes show early design review, scoped tests, explicit exceptions, and recorded signoff, while low-risk changes follow lighter evidence.
Incorrect Answers
This response concerns security exception lifecycle. Here, a release process treats all security checks as a single final approval even when high-risk payments features receive the same scrutiny as a static help page. The confirming evidence is: High-risk changes show early design review, scoped tests, explicit exceptions, and recorded signoff, while low-risk changes follow lighter evidence.
Focusing on development security ownership would leave this problem unresolved: A release process treats all security checks as a single final approval even when high-risk payments features receive the same scrutiny as a static help page.
Security acceptance criteria concerns another aspect of the problem. Risk-based security integrates assurance where design decisions are still changeable instead of relying on late blanket review.