Azure Policy Regulatory Compliance controls for Azure App Configuration
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.
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 | App Configuration should use private link | 1.0.2 |
| Access Control | AC-17 | Remote Access | App Configuration should use private link | 1.0.2 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | App Configuration should use private link | 1.0.2 |
| System And Communications Protection | SC-7 | Boundary Protection | App Configuration should use private link | 1.0.2 |
| System And Communications Protection | SC-7 (3) | Access Points | App Configuration should use private link | 1.0.2 |
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 | App Configuration should use private link | 1.0.2 |
| Access Control | AC-17 | Remote Access | App Configuration should use private link | 1.0.2 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | App Configuration should use private link | 1.0.2 |
| System And Communications Protection | SC-7 | Boundary Protection | App Configuration should use private link | 1.0.2 |
| System And Communications Protection | SC-7 (3) | Access Points | App Configuration should use private link | 1.0.2 |
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 | App Configuration should use private link | 1.0.2 |
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). | App Configuration should use private link | 1.0.2 |
| Access Control | 3.1.12 | Monitor and control remote access sessions. | App Configuration should use private link | 1.0.2 |
| Access Control | 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. | App Configuration should use private link | 1.0.2 |
| Access Control | 3.1.14 | Route remote access via managed access control points. | App Configuration should use private link | 1.0.2 |
| Access Control | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | App Configuration should use private link | 1.0.2 |
| 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. | App Configuration should use private link | 1.0.2 |
| 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. | App Configuration should use private link | 1.0.2 |
| System and Communications Protection | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | App Configuration should use private link | 1.0.2 |
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 | App Configuration should use private link | 1.0.2 |
| Access Control | AC-17 | Remote Access | App Configuration should use private link | 1.0.2 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | App Configuration should use private link | 1.0.2 |
| System And Communications Protection | SC-7 | Boundary Protection | App Configuration should use private link | 1.0.2 |
| System And Communications Protection | SC-7 (3) | Access Points | App Configuration should use private link | 1.0.2 |
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 | App Configuration should use private link | 1.0.2 |
| Access Control | AC-17 | Remote Access | App Configuration should use private link | 1.0.2 |
| Access Control | AC-17 (1) | Monitoring and Control | App Configuration should use private link | 1.0.2 |
| System and Communications Protection | SC-7 | Boundary Protection | App Configuration should use private link | 1.0.2 |
| System and Communications Protection | SC-7 (3) | Access Points | App Configuration should use private link | 1.0.2 |
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. | App Configuration should use private link | 1.0.2 |
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.1.h | Public Key Infrastructure (PKI)-3.1 | App Configuration should use a customer-managed key | 1.1.0 |
Reserve Bank of India IT Framework for Banks v2016
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RBI ITF Banks v2016. For more information about this compliance standard, see RBI ITF Banks v2016 (PDF).
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | App Configuration should use private link | 1.0.2 |
RMIT Malaysia
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RMIT Malaysia. For more information about this compliance standard, see RMIT Malaysia.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Network Resilience | 10.33 | Network Resilience - 10.33 | Configure App Configuration to disable public network access | 1.0.0 |
| Cloud Services | 10.53 | Cloud Services - 10.53 | App Configuration should use a customer-managed key | 1.1.0 |
| Access Control | 10.54 | Access Control - 10.54 | App Configuration should disable public network access | 1.0.0 |
| Data Loss Prevention (DLP) | 11.15 | Data Loss Prevention (DLP) - 11.15 | Configure App Configuration to disable public network access | 1.0.0 |
Next steps
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.