Ensure that your Enterprise Redis cache clusters are configured to accept TLS connections only in order to meet Microsoft Azure cloud security and compliance requirements. Enforcing TLS-only communication helps prevent unauthorized users from reading sensitive data that is intercepted as it travels through the network, between clients and cache clusters, known as data in transit.
The use of secure TLS connections ensures authentication between the client and the Redis cache cluster and protects data in transit against network layer attacks such as Man-In-The-Middle (MITM) attacks, eavesdropping, and session hijacking. When working with production data, it is strongly recommended to implement encryption to protect it from unauthorized access and to fulfill compliance requirements for data encryption within your organization. For example, a compliance requirement is to protect sensitive data that could potentially identify a specific individual, such as Personally Identifiable Information (PII), which is commonly used in the Financial Services, Healthcare, and Telecommunications sectors."
Audit
To determine if your Enterprise Redis cache clusters are configured to allow non-TLS access, perform the following operations:
Remediation / Resolution
To disable non-TLS, non-encrypted communication and enable TLS-only access for your Enterprise Redis cache clusters, perform the following operations:
Modifying existing TLS protocol configuration for Enterprise Redis cache clusters using Azure Command Line Interface (Azure CLI) is not currently supported.References
- Azure Official Documentation
- What are the Azure Cache for Redis configuration settings for the TLS protocol?
- How to configure Azure Cache for Redis
- Azure Command Line Interface (CLI) Documentation
- az account list
- az account set
- az redisenterprise list
- az redisenterprise show