A.8.11 Data Masking
What is this control?
ISO 27001 control A.8.11 Data Masking limits unnecessary exposure of sensitive data including Personally Identifiable Information through a combination of strict access controls, data minimisation, native platform data masking features, and secure non-production environment handling. The control addresses risks of sensitive data exposure during development, testing, analytics, or support scenarios where individuals without legitimate need-to-know might access it.
How to implement in Microsoft 365
Implement A.8.11 by applying the principle of Least Privilege Access to restrict who can view sensitive data in the first place. Configure SQL Server Dynamic Data Masking for structured data in SQL Server Managed Instance or VMs. Implement Microsoft Entra Conditional Access, Azure RBAC, and Microsoft Entra PIM for access-based data masking.
Configure Microsoft Purview Sensitivity Labels with protection settings including encryption, content marking, and watermarks. Deploy Microsoft Purview Data Loss Prevention policies across Exchange, SharePoint, OneDrive, and Teams. Restrict access to logs containing potentially sensitive information via Azure RBAC on Log Analytics workspaces.
What an auditor looks for
Auditors will verify RBAC and Conditional Access policies are configured and enabled for data access control. They will check Sensitivity labels are configured with protection settings including encryption or content marking. Auditors will verify Azure Log Analytics RBAC is configured to restrict access to log data.
They will check DLP policies are deployed across M365 workloads to detect and block sensitive data sharing. Auditors will verify Test Tenant data handling procedures are documented with approval records for any production data use.