1
1
---
2
+ reviewed : 2024-09-27
2
3
severity : Critical
3
4
pillar : Security
4
5
category : SE:07 Encryption
@@ -15,31 +16,35 @@ Redis Cache should reject TLS versions older than 1.2.
15
16
16
17
## DESCRIPTION
17
18
18
- The minimum version of TLS that Redis Cache accepts is configurable.
19
+ The minimum version of TLS that Redis Cache accepts was previously configurable.
19
20
Older TLS versions are no longer considered secure by industry standards, such as PCI DSS.
20
21
21
- Azure lets you disable outdated protocols and require connections to use a minimum of TLS 1.2.
22
- By default, TLS 1.0, TLS 1.1, and TLS 1.2 is accepted.
22
+ Depending on when your cache was deployed you may be using a default that specifies an older version of TLS.
23
+ Any new deployments do not allow TLS 1.0 or 1.1 to be specified, however existing cache deployment may require updating.
24
+
25
+ Support for TLS 1.0 and TLS 1.1 will be removed in 1 November 2024.
23
26
24
27
## RECOMMENDATION
25
28
26
29
Consider configuring the minimum supported TLS version to be 1.2.
27
- Support for TLS 1.0/ 1.1 version will be removed .
30
+ No action is required for new cache deployments from March 2024, which only support a minimum of TLS 1.2 .
28
31
29
32
## EXAMPLES
30
33
31
34
### Configure with Azure template
32
35
33
36
To deploy caches that pass this rule:
34
37
35
- - Set the ` properties.minimumTlsVersion ` property to a minimum of ` 1.2 ` .
38
+ - Set the ` properties.minimumTlsVersion ` property to a minimum of ` 1.2 ` for existing caches with an old version of TLS configured.
39
+ It is not possible to set the ` properties.minimumTlsVersion ` on new cache deployments from March 2024.
40
+ New cache deployments only support a minimum TLS version of 1.2.
36
41
37
42
For example:
38
43
39
44
``` json
40
45
{
41
46
"type" : " Microsoft.Cache/redis" ,
42
- "apiVersion" : " 2023-04 -01" ,
47
+ "apiVersion" : " 2024-03 -01" ,
43
48
"name" : " [parameters('name')]" ,
44
49
"location" : " [parameters('location')]" ,
45
50
"properties" : {
@@ -53,7 +58,8 @@ For example:
53
58
"redisConfiguration" : {
54
59
"maxmemory-reserved" : " 615"
55
60
},
56
- "enableNonSslPort" : false
61
+ "enableNonSslPort" : false ,
62
+ "publicNetworkAccess" : " Disabled"
57
63
},
58
64
"zones" : [
59
65
" 1" ,
@@ -67,12 +73,14 @@ For example:
67
73
68
74
To deploy caches that pass this rule:
69
75
70
- - Set the ` properties.minimumTlsVersion ` property to a minimum of ` 1.2 ` .
76
+ - Set the ` properties.minimumTlsVersion ` property to a minimum of ` 1.2 ` for existing caches with an old version of TLS configured.
77
+ It is not possible to set the ` properties.minimumTlsVersion ` on new cache deployments from March 2024.
78
+ New cache deployments only support a minimum TLS version of 1.2.
71
79
72
80
For example:
73
81
74
82
``` bicep
75
- resource cache 'Microsoft.Cache/redis@2023-04 -01' = {
83
+ resource cache 'Microsoft.Cache/redis@2024-03 -01' = {
76
84
name: name
77
85
location: location
78
86
properties: {
@@ -87,6 +95,7 @@ resource cache 'Microsoft.Cache/redis@2023-04-01' = {
87
95
'maxmemory-reserved': '615'
88
96
}
89
97
enableNonSslPort: false
98
+ publicNetworkAccess: 'Disabled'
90
99
}
91
100
zones: [
92
101
'1'
@@ -103,6 +112,7 @@ resource cache 'Microsoft.Cache/redis@2023-04-01' = {
103
112
To deploy caches that pass this rule:
104
113
105
114
- Use the ` --set ` parameter.
115
+ This parameter only applies to old cache deployments using TLS 1.0 or TLS 1.1.
106
116
107
117
For example:
108
118
@@ -115,6 +125,7 @@ az redis update -n '<name>' -g '<resource_group>' --set minimumTlsVersion=1.2
115
125
To deploy caches that pass this rule:
116
126
117
127
- Use the ` -MinimumTlsVersion ` parameter.
128
+ This parameter only applies to old cache deployments using TLS 1.0 or TLS 1.1.
118
129
119
130
For example:
120
131
0 commit comments