This repository has been archived by the owner on Apr 3, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 63
/
AWSConfig.json
1366 lines (1366 loc) · 83.2 KB
/
AWSConfig.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
{
"name": "AWS Config",
"versions": {
"attack": "9",
"navigator": "4.2",
"layer": "4.2"
},
"domain": "enterprise-attack",
"description": "AWS Config rules evaluate the configuration settings of AWS resources in order to detect resources that are out of compliance with internal policies and best practices.",
"filters": {
"platforms": [
"Linux",
"macOS",
"Windows",
"Office 365",
"Azure AD",
"AWS",
"GCP",
"Azure",
"SaaS",
"PRE",
"Network"
]
},
"sorting": 0,
"layout": {
"layout": "side",
"showID": false,
"showName": true,
"showAggregateScores": false,
"countUnscored": false,
"aggregateFunction": "average"
},
"hideDisabled": false,
"techniques": [
{
"techniqueID": "T1020",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "This control provides partial coverage for this technique's only sub-technique, but without specific coverage for its procedures, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1020.001",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure SSL/TLS encryption is enabled to protect network traffic: \"acm-certificate-expiration-check\" for nearly expired certificates in AWS Certificate Manager (ACM); \"alb-http-to-https-redirection-check\" for Application Load Balancer (ALB) HTTP listeners; \"api-gw-ssl-enabled\" for API Gateway REST API stages; \"cloudfront-custom-ssl-certificate\", \"cloudfront-sni-enabled\", and \"cloudfront-viewer-policy-https\", for Amazon CloudFront distributions; \"elb-acm-certificate-required\", \"elb-custom-security-policy-ssl-check\", \"elb-predefined-security-policy-ssl-check\", and \"elb-tls-https-listeners-only\" for Elastic Load Balancing (ELB) Classic Load Balancer listeners; \"redshift-require-tls-ssl\" for Amazon Redshift cluster connections to SQL clients; \"s3-bucket-ssl-requests-only\" for requests for S3 bucket contents; and \"elasticsearch-node-to-node-encryption-check\" for Amazon ElasticSearch Service node-to-node communications.\nAll of these are run on configuration changes except \"alb-http-to-https-redirection-check\", which is run periodically. Coverage factor is partial for these rules, since they are specific to a subset of the available AWS services and can only mitigate behavior for adversaries who are unable to decrypt the relevant traffic, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1040",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure SSL/TLS encryption is enabled to protect network traffic: \"acm-certificate-expiration-check\" for nearly expired certificates in AWS Certificate Manager (ACM); \"alb-http-to-https-redirection-check\" for Application Load Balancer (ALB) HTTP listeners; \"api-gw-ssl-enabled\" for API Gateway REST API stages; \"cloudfront-custom-ssl-certificate\", \"cloudfront-sni-enabled\", and \"cloudfront-viewer-policy-https\", for Amazon CloudFront distributions; \"elb-acm-certificate-required\", \"elb-custom-security-policy-ssl-check\", \"elb-predefined-security-policy-ssl-check\", and \"elb-tls-https-listeners-only\" for Elastic Load Balancing (ELB) Classic Load Balancer listeners; \"redshift-require-tls-ssl\" for Amazon Redshift cluster connections to SQL clients; \"s3-bucket-ssl-requests-only\" for requests for S3 bucket contents; and \"elasticsearch-node-to-node-encryption-check\" for Amazon ElasticSearch Service node-to-node communications.\nThe following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure that private traffic is routed securely and only within VPCs rather than on the public Internet: \"api-gw-endpoint-type-check\" for Amazon API Gateway APIs, \"elasticsearch-in-vpc-only\" for Amazon ElasticSearch Service domains, and \"redshift-enhanced-vpc-routing-enabled\" for Amazon Redshift cluster traffic.\nAll of these are run on configuration changes except \"alb-http-to-https-redirection-check\" and \"elasticsearch-in-vpc-only\", which are run periodically. Coverage factor is partial for these rules, since they are specific to a subset of the available AWS services and can only mitigate behavior for adversaries who are unable to decrypt the relevant traffic and/or do not have access to traffic within the relevant VPCs, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1053",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "This control provides partial coverage for one of this technique's sub-techniques, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1053.007",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The \"eks-endpoint-no-public-access\" managed rule can identify whether Amazon Elastic Kubernetes Service (Amazon EKS) endpoints are misconfigured to allow public endpoint access, which should be fixed in order to prevent malicious external access to the Kubernetes API server, including malicious attempts to create or modify orchestration jobs. It is run periodically and only provides partial coverage because it is specific to public access, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1068",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The \"ec2-managedinstance-applications-blacklisted\" managed rule verifies that a pre-defined list of applications are not installed on specified managed instances. It can be used to identify the presence of vulnerable applications (prompting removal before they can be exploited) and/or to identify the presence of allowed packages below a minimum version (prompting updates before they can be exploited). The \"ec2-managedinstance-platform-check\" managed rule verifies that managed instances are running desired platform types, including using a desired version (as opposed to an out-of-date one). Both can reduce instances' attack surface for adversary exploitation, including for privilege escalation.\nThe \"ecs-task-definition-user-for-host-mode-check\" managed rule can identify Amazon Elastic Container Service (ECS) task definitions for containers with host networking mode and 'privileged' or 'user' container definitions, which may enable adversaries to break out of containers and gain access to the underlying host, increasing their access and privileges.\nAll of these are run on configuration changes. Coverage factor is partial for these rules, since they are specific to a subset of the available AWS services and will only protect against certain forms of identifiable exploitation, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1078",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "This control provides significant coverage for one of this technique's sub-techniques, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1078.004",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure multi-factor authentication (MFA) is enabled properly, which can provide protection against attempted misuse of cloud accounts: \"iam-user-mfa-enabled\", \"mfa-enabled-for-iam-console-access\", \"root-account-hardware-mfa-enabled\", and \"root-account-mfa-enabled\". All of these controls are run periodically.\nThe following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure that appropriate AWS Identity and Access Management (IAM) policies are in place to enforce fine-grained access policies and mitigate the impact of compromised valid accounts: \"iam-customer-policy-blocked-kms-actions\", \"iam-inline-policy-blocked-kms-actions\", \"iam-no-inline-policy-check\", \"iam-group-has-users-check\", \"iam-policy-blacklisted-check\", \"iam-policy-no-statements-with-admin-access\", \"iam-policy-no-statements-with-full-access\", \"iam-role-managed-policy-check\", \"iam-user-group-membership-check\", \"iam-user-no-policies-check\", and \"ec2-instance-profile-attached\" are run on configuration changes. \"iam-password-policy\", \"iam-policy-in-use\", \"iam-root-access-key-check\", \"iam-user-mfa-enabled\", \"iam-user-unused-credentials-check\", and \"mfa-enabled-for-iam-console-access\" are run periodically. The \"access-keys-rotated\" managed rule ensures that IAM access keys are rotated at an appropriate rate.\nGiven that these rules provide robust coverage for a variety of IAM configuration problems and most are evaluated on configuration changes, they result in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"
},
{
"techniqueID": "T1098",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "This control provides significant coverage for one of this technique's sub-techniques, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1098.001",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure multi-factor authentication (MFA) is enabled properly, which can provide protection against attempted manipulation of cloud accounts: \"iam-user-mfa-enabled\", \"mfa-enabled-for-iam-console-access\", \"root-account-hardware-mfa-enabled\", and \"root-account-mfa-enabled\". All of these controls are run periodically and provide partial coverage, since adversaries may be able to manipulate cloud credentials via other mechanisms, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1110",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "This control provides significant coverage for all of this technique's sub-techniques, resulting in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"
},
{
"techniqueID": "T1110.001",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure multi-factor authentication (MFA) is enabled properly, which can significantly impede brute force authentication attempts by requiring adversaries to provide a second form of authentication even if they succeed in brute forcing a password via one of these sub-techniques: \"iam-user-mfa-enabled\", \"mfa-enabled-for-iam-console-access\", \"root-account-hardware-mfa-enabled\", and \"root-account-mfa-enabled\".\nThe \"iam-password-policy\" managed rule can identify insufficient password requirements that should be fixed in order to make brute force authentication more difficult by increasing the complexity of user passwords and decreasing the amount of time before they are rotated, giving adversaries less time to brute force passwords and making it more time consuming and resource intensive to do so. This is especially important in the case of Password Cracking, since adversaries in possession of password hashes may be able to recover usable credentials more quickly and do so without generating detectable noise via invalid login attempts.\nAll of these controls are run periodically, but implemented policies are enforced continuously once set and coverage factor is significant, resulting in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"
},
{
"techniqueID": "T1110.002",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure multi-factor authentication (MFA) is enabled properly, which can significantly impede brute force authentication attempts by requiring adversaries to provide a second form of authentication even if they succeed in brute forcing a password via one of these sub-techniques: \"iam-user-mfa-enabled\", \"mfa-enabled-for-iam-console-access\", \"root-account-hardware-mfa-enabled\", and \"root-account-mfa-enabled\".\nThe \"iam-password-policy\" managed rule can identify insufficient password requirements that should be fixed in order to make brute force authentication more difficult by increasing the complexity of user passwords and decreasing the amount of time before they are rotated, giving adversaries less time to brute force passwords and making it more time consuming and resource intensive to do so. This is especially important in the case of Password Cracking, since adversaries in possession of password hashes may be able to recover usable credentials more quickly and do so without generating detectable noise via invalid login attempts.\nAll of these controls are run periodically, but implemented policies are enforced continuously once set and coverage factor is significant, resulting in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"
},
{
"techniqueID": "T1110.003",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure multi-factor authentication (MFA) is enabled properly, which can significantly impede brute force authentication attempts by requiring adversaries to provide a second form of authentication even if they succeed in brute forcing a password via one of these sub-techniques: \"iam-user-mfa-enabled\", \"mfa-enabled-for-iam-console-access\", \"root-account-hardware-mfa-enabled\", and \"root-account-mfa-enabled\".\nThe \"iam-password-policy\" managed rule can identify insufficient password requirements that should be fixed in order to make brute force authentication more difficult by increasing the complexity of user passwords and decreasing the amount of time before they are rotated, giving adversaries less time to brute force passwords and making it more time consuming and resource intensive to do so. This is especially important in the case of Password Cracking, since adversaries in possession of password hashes may be able to recover usable credentials more quickly and do so without generating detectable noise via invalid login attempts.\nAll of these controls are run periodically, but implemented policies are enforced continuously once set and coverage factor is significant, resulting in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"
},
{
"techniqueID": "T1110.004",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure multi-factor authentication (MFA) is enabled properly, which can significantly impede brute force authentication attempts by requiring adversaries to provide a second form of authentication even if they succeed in brute forcing a password via one of these sub-techniques: \"iam-user-mfa-enabled\", \"mfa-enabled-for-iam-console-access\", \"root-account-hardware-mfa-enabled\", and \"root-account-mfa-enabled\".\nThe \"iam-password-policy\" managed rule can identify insufficient password requirements that should be fixed in order to make brute force authentication more difficult by increasing the complexity of user passwords and decreasing the amount of time before they are rotated, giving adversaries less time to brute force passwords and making it more time consuming and resource intensive to do so. This is especially important in the case of Password Cracking, since adversaries in possession of password hashes may be able to recover usable credentials more quickly and do so without generating detectable noise via invalid login attempts.\nAll of these controls are run periodically, but implemented policies are enforced continuously once set and coverage factor is significant, resulting in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"
},
{
"techniqueID": "T1119",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure that storage volumes are encrypted, which may mitigate adversary attempts to automate collection within cloud environments: \"ec2-ebs-encryption-by-default\" which is run periodically and \"encrypted-volumes\" which is run on configuration changes.\nCoverage factor is minimal for these rules, since they are specific to EBS volumes and will only prevent certain forms of collection since adversaries with access to mounted volumes may be able to decrypt their contents, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1136",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "This control provides partial coverage for one of this technique's sub-techniques, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1136.003",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure multi-factor authentication (MFA) is enabled properly, which can provide significant protection against attempted manipulation of cloud accounts, including the creation of new ones: \"iam-user-mfa-enabled\", \"mfa-enabled-for-iam-console-access\", \"root-account-hardware-mfa-enabled\", and \"root-account-mfa-enabled\". All of these controls are run periodically and provide partial coverage, since adversaries may be able to create cloud credentials via other mechanisms, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1190",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure that applications intended for internal use cannot be accessed externally for exploitation: \"api-gw-endpoint-type-check\" can ensure that Amazon API Gateway APIs are private and can only be accessed from within VPCs, \"elasticsearch-in-vpc-only\" can ensure that Amazon ElasticSearch Service (Amazon ES) domains are in the same VPC and the domain endpoint is not public, \"lambda-function-public-access-prohibited\" can verify that AWS Lambda functions are not publicly available, and \"ec2-instance-no-public-ip\" can verify whether EC2 instances have public IP addresses.\nThe following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure that insecure applications are not installed and installed packages are kept updated, reducing the likelihood of adversary exploitation: the \"ec2-managedinstance-applications-blacklisted\" managed rule verifies that a pre-defined list of applications are not installed on specified managed instances. It can be used to identify the presence of vulnerable applications (prompting removal before they can be exploited) and/or to identify the presence of allowed packages below a minimum version (prompting updates before they can be exploited). The \"ec2-managedinstance-platform-check\" managed rule verifies that managed instances are running desired platform types, including using a desired version (as opposed to an out-of-date one). Both can reduce instances' attack surface for adversary exploitation. \"rds-automatic-minor-version-upgrade-enabled\" can verify that Amazon RDS is being patched, and \"elastic-beanstalk-managed-updates-enabled\" can verify that Elastic Beanstalk is being patched.\nCoverage factor is partial for these rules, since they are specific to a subset of the available AWS services that can be used to host public-facing applications and will only protect against certain forms of identifiable exploitation, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1203",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The \"ec2-managedinstance-applications-blacklisted\" managed rule verifies that a pre-defined list of applications are not installed on specified managed instances. It can be used to identify the presence of vulnerable applications (prompting removal before they can be exploited) and/or to identify the presence of allowed packages below a minimum version (prompting updates before they can be exploited). The \"ec2-managedinstance-platform-check\" managed rule verifies that managed instances are running desired platform types, including using a desired version (as opposed to an out-of-date one). Both can reduce instances' attack surface for adversary exploitation, including for client execution.\nAll of these are run on configuration changes. Coverage factor is partial for these rules, since they are specific to a subset of the available AWS services and will only protect against certain forms of identifiable exploitation, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1210",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The \"ec2-managedinstance-applications-blacklisted\" managed rule verifies that a pre-defined list of applications are not installed on specified managed instances. It can be used to identify the presence of vulnerable applications (prompting removal before they can be exploited) and/or to identify the presence of allowed packages below a minimum version (prompting updates before they can be exploited), both of which can reduce instances' attack surface for adversary exploitation, including via those applications' exposed remote services. The \"ec2-instance-no-public-ip\" managed rule identifies EC2 instances with public IP associations, which should be removed unless necessary to avoid exposing services publicly for adversary access.\nAll of these are run on configuration changes. Coverage factor is partial for these rules, since they are specific to a subset of the available AWS services and will only protect against certain forms of identifiable exploitation, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1211",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The \"ec2-managedinstance-applications-blacklisted\" managed rule verifies that a pre-defined list of applications are not installed on specified managed instances. It can be used to identify the presence of vulnerable applications (prompting removal before they can be exploited) and/or to identify the presence of allowed packages below a minimum version (prompting updates before they can be exploited). The \"ec2-managedinstance-platform-check\" managed rule verifies that managed instances are running desired platform types, including using a desired version (as opposed to an out-of-date one). Both can reduce instances' attack surface for adversary exploitation, including for defense evasion.\nAll of these are run on configuration changes. Coverage factor is partial for these rules, since they are specific to a subset of the available AWS services and will only protect against certain forms of identifiable exploitation, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1212",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The \"ec2-managedinstance-applications-blacklisted\" managed rule verifies that a pre-defined list of applications are not installed on specified managed instances. It can be used to identify the presence of vulnerable applications (prompting removal before they can be exploited) and/or to identify the presence of allowed packages below a minimum version (prompting updates before they can be exploited). The \"ec2-managedinstance-platform-check\" managed rule verifies that managed instances are running desired platform types, including using a desired version (as opposed to an out-of-date one).Both can reduce instances' attack surface for adversary exploitation, including for credential access.\nAll of these are run on configuration changes. Coverage factor is partial for these rules, since they are specific to a subset of the available AWS services and will only protect against certain forms of identifiable exploitation, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1204",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Detect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "This control provides significant coverage for one of this technique's sub-techniques, resulting in an overall score of Minimal."
}
],
"color": "#AEEEEE",
"score_num": 10,
"score_display": "Minimal",
"category": "Detect"
},
{
"techniqueID": "T1204.003",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Detect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify running instances that are not using AMIs within a specified allow list: \"approved-amis-by-id\" and \"approved-amis-by-tag\", both of which are run on configuration changes. They provide significant coverage, resulting in an overall score of Significant."
}
],
"color": "#00FFFF",
"score_num": 100,
"score_display": "Significant",
"category": "Detect"
},
{
"techniqueID": "T1485",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to prevent malicious write access to data within Amazon Simple Storage Service (S3) storage, which may include data destruction: \"s3-bucket-blacklisted-actions-prohibited\" checks whether bucket policies prohibit disallowed actions (including S3:DeleteObject) for principals from other AWS accounts, \"s3-bucket-default-lock-enabled\" checks whether a bucket that should be locked in write-once-read-many (WORM) mode is configured to prevent modification, and \"s3-bucket-public-write-prohibited\" checks whether a bucket is configured to allow public access and modification. All of these controls are run on configuration changes.\nThe following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure backups and redundancy are in place which can mitigate the effects of data destruction: \"aurora-mysql-backtracking-enabled\" for data in Aurora MySQL; \"db-instance-backup-enabled\" and \"rds-in-backup-plan\" for Amazon Relational Database Service (RDS) data; \"dynamodb-in-backup-plan\" and \"dynamodb-pitr-enabled\" for Amazon DynamoDB table contents; \"ebs-in-backup-plan\" for Elastic Block Store (EBS) volumes; \"efs-in-backup-plan\" for Amazon Elastic File System (EFS) file systems; \"elasticache-redis-cluster-automatic-backup-check\" for Amazon ElastiCache Redis cluster data; \"redshift-backup-enabled\" and \"redshift-cluster-maintenancesettings-check\" for Redshift; \"s3-bucket-replication-enabled\" and \"s3-bucket-versioning-enabled\" for S3 storage; and \"cloudfront-origin-failover-enabled\" for CloudFront.\nThe following AWS Config managed rules provide specific detections for configuration problems that should be fixed in order to prevent malicious deletion of specific data: \"elb-deletion-protection-enabled\" for Elastic Block Store (EBS) volumes, and \"rds-cluster-deletion-protection-enabled\" and \"rds-instance-deletion-protection-enabled\" for RDS data.\nCoverage factor is partial for these rules, since they are specific to a subset of the available AWS services and will only protect certain types of data against destruction, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1486",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to prevent malicious changes to data encryption within Amazon Simple Storage Service (S3) storage: \"s3-bucket-blacklisted-actions-prohibited\" checks whether bucket policies prohibit disallowed actions (including encryption configuration changes) for principals from other AWS accounts, \"s3-bucket-default-lock-enabled\" checks whether a bucket that should be locked in write-once-read-many (WORM) mode is configured to prevent modification, and \"s3-bucket-public-write-prohibited\" checks whether a bucket is configured to allow public access and modification. All of these controls are run on configuration changes.\nThe following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure backups and redundancy are in place which can mitigate the effects of malicious changes to data encryption: \"aurora-mysql-backtracking-enabled\" for data in Aurora MySQL; \"db-instance-backup-enabled\" and \"rds-in-backup-plan\" for Amazon Relational Database Service (RDS) data; \"dynamodb-in-backup-plan\" and \"dynamodb-pitr-enabled\" for Amazon DynamoDB table contents; \"ebs-in-backup-plan\" for Elastic Block Store (EBS) volumes; \"efs-in-backup-plan\" for Amazon Elastic File System (EFS) file systems; \"elasticache-redis-cluster-automatic-backup-check\" for Amazon ElastiCache Redis cluster data; \"redshift-backup-enabled\" and \"redshift-cluster-maintenancesettings-check\" for Redshift; \"s3-bucket-replication-enabled\" and \"s3-bucket-versioning-enabled\" for S3 storage; and \"cloudfront-origin-failover-enabled\" for CloudFront.\nCoverage factor is partial for these rules, since they are specific to a subset of the available AWS services and will only protect certain types of data against malicious encryption changes, resulting in an overall score of Partial."
}
],
"color": "#659D32",
"score_num": 50,
"score_display": "Partial",
"category": "Protect"
},
{
"techniqueID": "T1491",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "This control provides significant coverage for all of this technique's sub-techniques, resulting in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"
},
{
"techniqueID": "T1491.001",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to prevent malicious write access to data within Amazon Simple Storage Service (S3) storage, which may include internal and/or external defacement: \"s3-bucket-blacklisted-actions-prohibited\" checks whether bucket policies prohibit disallowed actions (including encryption configuration changes) for principals from other AWS accounts, \"s3-bucket-default-lock-enabled\" checks whether a bucket that should be locked in write-once-read-many (WORM) mode is configured to prevent modification, and \"s3-bucket-public-write-prohibited\" checks whether a bucket is configured to allow public access and modification. All of these controls are run on configuration changes.\nThe following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure backups and redundancy are in place which can mitigate the effects of malicious defacement: \"aurora-mysql-backtracking-enabled\" for data in Aurora MySQL; \"db-instance-backup-enabled\" and \"rds-in-backup-plan\" for Amazon Relational Database Service (RDS) data; \"dynamodb-in-backup-plan\" and \"dynamodb-pitr-enabled\" for Amazon DynamoDB table contents; \"ebs-in-backup-plan\" for Elastic Block Store (EBS) volumes; \"efs-in-backup-plan\" for Amazon Elastic File System (EFS) file systems; \"elasticache-redis-cluster-automatic-backup-check\" for Amazon ElastiCache Redis cluster data; \"redshift-backup-enabled\" and \"redshift-cluster-maintenancesettings-check\" for Redshift; \"s3-bucket-replication-enabled\" and \"s3-bucket-versioning-enabled\" for S3 storage; and \"cloudfront-origin-failover-enabled\" for CloudFront.\nCoverage factor is significant for these rules, since they cover a wide range of services used to host content for websites within AWS, resulting in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"
},
{
"techniqueID": "T1491.002",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to prevent malicious write access to data within Amazon Simple Storage Service (S3) storage, which may include internal and/or external defacement: \"s3-bucket-blacklisted-actions-prohibited\" checks whether bucket policies prohibit disallowed actions (including encryption configuration changes) for principals from other AWS accounts, \"s3-bucket-default-lock-enabled\" checks whether a bucket that should be locked in write-once-read-many (WORM) mode is configured to prevent modification, and \"s3-bucket-public-write-prohibited\" checks whether a bucket is configured to allow public access and modification. All of these controls are run on configuration changes.\nThe following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure backups and redundancy are in place which can mitigate the effects of malicious defacement: \"aurora-mysql-backtracking-enabled\" for data in Aurora MySQL; \"db-instance-backup-enabled\" and \"rds-in-backup-plan\" for Amazon Relational Database Service (RDS) data; \"dynamodb-in-backup-plan\" and \"dynamodb-pitr-enabled\" for Amazon DynamoDB table contents; \"ebs-in-backup-plan\" for Elastic Block Store (EBS) volumes; \"efs-in-backup-plan\" for Amazon Elastic File System (EFS) file systems; \"elasticache-redis-cluster-automatic-backup-check\" for Amazon ElastiCache Redis cluster data; \"redshift-backup-enabled\" and \"redshift-cluster-maintenancesettings-check\" for Redshift; \"s3-bucket-replication-enabled\" and \"s3-bucket-versioning-enabled\" for S3 storage; and \"cloudfront-origin-failover-enabled\" for CloudFront.\nCoverage factor is significant for these rules, since they cover a wide range of services used to host content for websites within AWS, resulting in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"
},
{
"techniqueID": "T1496",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Detect"
},
{
"name": "value",
"value": "Partial"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure alarms exist for spikes in resource utilization, which help to identify malicious use of resources within a cloud environment: \"cloudwatch-alarm-action-check\", \"cloudwatch-alarm-resource-check\", \"cloudwatch-alarm-settings-check\", \"desired-instance-tenancy\", \"desired-instance-type\", \"dynamodb-autoscaling-enabled\", \"dynamodb-throughput-limit-check\", \"ec2-instance-detailed-monitoring-enabled\", and \"rds-enhanced-monitoring-enabled\".\nCoverage factor is partial for these rules, since they are specific to a subset of the available AWS services and will only detect resource hijacking that results in a change in utilization that is significant enough to trigger alarms, resulting in an overall score of Partial."
}
],
"color": "#5F9F9F",
"score_num": 50,
"score_display": "Partial",
"category": "Detect"
},
{
"techniqueID": "T1498",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "This control provides minimal coverage for this technique's sub-techniques as well as its procedures, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1498.001",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "The \"elb-cross-zone-load-balancing-enabled\" managed rule can verify that load balancing is properly configured, which can mitigate adversaries' ability to perform Denial of Service (DoS) attacks and impact resource availability. \"cloudfront-origin-failover-enabled\" can verify that failover policies are in place to increase CloudFront content availability.\nCoverage factor is minimal for these rules, since they are specific to a subset of the available AWS services, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1498.002",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "The \"elb-cross-zone-load-balancing-enabled\" managed rule can verify that load balancing is properly configured, which can mitigate adversaries' ability to perform Denial of Service (DoS) attacks and impact resource availability. \"cloudfront-origin-failover-enabled\" can verify that failover policies are in place to increase CloudFront content availability.\nCoverage factor is minimal for these rules, since they are specific to a subset of the available AWS services, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1499",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "This control provides minimal coverage for this technique's sub-techniques as well as its procedures, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1499.001",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "The \"elb-cross-zone-load-balancing-enabled\" managed rule can verify that load balancing is properly configured, which can mitigate adversaries' ability to perform Denial of Service (DoS) attacks and impact resource availability. \"cloudfront-origin-failover-enabled\" can verify that failover policies are in place to increase CloudFront content availability.\nCoverage factor is minimal for these rules, since they are specific to a subset of the available AWS services, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1499.002",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "The \"elb-cross-zone-load-balancing-enabled\" managed rule can verify that load balancing is properly configured, which can mitigate adversaries' ability to perform Denial of Service (DoS) attacks and impact resource availability. \"cloudfront-origin-failover-enabled\" can verify that failover policies are in place to increase CloudFront content availability.\nCoverage factor is minimal for these rules, since they are specific to a subset of the available AWS services, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1499.003",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "The \"elb-cross-zone-load-balancing-enabled\" managed rule can verify that load balancing is properly configured, which can mitigate adversaries' ability to perform Denial of Service (DoS) attacks and impact resource availability. \"cloudfront-origin-failover-enabled\" can verify that failover policies are in place to increase CloudFront content availability.\nCoverage factor is minimal for these rules, since they are specific to a subset of the available AWS services, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1499.004",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "The \"elb-cross-zone-load-balancing-enabled\" managed rule can verify that load balancing is properly configured, which can mitigate adversaries' ability to perform Denial of Service (DoS) attacks and impact resource availability. \"cloudfront-origin-failover-enabled\" can verify that failover policies are in place to increase CloudFront content availability.\nCoverage factor is minimal for these rules, since they are specific to a subset of the available AWS services, resulting in an overall score of Minimal."
}
],
"color": "#9CBA7F",
"score_num": 10,
"score_display": "Minimal",
"category": "Protect"
},
{
"techniqueID": "T1525",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Detect"
},
{
"name": "value",
"value": "Minimal"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify running instances that are not using AMIs within a specified allow list: \"approved-amis-by-id\" and \"approved-amis-by-tag\", both of which are run on configuration changes. This does not provide detection of the image implanting itself, but does provide detection for any subsequent use of images that are implanted and not present within the allow list, resulting in a score of Minimal."
}
],
"color": "#AEEEEE",
"score_num": 10,
"score_display": "Minimal",
"category": "Detect"
},
{
"techniqueID": "T1530",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "The following AWS Config managed rules can identify configuration problems that should be fixed in order to prevent malicious access of data within Amazon Simple Storage Service (S3) storage: \"s3-account-level-public-access-blocks\", \"s3-bucket-level-public-access-prohibited\", \"s3-bucket-public-read-prohibited\", \"s3-bucket-policy-not-more-permissive\", \"cloudfront-origin-access-identity-enabled\", and \"cloudfront-default-root-object-configured\" identify objects that are publicly available or subject to overly permissive access policies; \"s3-bucket-blacklisted-actions-prohibited\" checks whether bucket policies prohibit disallowed actions for principals from other AWS accounts; and \"s3-bucket-policy-grantee-check\" checks whether bucket policies appropriately control which AWS principals, federated users, service principals, IP addresses, and VPCs have access. All of these controls are run on configuration changes.\nThe following AWS Config managed rules can identify configuration problems that should be fixed in order to prevent malicious access of data from other AWS services: \"dms-replication-not-public\" for AWS Database Migration Service; \"emr-master-no-public-ip\" for Amazon Elastic MapReduce (EMR); \"rds-cluster-iam-authentication-enabled\", \"rds-instance-iam-authentication-enabled\", \"rds-instance-public-access-check\" and \"rds-snapshots-public-prohibited\" for Amazon Relational Database Service; \"redshift-cluster-public-access-check\" for Amazon Redshift; and \"sagemaker-notebook-no-direct-internet-access\" for SageMaker.\nThe following AWS Config managed rules can identify configuration problems that should be fixed in order to ensure that cloud storage data are encrypted to prevent malicious access: \"dax-encryption-enabled\", \"dynamodb-table-encrypted-kms\", and \"dynamodb-table-encryption-enabled\" for Amazon DynamoDB table contents; \"efs-encrypted-check\" for Amazon Elastic File System (EFS) file systems; \"elasticsearch-encrypted-at-rest\" for Elasticsearch Service (ES) domains; \"rds-snapshot-encrypted\" and \"rds-storage-encrypted\" for Amazon Relational Database Service; \"s3-bucket-server-side-encryption-enabled\" and \"s3-default-encryption-kms\" for S3 storage; \"sns-encrypted-kms\" for Amazon Simple Notification Service (SNS); \"redshift-cluster-configuration-check\" and \"redshift-cluster-kms-enabled\" for Redshift clusters; \"sagemaker-endpoint-configuration-kms-key-configured\" and \"sagemaker-notebook-instance-kms-key-configured\" for SageMaker.\nThese rules provide a wide range of coverage for many AWS services, especially those most significant to procedures for this technique, resulting in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"
},
{
"techniqueID": "T1538",
"enabled": true,
"showSubtechniques": false,
"metadata": [
{
"name": "category",
"value": "Protect"
},
{
"name": "value",
"value": "Significant"
},
{
"name": "comment",
"value": "The \"mfa-enabled-for-iam-console-access\" managed rule checks whether multi-factor authentication is enabled for all AWS IAM users that use a console password, protecting against misuse of those accounts' dashboard access. It is run periodically, and provides significant coverage, resulting in an overall score of Significant."
}
],
"color": "#7FFF00",
"score_num": 100,
"score_display": "Significant",
"category": "Protect"