Azure Policy Regulatory Compliance controls for Azure Service Fabric
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 Service Fabric. 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.
Australian Government ISM PROTECTED
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Australian Government ISM PROTECTED. For more information about this compliance standard, see Australian Government ISM PROTECTED.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Guidelines for System Hardening - Authentication hardening | 1546 | Authenticating to systems - 1546 | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
Canada Federal PBMM
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Canada Federal PBMM. For more information about this compliance standard, see Canada Federal PBMM.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC-2(7) | Account Management | Role-Based Schemes | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
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. | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 1.1.0 |
| System and Communications Protection | SC.3.191 | Protect the confidentiality of CUI at rest. | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 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.
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.
IRS 1075 September 2016
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - IRS 1075 September 2016. For more information about this compliance standard, see IRS 1075 September 2016.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | 9.3.1.2 | Account Management (AC-2) | Service Fabric clusters should only use Azure Active Directory for client authentication | 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 | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 1.1.0 |
| Access Control | 9.2.3 | Management of privileged access rights | Service Fabric clusters should only use Azure Active Directory for client authentication | 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) |
|---|---|---|---|---|
| Identity Management | IM-1 | Use centralized identity and authentication system | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| Data Protection | DP-4 | Enable data at rest encryption by default | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 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) |
|---|---|---|---|---|
| Access Control | 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| Access Control | 3.1.2 | Limit system access to the types of transactions and functions that authorized users are permitted to execute. | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| System and Communications Protection | 3.13.16 | Protect the confidentiality of CUI at rest. | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 1.1.0 |
| Identification and Authentication | 3.5.1 | Identify system users, processes acting on behalf of users, and devices. | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| Identification and Authentication | 3.5.2 | Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems. | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| Identification and Authentication | 3.5.5 | Prevent reuse of identifiers for a defined period. | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| Identification and Authentication | 3.5.6 | Disable identifiers after a defined period of inactivity. | Service Fabric clusters should only use Azure Active Directory for client authentication | 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.
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.
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.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. | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 1.1.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. | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| U.10.2 Access to IT services and data - Users | U.10.2 | Under the responsibility of the CSP, access is granted to administrators. | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| U.10.3 Access to IT services and data - Users | U.10.3 | Only users with authenticated equipment can access IT services and data. | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| U.10.5 Access to IT services and data - Competent | U.10.5 | Access to IT services and data is limited by technical measures and has been implemented. | Service Fabric clusters should only use Azure Active Directory for client authentication | 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. | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 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. | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 1.1.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 | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 1.1.0 |
| Requirement 4 | 4.1 | PCI DSS requirement 4.1 | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 1.1.0 |
| Requirement 6 | 6.5.3 | PCI DSS requirement 6.5.3 | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 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 | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 1.1.0 |
| Requirement 06: Develop and Maintain Secure Systems and Software | 6.2.4 | Bespoke and custom software are developed securely | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 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) |
|---|---|---|---|---|
| User Access Control / Management | User Access Control / Management-8.2 | Service Fabric clusters should only use Azure Active Directory for client authentication | 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) |
|---|---|---|---|---|
| SWIFT Environment Protection | 1.2 | Operating System Privileged Account Control | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| Reduce Attack Surface and Vulnerabilities | 2.1 | Internal Data Flow Security | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 1.1.0 |
System and Organization Controls (SOC) 2
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 System and Organization Controls (SOC) 2. For more information about this compliance standard, see System and Organization Controls (SOC) 2.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Logical and Physical Access Controls | CC6.1 | Logical access security software, infrastructure, and architectures | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 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) |
|---|---|---|---|---|
| Identity and authentication | 10 | Identity and authentication | Service Fabric clusters should only use Azure Active Directory for client authentication | 1.1.0 |
| Asset protection and resilience | 2.3 | Data at rest protection | Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign | 1.1.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