You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: 'AWS CIS 5.3 Ensure no security groups allow ingress from ::/0 to remote server administration ports',
4
+
5
+
description: 'Security groups provide stateful filtering of ingress and egress network traffic to AWS resources. It is recommended that no security group allows unrestricted ingress access to remote server administration ports, such as SSH to port *22* and RDP to port *3389*.',
6
+
7
+
audit: `Perform the following to determine if the account is configured as prescribed:
8
+
9
+
1. Login to the AWS Management Console at https://console.aws.amazon.com/vpc/home
10
+
2. In the left pane, click *Security Groups*
11
+
3. For each security group, perform the following:
12
+
4. Select the security group
13
+
5. Click the *Inbound Rules* tab
14
+
6. Ensure no rule exists that has a port range that includes port 22, 3389, or other remote server administration ports for your environment and has a Source of ::/0
15
+
16
+
**Note:** A Port value of *ALL* or a port range such as *0-1024* are inclusive of port *22*, *3389*,
17
+
and other remote server administration ports.`,
18
+
19
+
rationale: 'Public access to remote server administration ports, such as 22 and 3389, increases resource attack surface and unnecessarily raises the risk of resource compromise.',
20
+
21
+
remediation: `Perform the following to implement the prescribed state:
22
+
23
+
1. Login to the AWS Management Console at https://console.aws.amazon.com/vpc/home
24
+
2. In the left pane, click *Security Groups*
25
+
3. For each security group, perform the following:
26
+
27
+
Page 215
28
+
29
+
4. Select the security group
30
+
5. Click the *Inbound Rules* tab
31
+
6. Click the *Edit inbound rules* button
32
+
7. Identify the rules to be edited or removed
33
+
8. Either A) update the Source field to a range other than ::/0, or, B) Click *Delete* to remove the offending inbound rule
test('No Security Issue when there is an inbound rule with IPv6 wildcard address and a port range not including the port 22',async()=>{
281
-
awaittestRule(
282
-
100,
283
-
200,
284
-
ipV6WildcardAddress,
285
-
Result.PASS
286
-
)
287
-
})
288
-
289
-
test('No Security Issue when there is an inbound rule with IPv6 wildcard address and a port range not including the port 3389 (multiple values)',async()=>{
290
-
awaittestRule(
291
-
1000,
292
-
2000,
293
-
ipV6WildcardAddress,
294
-
Result.PASS,
295
-
true
296
-
)
297
-
})
298
-
299
281
test('Security Issue when IPv4 wildcard address and port 22',async()=>{
test('No Security Issue when there is an inbound rule with a random IPv4 and a port range not including the port 22',async()=>{
381
+
awaittestRule(
382
+
100,
383
+
200,
384
+
'10.10.10.10/16',
385
+
Result.PASS
386
+
)
387
+
})
388
+
389
+
test('No Security Issue when there is an inbound rule with IPv6 wildcard address and a port range not including the port 22',async()=>{
390
+
awaittestRule(
391
+
100,
392
+
200,
393
+
ipV6WildcardAddress,
394
+
Result.PASS
395
+
)
396
+
})
397
+
398
+
test('No Security Issue when there is an inbound rule with IPv6 wildcard address and a port range not including the port 3389 (multiple values)',async()=>{
399
+
awaittestRule(
400
+
1000,
401
+
2000,
402
+
ipV6WildcardAddress,
403
+
Result.PASS,
404
+
true
405
+
)
406
+
})
407
+
408
+
test('Security Issue when IPv6 wildcard address and port 3389',async()=>{
0 commit comments