Question 300
At fictional Kestrel Works, a software-security team is conducting a planned system modernization within the approved release and rollback constraints. The case observation is: A service deploys strong multifactor authentication but permits a helpdesk agent to disable it using only a caller's email address. 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
Weak fallback authentication can undermine stronger primary authentication controls. Simulated social-engineering requests fail, approved recoveries produce attributable records and notifications.
Incorrect Answers
This response concerns session revocation after termination. Here, a service deploys strong multifactor authentication but permits a helpdesk agent to disable it using only a caller's email address. The confirming evidence is: Simulated social-engineering requests fail, approved recoveries produce attributable records and notifications.
Server side object authorization concerns a different operational mechanism. Weak fallback authentication can undermine stronger primary authentication controls.
Focusing on privilege escalation by role flags would leave this problem unresolved: A service deploys strong multifactor authentication but permits a helpdesk agent to disable it using only a caller's email address.