Azure Policy Regulatory Compliance controls for Azure Cache for Redis

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 Cache for Redis. 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 Database Systems - Database servers	1277	Communications between database servers and web servers - 1277	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
Guidelines for Software Development - Web application development	1552	Web application interactions - 1552	Only secure connections to your Azure Cache for Redis should be enabled	1.0.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)
System and Communications Protection	SC-8(1)	Transmission Confidentiality and Integrity | Cryptographic or Alternate Physical Protection	Only secure connections to your Azure Cache for Redis should be enabled	1.0.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)
Access Control	AC.1.002	Limit information system access to the types of transactions and functions that authorized users are permitted to execute.	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
System and Communications Protection	SC.1.175	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.	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
System and Communications Protection	SC.3.185	Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.	Only secure connections to your Azure Cache for Redis should be enabled	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 Cache for Redis should use private link	1.0.0
Access Control	AC-17	Remote Access	Azure Cache for Redis should use private link	1.0.0
Access Control	AC-17 (1)	Automated Monitoring / Control	Azure Cache for Redis should use private link	1.0.0
System And Communications Protection	SC-7	Boundary Protection	Azure Cache for Redis should use private link	1.0.0
System And Communications Protection	SC-7 (3)	Access Points	Azure Cache for Redis should use private link	1.0.0
System And Communications Protection	SC-8	Transmission Confidentiality And Integrity	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
System And Communications Protection	SC-8 (1)	Cryptographic Or Alternate Physical Protection	Only secure connections to your Azure Cache for Redis should be enabled	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 Cache for Redis should use private link	1.0.0
Access Control	AC-17	Remote Access	Azure Cache for Redis should use private link	1.0.0
Access Control	AC-17 (1)	Automated Monitoring / Control	Azure Cache for Redis should use private link	1.0.0
System And Communications Protection	SC-7	Boundary Protection	Azure Cache for Redis should use private link	1.0.0
System And Communications Protection	SC-7 (3)	Access Points	Azure Cache for Redis should use private link	1.0.0
System And Communications Protection	SC-8	Transmission Confidentiality And Integrity	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
System And Communications Protection	SC-8 (1)	Cryptographic Or Alternate Physical Protection	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0

