Question 420
After the team responds to the following issue, which finding best demonstrates the desired security outcome? A container security workflow launches ephemeral scanning jobs but provides broad access to the production Kubernetes API.
Explanation
Correct Answer
This is direct test evidence of the control objective in the case: A container security workflow launches ephemeral scanning jobs but provides broad access to the production Kubernetes API. It demonstrates that the proposed response, scope scanning service accounts to read-only resources and isolate scan execution with network policy., produces the measurable result a compromised scanner pod cannot modify workload deployments or read unrelated secrets. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.
Incorrect Answers
“A malformed or unapproved input cannot disable an unrelated account” would verify “Require signed approval records, account resolution checks, dry-run output, and audit logging before action” for the situation “A security analyst builds a PowerShell script that disables accounts from CSV input without validating identity or approval”. Here the required evidence is “A compromised scanner pod cannot modify workload deployments or read unrelated secrets” after “Scope scanning service accounts to read-only resources and isolate scan execution with network policy”; the alternative observation does not test that control.
Observation “A test malicious page cannot access local secrets or execute code on the researcher workstation.” would be useful for “A data-science workstation requires browser access to untrusted research websites while retaining sensitive local credentials”, but it does not prove that the response to “A container security workflow launches ephemeral scanning jobs but provides broad access to the production Kubernetes API” achieved the relevant outcome, a compromised scanner pod cannot modify workload deployments or read unrelated secrets.
For the issue “A container security workflow launches ephemeral scanning jobs but provides broad access to the production Kubernetes API”, measuring “Expired low-confidence indicators cannot automatically create production blocking rules.” would validate “An incident workflow sends all threat-intelligence objects into the SIEM without validating source confidence or expiration” instead of the required control effect: a compromised scanner pod cannot modify workload deployments or read unrelated secrets.