Question 620
Following the issue — A server migration reuses a storage account key for SMB access although the organization requires identity-based file authentication. — the team takes this action: Configure supported Azure Files identity authentication and share authorization for the target environment. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Review identity source and file ACL compatibility before server migrations. This mitigates the control weakness because: Azure Files can use identity-based SMB access when its authentication prerequisites are met. Keep the intervention, Configure supported Azure Files identity authentication and share authorization for the target environment., in the approved deployment, monitoring and change governance process.
Incorrect Answers
That review protects the control associated with: Container vulnerabilities can exist in workloads even when host nodes are up to date. It does not directly prevent the stated recurrence, which concerns: Azure Files can use identity-based SMB access when its authentication prerequisites are met. The appropriate guardrail is “Review identity source and file ACL compatibility before server migrations”.
“Teach reviewers the limitations of masking versus encryption and role-based access” addresses a different recurring failure: Dynamic masking is not a comprehensive confidentiality boundary against arbitrary query inference. For the condition in this question, maintain “Review identity source and file ACL compatibility before server migrations” because azure Files can use identity-based SMB access when its authentication prerequisites are met.
That review protects the control associated with: Client-side cryptography depends on coordinated keys, metadata and compatible application drivers. It does not directly prevent the stated recurrence, which concerns: Azure Files can use identity-based SMB access when its authentication prerequisites are met. The appropriate guardrail is “Review identity source and file ACL compatibility before server migrations”.