Question 400
A follow-up assurance review considers this problem: An automated containment workflow isolates any device with one unsigned process event, frequently interrupting authorized field engineers. Which outcome best shows the intended improvement?
Explanation
Correct Answer
This is direct test evidence of the control objective in the case: An automated containment workflow isolates any device with one unsigned process event, frequently interrupting authorized field engineers. It demonstrates that the proposed response, add multi-signal confirmation and human approval for disruptive isolation actions in the SOAR playbook., produces the measurable result benign signed-exception tests remain online and confirmed malicious cases follow the approved isolation gate. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.
Incorrect Answers
The observed “The service meets throughput requirements and raw signing keys remain inside the approved module” validates the separate control “Use an HSM-backed signing service with performance-tested batching or hardware acceleration” under “A financial institution handles high-volume cryptographic signing on ordinary CPU software while key custody rules require separate hardware protection”. The present decision calls for the different result “Benign signed-exception tests remain online and confirmed malicious cases follow the approved isolation gate” from “Add multi-signal confirmation and human approval for disruptive isolation actions in the SOAR playbook”.
In the problem “An automated containment workflow isolates any device with one unsigned process event, frequently interrupting authorized field engineers”, evidence “Simulated network retries create one authorized account change and one auditable result.” is not decisive because it tests “A SOC playbook's webhook retries duplicate the same account-disable action and break an incident recovery workflow”; the requested validation is benign signed-exception tests remain online and confirmed malicious cases follow the approved isolation gate.
For the issue “An automated containment workflow isolates any device with one unsigned process event, frequently interrupting authorized field engineers”, measuring “Test logs contain no reusable secret and API calls remain attributable to approved automation.” would validate “A Python remediation script logs cloud API keys while fetching vulnerability results from a provider SDK” instead of the required control effect: benign signed-exception tests remain online and confirmed malicious cases follow the approved isolation gate.