Azure Policy Regulatory Compliance controls for Azure Synapse Analytics
Regulatory Compliance in Azure Policy provides Microsoft 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.
CMMC Level 3
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CMMC Level 3. For more information about this compliance standard, see Cybersecurity Maturity Model Certification (CMMC).
| 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 |
FedRAMP High
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP High. For more information about this compliance standard, see FedRAMP High.
| 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 |
FedRAMP Moderate
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP Moderate. For more information about this compliance standard, see FedRAMP Moderate.
| 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 |
Microsoft cloud security benchmark
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 |
NIST SP 800-171 R2
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-171 R2. For more information about this compliance standard, see NIST SP 800-171 R2.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). | Azure Synapse workspaces should use private link | 1.0.1 |
| Access Control | 3.1.12 | Monitor and control remote access sessions. | Azure Synapse workspaces should use private link | 1.0.1 |
| Access Control | 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. | Azure Synapse workspaces should use private link | 1.0.1 |
| Access Control | 3.1.14 | Route remote access via managed access control points. | Azure Synapse workspaces should use private link | 1.0.1 |
| Access Control | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | Azure Synapse workspaces should use private link | 1.0.1 |
| Risk Assessment | 3.11.2 | Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified. | Vulnerability assessment should be enabled on your Synapse workspaces | 1.0.0 |
| Risk Assessment | 3.11.3 | Remediate vulnerabilities in accordance with risk assessments. | Vulnerability assessment should be enabled on your Synapse workspaces | 1.0.0 |
| System and Communications Protection | 3.13.1 | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | Azure Synapse workspaces should use private link | 1.0.1 |
| System and Communications Protection | 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Azure Synapse workspaces should use customer-managed keys to encrypt data at rest | 1.0.0 |
| System and Communications Protection | 3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | Azure Synapse workspaces should use private link | 1.0.1 |
| System and Communications Protection | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | Azure Synapse workspaces should use private link | 1.0.1 |
NIST SP 800-53 Rev. 4
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 4. For more information about this compliance standard, see NIST SP 800-53 Rev. 4.
| 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 |
NIST SP 800-53 Rev. 5
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 5. For more information about this compliance standard, see NIST SP 800-53 Rev. 5.
| 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 |
NL BIO Cloud Theme
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for NL BIO Cloud Theme. For more information about this compliance standard, see Baseline Information Security Government Cybersecurity - Digital Government (digitaleoverheid.nl).
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| C.04.3 Technical vulnerability management - Timelines | C.04.3 | If the probability of abuse and the expected damage are both high, patches are installed no later than within a week. | Vulnerability assessment should be enabled on your Synapse workspaces | 1.0.0 |
| U.05.2 Data protection - Cryptographic measures | U.05.2 | Data stored in the cloud service shall be protected to the latest state of the art. | Azure Synapse workspaces should use customer-managed keys to encrypt data at rest | 1.0.0 |
| U.07.1 Data separation - Isolated | U.07.1 | Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner. | Azure Synapse workspaces should use private link | 1.0.1 |
| U.11.3 Cryptoservices - Encrypted | U.11.3 | Sensitive data is always encrypted, with private keys managed by the CSC. | Azure Synapse workspaces should use customer-managed keys to encrypt data at rest | 1.0.0 |
| U.17.1 Multi-tenant architecture - Encrypted | U.17.1 | CSC data on transport and at rest is encrypted. | Vulnerability assessment should be enabled on your Synapse workspaces | 1.0.0 |
Reserve Bank of India - IT Framework for NBFC
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Reserve Bank of India - IT Framework for NBFC. For more information about this compliance standard, see Reserve Bank of India - IT Framework for NBFC.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Information and Cyber Security | 3.3 | Vulnerability Management-3.3 | Vulnerability assessment should be enabled on your Synapse workspaces | 1.0.0 |
| IS Audit | 5 | Policy for Information System Audit (IS Audit)-5 | IP firewall rules on Azure Synapse workspaces should be removed | 1.0.0 |
Next steps
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for