Question 250
A follow-up assurance review considers this problem: A Kubernetes service account is mounted automatically into pods that never invoke the cluster API. Which outcome best shows the intended improvement?
Explanation
Correct Answer
This is direct test evidence of the control objective in the case: A Kubernetes service account is mounted automatically into pods that never invoke the cluster API. It demonstrates that the proposed response, disable unneeded token automount and apply workload-specific RBAC to the remaining service accounts., produces the measurable result a test pod without API duties has no mounted token and cannot list unrelated cluster resources. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.
Incorrect Answers
In the problem “A Kubernetes service account is mounted automatically into pods that never invoke the cluster API”, evidence “A test function accesses approved objects but is denied unrelated project storage.” is not decisive because it tests “A SaaS company allows serverless functions to assume a cloud role with unrestricted storage read permissions across all projects”; the requested validation is a test pod without API duties has no mounted token and cannot list unrelated cluster resources.
The observed “A crafted event cannot invoke unauthorized actions and vulnerable package versions are detected in the build” validates the separate control “Model event input validation, dependency risk, IAM scope, and downstream resource access for the function” under “An enterprise faces this security constraint: A software team assumes a serverless function cannot be attacked because it has no managed operating system”. The present decision calls for the different result “A test pod without API duties has no mounted token and cannot list unrelated cluster resources” from “Disable unneeded token automount and apply workload-specific RBAC to the remaining service accounts”.
Observation “A compromise simulation cannot use third-party service credentials to impersonate unrelated privileged users.” would be useful for “An enterprise uses legacy Kerberos across an acquisition but accepts unconstrained delegation on servers managed by third parties”, but it does not prove that the response to “A Kubernetes service account is mounted automatically into pods that never invoke the cluster API” achieved the relevant outcome, a test pod without API duties has no mounted token and cannot list unrelated cluster resources.