Question 580
Following the issue — A containerized service runs with an unnecessarily privileged Kubernetes service account. — the team takes this action: Bind the pod to a suitably scoped Kubernetes service account with required permissions only. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Inspect Kubernetes service account permissions during every workload rollout. This mitigates the control weakness because: Container workload identities should not inherit broad cluster privileges unnecessarily. Keep the intervention, Bind the pod to a suitably scoped Kubernetes service account with required permissions only., in the approved deployment, monitoring and change governance process.
Incorrect Answers
“Monitor key expiry and access for CMK-encrypted SQL services” addresses a different recurring failure: Customer-managed TDE protectors must remain accessible for database encryption operations. For the condition in this question, maintain “Inspect Kubernetes service account permissions during every workload rollout” because container workload identities should not inherit broad cluster privileges unnecessarily.
That review protects the control associated with: Encryption at rest does not replace strong access control for storage data. It does not directly prevent the stated recurrence, which concerns: Container workload identities should not inherit broad cluster privileges unnecessarily. The appropriate guardrail is “Inspect Kubernetes service account permissions during every workload rollout”.
This safeguard is for the dependency described by: Application database reachability does not guarantee every telemetry or audit egress path. The continuing risk here is determined by: Container workload identities should not inherit broad cluster privileges unnecessarily. The targeted safeguard is “Inspect Kubernetes service account permissions during every workload rollout”.