Edit

Azure Policy Regulatory Compliance controls for Azure Synapse Analytics

  • Article
  • 4 minutes to read

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

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

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 RBI IT Framework 3.3 Vulnerability Management-3.3 Vulnerability assessment should be enabled on your Synapse workspaces 1.0.0
IS Audit RBI IT Framework 5 Policy for Information System Audit (IS Audit)-5 IP firewall rules on Azure Synapse workspaces should be removed 1.0.0

Next steps