Azure Policy Regulatory Compliance controls for Azure Automation
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 Automation. 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. | Automation account variables should be encrypted | 1.1.0 |
System and Communications Protection | SC.3.191 | Protect the confidentiality of CUI at rest. | Automation account variables should be encrypted | 1.1.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) |
---|---|---|---|---|
System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure Automation accounts should use customer-managed keys to encrypt data at rest | 1.0.0 |
System And Communications Protection | SC-28 | Protection Of Information At Rest | Automation account variables should be encrypted | 1.1.0 |
System And Communications Protection | SC-28 (1) | Cryptographic Protection | Automation account variables should be encrypted | 1.1.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) |
---|---|---|---|---|
System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure Automation accounts should use customer-managed keys to encrypt data at rest | 1.0.0 |
System And Communications Protection | SC-28 | Protection Of Information At Rest | Automation account variables should be encrypted | 1.1.0 |
System And Communications Protection | SC-28 (1) | Cryptographic Protection | Automation account variables should be encrypted | 1.1.0 |
ISO 27001:2013
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - ISO 27001:2013. For more information about this compliance standard, see ISO 27001:2013.
Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
---|---|---|---|---|
Cryptography | 10.1.1 | Policy on the use of cryptographic controls | Automation account variables should be encrypted | 1.1.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) |
---|---|---|---|---|
Data Protection | DP-4 | Enable data at rest encryption by default | Automation account variables should be encrypted | 1.1.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) |
---|---|---|---|---|
System and Communications Protection | 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Azure Automation accounts should use customer-managed keys to encrypt data at rest | 1.0.0 |
System and Communications Protection | 3.13.16 | Protect the confidentiality of CUI at rest. | Automation account variables should be encrypted | 1.1.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) |
---|---|---|---|---|
System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure Automation accounts should use customer-managed keys to encrypt data at rest | 1.0.0 |
System And Communications Protection | SC-28 | Protection Of Information At Rest | Automation account variables should be encrypted | 1.1.0 |
System And Communications Protection | SC-28 (1) | Cryptographic Protection | Automation account variables should be encrypted | 1.1.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) |
---|---|---|---|---|
System and Communications Protection | SC-12 | Cryptographic Key Establishment and Management | Azure Automation accounts should use customer-managed keys to encrypt data at rest | 1.0.0 |
System and Communications Protection | SC-28 | Protection of Information at Rest | Automation account variables should be encrypted | 1.1.0 |
System and Communications Protection | SC-28 (1) | Cryptographic Protection | Automation account variables should be encrypted | 1.1.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.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 Automation accounts should use customer-managed keys to encrypt data at rest | 1.0.0 |
U.07.3 Data separation - Management features | U.07.3 | U.07.3 - The privileges to view or modify CSC data and/or encryption keys are granted in a controlled manner and use is logged. | Automation account variables should be encrypted | 1.1.0 |
U.11.1 Cryptoservices - Policy | U.11.1 | In the cryptography policy, at least the subjects in accordance with BIO have been elaborated. | Automation account variables should be encrypted | 1.1.0 |
U.11.2 Cryptoservices - Cryptographic measures | U.11.2 | In case of PKIoverheid certificates use PKIoverheid requirements for key management. In other situations use ISO11770. | Automation account variables should be encrypted | 1.1.0 |
U.11.3 Cryptoservices - Encrypted | U.11.3 | Sensitive data is always encrypted, with private keys managed by the CSC. | Azure Automation accounts should use customer-managed keys to encrypt data at rest | 1.0.0 |
PCI DSS 3.2.1
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see PCI DSS 3.2.1. For more information about this compliance standard, see PCI DSS 3.2.1.
Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
---|---|---|---|---|
Requirement 3 | 3.4 | PCI DSS requirement 3.4 | Automation account variables should be encrypted | 1.1.0 |
Requirement 4 | 4.1 | PCI DSS requirement 4.1 | Automation account variables should be encrypted | 1.1.0 |
Requirement 6 | 6.5.3 | PCI DSS requirement 6.5.3 | Automation account variables should be encrypted | 1.1.0 |
PCI DSS v4.0
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 PCI DSS v4.0. For more information about this compliance standard, see PCI DSS v4.0.
Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
---|---|---|---|---|
Requirement 03: Protect Stored Account Data | 3.5.1 | Primary account number (PAN) is secured wherever it is stored | Automation account variables should be encrypted | 1.1.0 |
Requirement 06: Develop and Maintain Secure Systems and Software | 6.2.4 | Bespoke and custom software are developed securely | Automation account variables should be encrypted | 1.1.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.1.h | Public Key Infrastructure (PKI)-3.1 | Automation account variables should be encrypted | 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) |
---|---|---|---|---|
Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | Automation account variables should be encrypted | 1.1.0 |
SWIFT CSP-CSCF v2021
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 SWIFT CSP-CSCF v2021. For more information about this compliance standard, see SWIFT CSP CSCF v2021.
Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
---|---|---|---|---|
Reduce Attack Surface and Vulnerabilities | 2.1 | Internal Data Flow Security | Automation account variables should be encrypted | 1.1.0 |
Reduce Attack Surface and Vulnerabilities | 2.4A | Back-office Data Flow Security | Automation account variables should be encrypted | 1.1.0 |
Reduce Attack Surface and Vulnerabilities | 2.5A | External Transmission Data Protection | Automation account variables should be encrypted | 1.1.0 |
SWIFT CSP-CSCF v2022
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 SWIFT CSP-CSCF v2022. For more information about this compliance standard, see SWIFT CSP CSCF v2022.
Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
---|---|---|---|---|
2. Reduce Attack Surface and Vulnerabilities | 2.1 | Ensure the confidentiality, integrity, and authenticity of application data flows between local SWIFT-related components. | Automation account variables should be encrypted | 1.1.0 |
2. Reduce Attack Surface and Vulnerabilities | 2.4A | Back-office Data Flow Security | Automation account variables should be encrypted | 1.1.0 |
2. Reduce Attack Surface and Vulnerabilities | 2.5A | External Transmission Data Protection | Automation account variables should be encrypted | 1.1.0 |
UK OFFICIAL and UK NHS
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - UK OFFICIAL and UK NHS. For more information about this compliance standard, see UK OFFICIAL.
Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
---|---|---|---|---|
Asset protection and resilience | 2.3 | Data at rest protection | Automation account variables should be encrypted | 1.1.0 |
Next steps
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.
Feedback
https://aka.ms/ContentUserFeedback.
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:Submit and view feedback for