Question 680
Following the issue — A backup process stores Azure Files credentials in plain text on every server image. — the team takes this action: Use approved identity-based share authentication or securely managed credentials as supported. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Scan base images for storage credentials and rotate compromised secrets. This mitigates the control weakness because: Distributing storage account secrets in machine images creates broad and persistent exposure. Keep the intervention, Use approved identity-based share authentication or securely managed credentials as supported., in the approved deployment, monitoring and change governance process.
Incorrect Answers
This safeguard is for the dependency described by: Kubernetes management authorization should align with namespace boundaries and operational job needs. The continuing risk here is determined by: Distributing storage account secrets in machine images creates broad and persistent exposure. The targeted safeguard is “Scan base images for storage credentials and rotate compromised secrets”.
“Test SQL auditing destinations after storage permission or network changes” addresses a different recurring failure: Audit policy presence does not prove that authorized log records are successfully stored. For the condition in this question, maintain “Scan base images for storage credentials and rotate compromised secrets” because distributing storage account secrets in machine images creates broad and persistent exposure.
That review protects the control associated with: Audit event selection determines whether activity of interest can be reconstructed. It does not directly prevent the stated recurrence, which concerns: Distributing storage account secrets in machine images creates broad and persistent exposure. The appropriate guardrail is “Scan base images for storage credentials and rotate compromised secrets”.