HIPAA HITRUST 9.2

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - HIPAA HITRUST 9.2. For more information about this compliance standard, see HIPAA HITRUST 9.2.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
08 Network Protection	0809.01n2Organizational.1234-01.n	0809.01n2Organizational.1234-01.n 01.04 Network Access Control	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
08 Network Protection	0810.01n2Organizational.5-01.n	0810.01n2Organizational.5-01.n 01.04 Network Access Control	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
08 Network Protection	0811.01n2Organizational.6-01.n	0811.01n2Organizational.6-01.n 01.04 Network Access Control	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
08 Network Protection	0812.01n2Organizational.8-01.n	0812.01n2Organizational.8-01.n 01.04 Network Access Control	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
08 Network Protection	0814.01n1Organizational.12-01.n	0814.01n1Organizational.12-01.n 01.04 Network Access Control	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
On-line Transactions	0946.09y2Organizational.14 - 09.y	The organization requires the use of encryption between, and the use of electronic signatures by, each of the parties involved in the transaction.	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
14 Third Party Assurance	1451.05iCSPOrganizational.2-05.i	1451.05iCSPOrganizational.2-05.i 05.02 External Parties	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0

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)
System and Communications Protection	9.3.16.6	Transmission Confidentiality and Integrity (SC-8)	Only secure connections to your Azure Cache for Redis should be enabled	1.0.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	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
Communications Security	13.2.1	Information transfer policies and procedures	Only secure connections to your Azure Cache for Redis should be enabled	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 Cache for Redis should use private link	1.0.0
Data Protection	DP-3	Encrypt sensitive data in transit	Only secure connections to your Azure Cache for Redis should be enabled	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 Cache for Redis should use private link	1.0.0
Access Control	3.1.12	Monitor and control remote access sessions.	Azure Cache for Redis should use private link	1.0.0
Access Control	3.1.13	Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.	Azure Cache for Redis should use private link	1.0.0
Access Control	3.1.14	Route remote access via managed access control points.	Azure Cache for Redis should use private link	1.0.0
Access Control	3.1.3	Control the flow of CUI in accordance with approved authorizations.	Azure Cache for Redis 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 Cache for Redis 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 Cache for Redis 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 Cache for Redis should use private link	1.0.0
System and Communications Protection	3.13.8	Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.	Only secure connections to your Azure Cache for Redis should be enabled	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 Cache for Redis should use private link	1.0.0
Access Control	AC-17	Remote Access	Azure Cache for Redis should use private link	1.0.0
Access Control	AC-17 (1)	Automated Monitoring / Control	Azure Cache for Redis should use private link	1.0.0
System And Communications Protection	SC-7	Boundary Protection	Azure Cache for Redis should use private link	1.0.0
System And Communications Protection	SC-7 (3)	Access Points	Azure Cache for Redis should use private link	1.0.0
System And Communications Protection	SC-8	Transmission Confidentiality And Integrity	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
System And Communications Protection	SC-8 (1)	Cryptographic Or Alternate Physical Protection	Only secure connections to your Azure Cache for Redis should be enabled	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 Cache for Redis should use private link	1.0.0
Access Control	AC-17	Remote Access	Azure Cache for Redis should use private link	1.0.0
Access Control	AC-17 (1)	Monitoring and Control	Azure Cache for Redis should use private link	1.0.0
System and Communications Protection	SC-7	Boundary Protection	Azure Cache for Redis should use private link	1.0.0
System and Communications Protection	SC-7 (3)	Access Points	Azure Cache for Redis should use private link	1.0.0
System and Communications Protection	SC-8	Transmission Confidentiality and Integrity	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
System and Communications Protection	SC-8 (1)	Cryptographic Protection	Only secure connections to your Azure Cache for Redis should be enabled	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)
B.09.1 Privacy and protection of personal data - Security aspects and stages	B.09.1	Availability, integrity and confidentiality measures have been taken.	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
U.05.1 Data protection - Cryptographic measures	U.05.1	Data transport is secured with cryptography where key management is carried out by the CSC itself if possible.	Only secure connections to your Azure Cache for Redis should be enabled	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 Cache for Redis should use private link	1.0.0
U.11.1 Cryptoservices - Policy	U.11.1	In the cryptography policy, at least the subjects in accordance with BIO have been elaborated.	Only secure connections to your Azure Cache for Redis should be enabled	1.0.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.	Only secure connections to your Azure Cache for Redis should be enabled	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	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
Requirement 4	4.1	PCI DSS requirement 4.1	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
Requirement 6	6.5.3	PCI DSS requirement 6.5.3	Only secure connections to your Azure Cache for Redis should be enabled	1.0.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	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
Requirement 06: Develop and Maintain Secure Systems and Software	6.2.4	Bespoke and custom software are developed securely	Only secure connections to your Azure Cache for Redis should be enabled	1.0.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)
Secure Mail And Messaging Systems		Secure Mail And Messaging Systems-10.1	Only secure connections to your Azure Cache for Redis should be enabled	1.0.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.4A	Back-office Data Flow Security	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
Reduce Attack Surface and Vulnerabilities	2.6	Operator Session Confidentiality and Integrity	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
Detect Anomalous Activity to Systems or Transaction Records	6.5A	Intrusion Detection	Only secure connections to your Azure Cache for Redis should be enabled	1.0.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	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
Logical and Physical Access Controls	CC6.6	Security measures against threats outside system boundaries	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0
Logical and Physical Access Controls	CC6.7	Restrict the movement of information to authorized users	Only secure connections to your Azure Cache for Redis should be enabled	1.0.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)
Data in transit protection	1	Data in transit protection	Only secure connections to your Azure Cache for Redis should be enabled	1.0.0

Next steps

• Learn more about Azure Policy Regulatory Compliance.
• See the built-ins on the Azure Policy GitHub repo.