Azure Policy Regulatory Compliance controls for Azure SignalR

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 SignalR. 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.

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 SignalR Service should use private link 1.0.0
Access Control AC-4 Information Flow Enforcement Azure Web PubSub Service should use private link 1.0.0
Access Control AC-17 Remote Access Azure SignalR Service should use private link 1.0.0
Access Control AC-17 Remote Access Azure Web PubSub Service should use private link 1.0.0
Access Control AC-17 (1) Automated Monitoring / Control Azure SignalR Service should use private link 1.0.0
Access Control AC-17 (1) Automated Monitoring / Control Azure Web PubSub Service should use private link 1.0.0
System And Communications Protection SC-7 Boundary Protection Azure SignalR Service should use private link 1.0.0
System And Communications Protection SC-7 Boundary Protection Azure Web PubSub Service should use private link 1.0.0
System And Communications Protection SC-7 (3) Access Points Azure SignalR Service should use private link 1.0.0
System And Communications Protection SC-7 (3) Access Points Azure Web PubSub Service should use private link 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 SignalR Service should use private link 1.0.0
Access Control AC-4 Information Flow Enforcement Azure Web PubSub Service should use private link 1.0.0
Access Control AC-17 Remote Access Azure SignalR Service should use private link 1.0.0
Access Control AC-17 Remote Access Azure Web PubSub Service should use private link 1.0.0
Access Control AC-17 (1) Automated Monitoring / Control Azure SignalR Service should use private link 1.0.0
Access Control AC-17 (1) Automated Monitoring / Control Azure Web PubSub Service should use private link 1.0.0
System And Communications Protection SC-7 Boundary Protection Azure SignalR Service should use private link 1.0.0
System And Communications Protection SC-7 Boundary Protection Azure Web PubSub Service should use private link 1.0.0
System And Communications Protection SC-7 (3) Access Points Azure SignalR Service should use private link 1.0.0
System And Communications Protection SC-7 (3) Access Points Azure Web PubSub Service should use private link 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)
Network Security NS-2 Secure cloud services with network controls Azure SignalR Service should use private link 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 SignalR Service should use private link 1.0.0
Access Control 3.1.1 Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). Azure Web PubSub Service should use private link 1.0.0
Access Control 3.1.12 Monitor and control remote access sessions. Azure SignalR Service should use private link 1.0.0
Access Control 3.1.12 Monitor and control remote access sessions. Azure Web PubSub Service should use private link 1.0.0
Access Control 3.1.13 Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. Azure SignalR Service should use private link 1.0.0
Access Control 3.1.13 Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. Azure Web PubSub Service should use private link 1.0.0
Access Control 3.1.14 Route remote access via managed access control points. Azure SignalR Service should use private link 1.0.0
Access Control 3.1.14 Route remote access via managed access control points. Azure Web PubSub Service should use private link 1.0.0
Access Control 3.1.3 Control the flow of CUI in accordance with approved authorizations. Azure SignalR Service should use private link 1.0.0
Access Control 3.1.3 Control the flow of CUI in accordance with approved authorizations. Azure Web PubSub Service should use private link 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 SignalR Service should use private link 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 Web PubSub Service should use private link 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 SignalR Service should use private link 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 Web PubSub Service should use private link 1.0.0
System and Communications Protection 3.13.5 Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. Azure SignalR Service should use private link 1.0.0
System and Communications Protection 3.13.5 Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. Azure Web PubSub Service should use private link 1.0.0

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 SignalR Service should use private link 1.0.0
Access Control AC-4 Information Flow Enforcement Azure Web PubSub Service should use private link 1.0.0
Access Control AC-17 Remote Access Azure SignalR Service should use private link 1.0.0
Access Control AC-17 Remote Access Azure Web PubSub Service should use private link 1.0.0
Access Control AC-17 (1) Automated Monitoring / Control Azure SignalR Service should use private link 1.0.0
Access Control AC-17 (1) Automated Monitoring / Control Azure Web PubSub Service should use private link 1.0.0
System And Communications Protection SC-7 Boundary Protection Azure SignalR Service should use private link 1.0.0
System And Communications Protection SC-7 Boundary Protection Azure Web PubSub Service should use private link 1.0.0
System And Communications Protection SC-7 (3) Access Points Azure SignalR Service should use private link 1.0.0
System And Communications Protection SC-7 (3) Access Points Azure Web PubSub Service should use private link 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 SignalR Service should use private link 1.0.0
Access Control AC-4 Information Flow Enforcement Azure Web PubSub Service should use private link 1.0.0
Access Control AC-17 Remote Access Azure SignalR Service should use private link 1.0.0
Access Control AC-17 Remote Access Azure Web PubSub Service should use private link 1.0.0
Access Control AC-17 (1) Monitoring and Control Azure SignalR Service should use private link 1.0.0
Access Control AC-17 (1) Monitoring and Control Azure Web PubSub Service should use private link 1.0.0
System and Communications Protection SC-7 Boundary Protection Azure SignalR Service should use private link 1.0.0
System and Communications Protection SC-7 Boundary Protection Azure Web PubSub Service should use private link 1.0.0
System and Communications Protection SC-7 (3) Access Points Azure SignalR Service should use private link 1.0.0
System and Communications Protection SC-7 (3) Access Points Azure Web PubSub Service should use private link 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)
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 SignalR Service should use private link 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 Web PubSub Service should use private link 1.0.0

Next steps