Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Regulatory Compliance in Azure Policy provides Azure created and managed initiative definitions, known as built-ins, for the compliance domains and security controls related to different compliance standards. This page lists the compliance domains and security controls for Azure App Configuration. You can assign the built-ins for a security control individually to help make your Azure resources compliant with the specific standard.
The title of each built-in policy definition links to the policy definition in the Azure portal. Use the link in the Policy Version column to view the source on the Azure Policy GitHub repo.
Important
Each control is associated with one or more Azure Policy definitions. These policies might help you assess compliance with the control. However, there often isn't a one-to-one or complete match between a control and one or more policies. As such, Compliant in Azure Policy refers only to the policies themselves. This doesn't ensure that you're fully compliant with all requirements of a control. In addition, the compliance standard includes controls that aren't addressed by any Azure Policy definitions at this time. Therefore, compliance in Azure Policy is only a partial view of your overall compliance status. The associations between controls and Azure Policy Regulatory Compliance definitions for these compliance standards can change over time.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Azure Synapse workspaces should use customer-managed keys to encrypt data at rest | 1.0.0 |
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC-4 | Information Flow Enforcement | Azure Synapse workspaces should use private link | 1.0.1 |
| Access Control | AC-17 | Remote Access | Azure Synapse workspaces should use private link | 1.0.1 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Azure Synapse workspaces should use private link | 1.0.1 |
| Risk Assessment | RA-5 | Vulnerability Scanning | Vulnerability assessment should be enabled on your Synapse workspaces | 1.0.0 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Synapse workspaces should use private link | 1.0.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Synapse workspaces should use private link | 1.0.1 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure Synapse workspaces should use customer-managed keys to encrypt data at rest | 1.0.0 |
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC-4 | Information Flow Enforcement | Azure Synapse workspaces should use private link | 1.0.1 |
| Access Control | AC-17 | Remote Access | Azure Synapse workspaces should use private link | 1.0.1 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Azure Synapse workspaces should use private link | 1.0.1 |
| Risk Assessment | RA-5 | Vulnerability Scanning | Vulnerability assessment should be enabled on your Synapse workspaces | 1.0.0 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Synapse workspaces should use private link | 1.0.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Synapse workspaces should use private link | 1.0.1 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure Synapse workspaces should use customer-managed keys to encrypt data at rest | 1.0.0 |
The Microsoft cloud security benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Microsoft cloud security benchmark, see the Azure Security Benchmark mapping files.
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Microsoft cloud security benchmark.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Identity Management | IM-1 | Use centralized identity and authentication system | Synapse Workspaces should have Microsoft Entra-only authentication enabled | 1.0.0 |
| Identity Management | IM-1 | Use centralized identity and authentication system | Synapse Workspaces should use only Microsoft Entra identities for authentication during workspace creation | 1.2.0 |
| Logging and Threat Detection | LT-1 | Enable threat detection capabilities | Microsoft Defender for SQL should be enabled for unprotected Synapse workspaces | 1.0.0 |
| Logging and Threat Detection | LT-2 | Enable threat detection for identity and access management | Microsoft Defender for SQL should be enabled for unprotected Synapse workspaces | 1.0.0 |
| Incident Response | IR-3 | Detection and analysis - create incidents based on high-quality alerts | Microsoft Defender for SQL should be enabled for unprotected Synapse workspaces | 1.0.0 |
| Incident Response | AIR-5 | Detection and analysis - prioritize incidents | Microsoft Defender for SQL should be enabled for unprotected Synapse workspaces | 1.0.0 |
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC-4 | Information Flow Enforcement | Azure Synapse workspaces should use private link | 1.0.1 |
| Access Control | AC-17 | Remote Access | Azure Synapse workspaces should use private link | 1.0.1 |
| Access Control | AC-17 (1) | Monitoring and Control | Azure Synapse workspaces should use private link | 1.0.1 |
| Risk Assessment | RA-5 | Vulnerability Monitoring and Scanning | Vulnerability assessment should be enabled on your Synapse workspaces | 1.0.0 |
| System and Communications Protection | SC-7 | Boundary Protection | Azure Synapse workspaces should use private link | 1.0.1 |
| System and Communications Protection | SC-7 (3) | Access Points | Azure Synapse workspaces should use private link | 1.0.1 |
| System and Communications Protection | SC-12 | Cryptographic Key Establishment and Management | Azure Synapse workspaces should use customer-managed keys to encrypt data at rest | 1.0.0 |
- See the built-ins on the Azure Policy GitHub repo.