Framework/Configurations/ARMChecker/ARMControls.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
{
  "resourceControlSets": [
    {
      "featureName": "TrafficManager",
      "supportedResourceTypes": [ "Microsoft.Network/trafficManagerProfiles" ],
      "controls": [
        {
          "id": "TrafficManager120",
          "controlId": "Azure_TrafficManager_DP_Enable_HTTPS",
          "isEnabled": true,
          "description": "Traffic Manager profile should use HTTPS protocol for endpoint monitoring",
          "rationale": "",
          "recommendation": "",
          "severity": "High",
          "jsonPath": [ "$.properties.monitorConfig.protocol" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "HTTPS",
            "isCaseSensitive": false
          }
        }
      ]
    },
    {
      "featureName": "ServiceFabric",
      "supportedResourceTypes": [ "Microsoft.ServiceFabric/clusters" ],
      "controls": [
        {
          "id": "ServiceFabric300",
          "controlId": "Azure_ServiceFabric_SI_Set_Auto_Update_Cluster",
          "isEnabled": true,
          "description": "Upgrade mode should be set to automatic for cluster",
          "rationale": "Clusters with unsupported fabric version can become targets for compromise from various malware/trojan attacks that exploit known vulnerabilities in software.",
          "recommendation": "You can set your cluster to receive automatic fabric upgrades as they are released by Microsoft, for details please refer: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-upgrade",
          "severity": "Medium",
          "jsonPath": [ "$.properties.upgradeMode" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "Automatic",
            "isCaseSensitive": false
          }
        },
        {
          "id": "ServiceFabric220",
          "controlId": "Azure_ServiceFabric_AuthN_Client_AuthN_AAD_Only",
          "isEnabled": true,
          "description": "Client authentication must be performed only via Azure Active Directory",
          "rationale": "Using the native enterprise directory for authentication ensures that there is a built-in high level of assurance in the user identity established for subsequent access control. All Enterprise subscriptions are automatically associated with their enterprise directory (xxx.onmicrosoft.com) and users in the native directory are trusted for authentication to enterprise subscriptions.",
          "recommendation": "A Service Fabric cluster offers several entry points to its management functionality, including the web-based Service Fabric Explorer, Visual Studio and PowerShell. Access to the cluster must be controlled using AAD. Refer: https://docs.microsoft.com/en-in/azure/service-fabric/service-fabric-cluster-creation-setup-aad",
          "severity": "High",
          "jsonPath": [ "$.properties.azureActiveDirectory.tenantId" ],
          "matchType": "StringWhitespace",
          "data": {
            "value": false
          }
        },
        {
          "id": "ServiceFabric220",
          "controlId": "Azure_ServiceFabric_AuthN_Client_AuthN_AAD_Only",
          "isEnabled": true,
          "description": "Client authentication must be performed only via Azure Active Directory",
          "rationale": "Using the native enterprise directory for authentication ensures that there is a built-in high level of assurance in the user identity established for subsequent access control. All Enterprise subscriptions are automatically associated with their enterprise directory (xxx.onmicrosoft.com) and users in the native directory are trusted for authentication to enterprise subscriptions.",
          "recommendation": "A Service Fabric cluster offers several entry points to its management functionality, including the web-based Service Fabric Explorer, Visual Studio and PowerShell. Access to the cluster must be controlled using AAD. Refer: https://docs.microsoft.com/en-in/azure/service-fabric/service-fabric-cluster-creation-setup-aad",
          "severity": "High",
          "jsonPath": [ "$.properties.azureActiveDirectory.clusterApplication" ],
          "matchType": "StringWhitespace",
          "data": {
            "value": false
          }
        },
        {
          "id": "ServiceFabric220",
          "controlId": "Azure_ServiceFabric_AuthN_Client_AuthN_AAD_Only",
          "isEnabled": true,
          "description": "Client authentication must be performed only via Azure Active Directory",
          "rationale": "Using the native enterprise directory for authentication ensures that there is a built-in high level of assurance in the user identity established for subsequent access control. All Enterprise subscriptions are automatically associated with their enterprise directory (xxx.onmicrosoft.com) and users in the native directory are trusted for authentication to enterprise subscriptions.",
          "recommendation": "A Service Fabric cluster offers several entry points to its management functionality, including the web-based Service Fabric Explorer, Visual Studio and PowerShell. Access to the cluster must be controlled using AAD. Refer: https://docs.microsoft.com/en-in/azure/service-fabric/service-fabric-cluster-creation-setup-aad",
          "severity": "High",
          "jsonPath": [ "$.properties.azureActiveDirectory.clientApplication" ],
          "matchType": "StringWhitespace",
          "data": {
            "value": false
          }
        },
        {
          "id": "ServiceFabric230",
          "controlId": "Azure_ServiceFabric_DP_Set_Property_ClusterProtectionLevel",
          "isEnabled": true,
          "description": "The ClusterProtectionLevel property must be set to EncryptAndSign",
          "rationale": "With cluster protection level set to 'EncryptAndSign', all the node-to-node messages are encrypted and digitally signed. This protects the intra-cluster communication from eavesdropping/tampering/man-in-the-middle attacks on the network.",
          "recommendation": "Service Fabric provides three levels of protection (None, Sign and EncryptAndSign) for node to node communication using cluster primary certificate. The protection level can be specified using property 'ClusterProtectionLevel' inside Service Fabric ARM template. The value of 'ClusterProtectionLevel' must be set to 'EncryptAndSign' to ensure that all the node-to-node messages are encrypted and digitally signed. Configure 'ClusterProtectionLevel' using ARM template as follows: ARM Template --> Resources --> Select resource type 'Microsoft.ServiceFabric/clusters' --> 'fabricSettings' --> Add 'ClusterProtectionLevel' property with value 'EncryptAndSign'.",
          "severity": "High",
          "jsonPath": [ "$.properties.fabricSettings[0].name" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "Security",
            "isCaseSensitive": false
          }
        },
        {
          "id": "ServiceFabric230",
          "controlId": "Azure_ServiceFabric_DP_Set_Property_ClusterProtectionLevel",
          "isEnabled": true,
          "description": "The ClusterProtectionLevel property must be set to EncryptAndSign",
          "rationale": "With cluster protection level set to 'EncryptAndSign', all the node-to-node messages are encrypted and digitally signed. This protects the intra-cluster communication from eavesdropping/tampering/man-in-the-middle attacks on the network.",
          "recommendation": "Service Fabric provides three levels of protection (None, Sign and EncryptAndSign) for node to node communication using cluster primary certificate. The protection level can be specified using property 'ClusterProtectionLevel' inside Service Fabric ARM template. The value of 'ClusterProtectionLevel' must be set to 'EncryptAndSign' to ensure that all the node-to-node messages are encrypted and digitally signed. Configure 'ClusterProtectionLevel' using ARM template as follows: ARM Template --> Resources --> Select resource type 'Microsoft.ServiceFabric/clusters' --> 'fabricSettings' --> Add 'ClusterProtectionLevel' property with value 'EncryptAndSign'.",
          "severity": "High",
          "jsonPath": [ "$.properties.fabricSettings[0].parameters[0].name" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "ClusterProtectionLevel",
            "isCaseSensitive": false
          }
        },
        {
          "id": "ServiceFabric230",
          "controlId": "Azure_ServiceFabric_DP_Set_Property_ClusterProtectionLevel",
          "isEnabled": true,
          "description": "The ClusterProtectionLevel property must be set to EncryptAndSign",
          "rationale": "With cluster protection level set to 'EncryptAndSign', all the node-to-node messages are encrypted and digitally signed. This protects the intra-cluster communication from eavesdropping/tampering/man-in-the-middle attacks on the network.",
          "recommendation": "Service Fabric provides three levels of protection (None, Sign and EncryptAndSign) for node to node communication using cluster primary certificate. The protection level can be specified using property 'ClusterProtectionLevel' inside Service Fabric ARM template. The value of 'ClusterProtectionLevel' must be set to 'EncryptAndSign' to ensure that all the node-to-node messages are encrypted and digitally signed. Configure 'ClusterProtectionLevel' using ARM template as follows: ARM Template --> Resources --> Select resource type 'Microsoft.ServiceFabric/clusters' --> 'fabricSettings' --> Add 'ClusterProtectionLevel' property with value 'EncryptAndSign'.",
          "severity": "High",
          "jsonPath": [ "$.properties.fabricSettings[0].parameters[0].value" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "EncryptAndSign",
            "isCaseSensitive": false
          }
        }
      ]
    },
    {
      "featureName": "DataLakeStore",
      "supportedResourceTypes": [ "Microsoft.DataLakeStore/accounts" ],
      "controls": [
        {
          "id": "DataLakeStore180",
          "controlId": "Azure_DataLakeStore_DP_Encrypt_At_Rest",
          "isEnabled": true,
          "description": "Sensitive data must be encrypted at rest",
          "rationale": "Using this feature ensures that sensitive data is stored encrypted at rest. This minimizes the risk of data loss from physical theft and also helps meet regulatory compliance requirements.",
          "recommendation": "Ensure that encryption is not disabled when creating a new Data Lake Store. Refer: https://docs.microsoft.com/en-us/azure/data-lake-store/data-lake-store-security-overview#data-protection. Encryption cannot be enabled after the fact for Data Lake Store.",
          "severity": "High",
          "jsonPath": [ "$.properties.encryptionState" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "Enabled",
            "isCaseSensitive": false
          }
        }
      ]
    },
    {
      "featureName": "CDN",
      "supportedResourceTypes": [ "Microsoft.Cdn/profiles" ],
      "controls": [],
      "NestedResourcesControlSet": [
        {
 
          "featureName": "CDN",
          "supportedResourceTypes": [ "endpoints" ],
          "controls": [
            {
              "id": "CDN140",
              "controlId": "Azure_CDN_DP_Enable_Https",
              "isEnabled": true,
              "description": "CDN endpoints must use HTTPS protocol while providing data to the client browser/machine or while fetching data from the origin server",
              "rationale": "Use of HTTPS ensures server/service authentication and protects data in transit from network layer man-in-the-middle, eavesdropping, session-hijacking attacks.",
              "recommendation": "To enable HTTPS protocol: Go to Azure Portal --> your CDN Profile --> your CDN Endpoint --> Origin --> Select HTTPS --> Save. Else implement through PowerShell as follows: `$ce= Get-AzCdnEndpoint -EndpointName <EndpointName> ProfileName '<CDNprofile>' -ResourceGroupName '<RGName>'; `$ce.IsHttpAllowed =`$false; `$ce.IsHttpsAllowed =`$true; Set-AzCdnEndpoint -CdnEndpoint `$ce",
              "severity": "High",
              "jsonPath": [ "$.properties.isHttpsAllowed" ],
              "matchType": "Boolean",
              "data": {
                "value": true
              }
            }
          ]
        }
      ]
 
    },
    {
      "featureName": "RedisCache",
      "supportedResourceTypes": [ "Microsoft.Cache/Redis" ],
      "controls": [
        {
          "id": "RedisCache150",
          "controlId": "Azure_RedisCache_DP_Use_SSL_Port",
          "isEnabled": true,
          "description": "Non-SSL port must not be enabled",
          "rationale": "Use of HTTPS ensures server/service authentication and protects data in transit from network layer man-in-the-middle, eavesdropping, session-hijacking attacks.",
          "recommendation": "To disable Non-SSL port for Redis Cache, run command : Set-AzRedisCache -ResourceGroupName <String> -Name <String> -EnableNonSslPort `$false",
          "severity": "High",
          "jsonPath": [ "$.properties.enableNonSslPort" ],
          "matchType": "Boolean",
          "data": {
            "value": false
          }
        }
      ]
    },
    {
      "featureName": "CosmosDb",
      "supportedResourceTypes": [ "Microsoft.DocumentDB/databaseAccounts" ],
      "controls": [
        {
          "id": "CosmosDb110",
          "controlId": "Azure_CosmosDB_AuthZ_Enable_Firewall",
          "isEnabled": true,
          "description": "Cosmos DB firewall should be enabled",
          "rationale": "Using the firewall feature ensures that access to the data or the service is restricted to a specific set/group of clients. While this may not be feasible in all scenarios, when it can be used, it provides an extra layer of access control protection for critical assets.",
          "recommendation": "Azure Portal --> Resource --> Firewall. Turn 'ON' - 'Selected Networks' and provide required IP addresses and/or ranges in the IP tab and save. Note: In case the IP range is indeterminate (for instance, if the client is a PaaS endpoint), you may need to attest this control.",
          "severity": "High",
          "jsonPath": [ "$.properties.ipRangeFilter" ],
          "matchType": "StringWhitespace",
          "data": { "value": false }
        },
        {
          "id": "CosmosDb120",
          "controlId": "Azure_CosmosDB_AuthZ_Verify_IP_Range",
          "isEnabled": true,
          "description": "Configure only the required IP addresses on Cosmos DB firewall",
          "rationale": "",
          "recommendation": "Do not use high ranges like 0.0.0.0/0, 0.0.0.0/1, 128.0.0.0/1, etc. Maximum IPs in a range should be less than 256 and total IPs including all ranges should be less than 2048. To modify - Azure Portal --> Resource --> Firewall. Turn 'ON' - 'Enable IP Access Control' and add/or remove IP addresses and/or ranges and save. Note: In case the IP range is indeterminate (for instance, if the client is a PaaS endpoint), you may need to attest this control.",
          "severity": "High",
          "jsonPath": [ "$.properties.ipRangeFilter" ],
          "matchType": "VerifiableSingleToken",
          "data": {}
        },
        {
          "id": "CosmosDb130",
          "controlId": "Azure_CosmosDB_Config_Default_Consistency",
          "isEnabled": true,
          "description": "Do not use 'Eventual' consistency",
          "rationale": "",
          "recommendation": "Using Eventual consistency might cause undesired effects due to its ordering guarantees. To modify - Azure Portal --> Resource --> Default consistency. Select 'Session' and save. Refer: https://docs.microsoft.com/en-in/azure/cosmos-db/consistency-levels",
          "severity": "High",
          "jsonPath": [ "$.properties.consistencyPolicy.defaultConsistencyLevel" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "NotAllow",
            "value": "Eventual",
            "isCaseSensitive": false
          }
        },
        {
          "id": "CosmosDb140",
          "controlId": "Azure_CosmosDB_Deploy_Use_Replication",
          "isEnabled": true,
          "description": "Use global replication",
          "rationale": "",
          "recommendation": "Replication ensures the continuity and rapid recovery during disasters. To add - Azure Portal --> Resource -> Replicate data globally. Select a secondary read region and save. Refer: https://docs.microsoft.com/en-in/azure/cosmos-db/distribute-data-globally",
          "severity": "Medium",
          "jsonPath": [ "$.properties.locations" ],
          "matchType": "ItemCount",
          "data": {
            "type": "GreaterThan",
            "value": 1
          }
        },
        {
          "id": "CosmosDb150",
          "controlId": "Azure_CosmosDB_Deploy_Use_Automatic_Failover",
          "isEnabled": true,
          "description": "Use automatic failover",
          "rationale": "",
          "recommendation": "Automatic failover ensures the continuity and auto recovery during disasters. To configure, you must have at least 1 secondary replica enabled. To enabled replica - Azure Portal --> Resource -> Replicate data globally. Select a secondary read region and save. To set automatic failover - Azure Portal --> Resource -> Replicate data globally --> Automatic Failover. Turn 'ON' - 'Enable Automatic Failover', set the priorities and click 'OK'.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.enableAutomaticFailover" ],
          "matchType": "Boolean",
          "data": { "value": true }
        }
      ]
    },
    {
      "featureName": "SqlServer",
      "supportedResourceTypes": [ "Microsoft.Sql/servers", "Microsoft.Sql/servers/databases", "Microsoft.Sql/servers/databases/transparentDataEncryption", "Microsoft.Sql/servers/databases/auditingSettings", "Microsoft.Sql/servers/auditingSettings", "Microsoft.Sql/servers/administrators", "Microsoft.Sql/servers/securityAlertPolicies", "Microsoft.Sql/servers/firewallrules" ],
      "controls": [
        {
          "id": "SQLDatabase120",
          "apiVersions": [ "2014-04-01-preview" ],
          "controlId": "Azure_SQLDatabase_AuthZ_Use_AAD_Admin",
          "isEnabled": true,
          "description": "Enable Azure AD admin for the SQL Database",
          "rationale": "",
          "recommendation": "",
          "severity": "High",
          "jsonPath": [ "$.properties.administratorType" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "ActiveDirectory",
            "isCaseSensitive": false
          }
        },
        {
          "id": "SQLDatabase160",
          "apiVersions": [ "2015-05-01-preview" ],
          "controlId": "Azure_SQLDatabase_Audit_Enable_Threat_Detection_Server",
          "isEnabled": true,
          "description": "Enable SQL Server threat detection with email admins option. Do not exclude any detection types",
          "rationale": "",
          "recommendation": "",
          "severity": "High",
          "jsonPath": [ "$.properties.state" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "Enabled",
            "isCaseSensitive": false
          }
        },
        {
          "id": "SQLDatabase160",
          "apiVersions": [ "2015-05-01-preview" ],
          "controlId": "Azure_SQLDatabase_Audit_Enable_Threat_Detection_Server",
          "isEnabled": true,
          "description": "Enable SQL Server threat detection with email admins option. Do not exclude any detection types",
          "rationale": "",
          "recommendation": "",
          "severity": "High",
          "jsonPath": [ "$.properties.emailAccountAdmins" ],
          "matchType": "Boolean",
          "data": { "value": true }
        },
        {
          "id": "SQLDatabase160",
          "apiVersions": [ "2015-05-01-preview" ],
          "controlId": "Azure_SQLDatabase_Audit_Enable_Threat_Detection_Server",
          "isEnabled": true,
          "description": "Enable SQL Server threat detection with email admins option. Do not exclude any detection types",
          "rationale": "",
          "recommendation": "",
          "severity": "High",
          "jsonPath": [ "$.properties.emailAddresses" ],
          "matchType": "StringWhitespace",
          "data": {
            "value": false
          }
        },
        {
          "id": "SQLDatabase160",
          "apiVersions": [ "2015-05-01-preview" ],
          "controlId": "Azure_SQLDatabase_Audit_Enable_Threat_Detection_Server",
          "isEnabled": true,
          "description": "Enable SQL Server threat detection with email admins option. Do not exclude any detection types",
          "rationale": "",
          "recommendation": "",
          "severity": "High",
          "jsonPath": [ "$.properties.disabledAlerts" ],
          "matchType": "StringWhitespace",
          "data": {
            "value": true
          }
        },
        {
          "id": "SQLDatabase150",
          "apiVersions": [ "2014-04-01-preview" ],
          "controlId": "Azure_SQLDatabase_DP_Enable_TDE",
          "isEnabled": true,
          "description": "Transparent data encryption (TDE) must be enabled",
          "rationale": "",
          "recommendation": "",
          "severity": "High",
          "jsonPath": [ "$.properties.status" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "Enabled",
            "isCaseSensitive": false
          }
        }
 
      ]
    },
    {
      "featureName": "Storage",
      "supportedResourceTypes": [ "Microsoft.Storage/storageAccounts" ],
      "controls": [
        {
          "id": "AzureStorage160",
          "controlId": "Azure_Storage_DP_Encrypt_In_Transit",
          "isEnabled": true,
          "description": "HTTPS protocol must be used for accessing Storage Account resources",
          "rationale": "Use of HTTPS ensures server/service authentication and protects data in transit from network layer man-in-the-middle, eavesdropping, session-hijacking attacks. When enabling HTTPS one must remember to simultaneously disable access over plain HTTP else data can still be subject to compromise over clear text connections.",
          "recommendation": "Run command 'Set-AzStorageAccount -ResourceGroupName <RGName> -Name <StorageAccountName> -EnableHttpsTrafficOnly `$true'. Run 'Get-Help Set-AzStorageAccount -full' for more help.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.supportsHttpsTrafficOnly" ],
          "matchType": "Boolean",
          "data": { "value": true }
        }
      ]
    },
    {
      "featureName": "AppService",
      "supportedResourceTypes": [ "Microsoft.Web/sites", "Microsoft.Web/serverfarms", "Microsoft.Web/sites/config" ],
      "controls": [
        {
          "id": "AppService270",
          "apiVersions": [ "2016-09-01" ],
          "controlId": "Azure_AppService_BCDR_Use_Multiple_Instances",
          "isEnabled": true,
          "description": "App Service must be deployed on a minimum of two instances to ensure availability",
          "rationale": "App Service deployed on multiple instances ensures that the App Service remains available even if an instance is down.",
          "recommendation": "Run command 'Set-AzAppServicePlan -Name '<AppServicePlanName>' -ResourceGroupName '<RGName>' -NumberofWorkers '<NumberofInstances>''. Run 'Get-Help Set-AzAppServicePlan -full' for more help.",
          "severity": "Medium",
          "jsonPath": [ "$.sku.capacity" ],
          "matchType": "IntegerValue",
          "data": {
            "type": "GreaterThan",
            "value": 1
          }
        },
        {
          "id": "AppService210",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_Config_Disable_Remote_Debugging",
          "isEnabled": true,
          "description": "Remote debugging must be turned off for App Service",
          "rationale": "Remote debugging requires inbound ports to be opened on App Service. These ports become easy targets for compromise from various internet based attacks.",
          "recommendation": "Go to Azure Portal --> your App Service --> Settings --> Application Settings --> Remote Debugging --> Click on 'OFF'.",
          "severity": "High",
          "jsonPath": [ "$.properties.siteConfig.remoteDebuggingEnabled", "$.properties.remoteDebuggingEnabled" ],
          "matchType": "Boolean",
          "data": { "value": false }
        },
        {
          "id": "AppService220",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_Config_Disable_Web_Sockets",
          "isEnabled": true,
          "description": "Web Sockets should be disabled for App Service",
          "rationale": "",
          "recommendation": "Run command 'Set-AzWebApp -Name '<WebAppName>' -ResourceGroupName '<RGName>' -WebSocketsEnabled `$false'. Run 'Get-Help Set-AzWebApp -full' for more help. Refer: https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/HTML5_Security_Cheat_Sheet.md#websockets",
          "severity": "High",
          "jsonPath": [ "$.properties.siteConfig.webSocketsEnabled", "$.properties.webSocketsEnabled" ],
          "matchType": "Boolean",
          "data": { "value": false }
        },
        {
          "id": "AppService230",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_BCDR_Use_AlwaysOn",
          "isEnabled": true,
          "description": "'Always On' should be configured for App Service",
          "rationale": "By default, websites are unloaded if they have been idle for some period of time. However, this may not be ideal for 'high availability' requirements. Configuring 'Always On' can help prevent app services from getting timed out.",
          "recommendation": "Go to Azure Portal --> your App Service --> Settings --> Application Settings --> Always On --> Click on 'ON'.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.siteConfig.alwaysOn", "$.properties.alwaysOn" ],
          "matchType": "Boolean",
          "data": { "value": true }
        },
        {
          "id": "AppService240",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_Deploy_Use_Latest_Version",
          "isEnabled": true,
          "description": "The latest version of .NET framework version should be used for App Service",
          "rationale": "",
          "recommendation": "Run command 'Set-AzWebApp -Name '<WebAppName>' -ResourceGroupName '<RGName>' -NetFrameworkVersion 'v4.7''. Run 'Get-Help Set-AzWebApp -full' for more help.",
          "severity": "Low",
          "jsonPath": [ "$.properties.siteConfig.netFrameworkVersion", "$.properties.netFrameworkVersion" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "v4.7",
            "isCaseSensitive": false
          }
        },
        {
          "id": "AppService290",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_Audit_Enable_Logging_and_Monitoring",
          "isEnabled": true,
          "description": "Auditing and Monitoring must be enabled for App Service",
          "rationale": "Auditing enables log collection of important system events pertinent to security. Regular monitoring of audit logs can help to detect any suspicious and malicious activity early and respond in a timely manner.",
          "recommendation": "Run command 'Set-AzWebApp -Name '<WebAppName>' -ResourceGroupName '<RGName>' -DetailedErrorLoggingEnabled `$true -HttpLoggingEnabled `$true -RequestTracingEnabled `$true'. Run 'Get-Help Set-AzWebApp -full' for more help.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.siteConfig.requestTracingEnabled", "$.properties.requestTracingEnabled" ],
          "matchType": "Boolean",
          "data": { "value": true }
        },
        {
          "id": "AppService290",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_Audit_Enable_Logging_and_Monitoring",
          "isEnabled": true,
          "description": "Auditing and Monitoring must be enabled for App Service",
          "rationale": "Auditing enables log collection of important system events pertinent to security. Regular monitoring of audit logs can help to detect any suspicious and malicious activity early and respond in a timely manner.",
          "recommendation": "Run command 'Set-AzWebApp -Name '<WebAppName>' -ResourceGroupName '<RGName>' -DetailedErrorLoggingEnabled `$true -HttpLoggingEnabled `$true -RequestTracingEnabled `$true'. Run 'Get-Help Set-AzWebApp -full' for more help.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.siteConfig.httpLoggingEnabled", "$.properties.httpLoggingEnabled" ],
          "matchType": "Boolean",
          "data": { "value": true }
        },
        {
          "id": "AppService290",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_Audit_Enable_Logging_and_Monitoring",
          "isEnabled": true,
          "description": "Auditing and Monitoring must be enabled for App Service",
          "rationale": "Auditing enables log collection of important system events pertinent to security. Regular monitoring of audit logs can help to detect any suspicious and malicious activity early and respond in a timely manner.",
          "recommendation": "Run command 'Set-AzWebApp -Name '<WebAppName>' -ResourceGroupName '<RGName>' -DetailedErrorLoggingEnabled `$true -HttpLoggingEnabled `$true -RequestTracingEnabled `$true'. Run 'Get-Help Set-AzWebApp -full' for more help.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.siteConfig.detailedErrorLoggingEnabled", "$.properties.detailedErrorLoggingEnabled" ],
          "matchType": "Boolean",
          "data": { "value": true }
        },
        {
          "id": "AppService310",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_DP_Dont_Allow_HTTP_Access",
          "isEnabled": true,
          "description": "App Service must only be accessible over HTTPS",
          "rationale": "Use of HTTPS ensures server/service authentication and protects data in transit from network layer eavesdropping attacks.",
          "recommendation": "",
          "severity": "High",
          "jsonPath": [ "$.properties.httpsOnly" ],
          "matchType": "Boolean",
          "data": {
            "value": true
          }
        },
        {
          "id": "AppService130",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_AuthN_Use_AAD_for_Client_AuthN",
          "isEnabled": true,
          "description": "App Service must authenticate users using Azure Active Directory backed credentials",
          "rationale": "Using the native enterprise directory for authentication ensures that there is a built-in high level of assurance in the user identity established for subsequent access control.All Enterprise subscriptions are automatically associated with their enterprise directory (xxx.onmicrosoft.com) and users in the native directory are trusted for authentication to enterprise subscriptions.",
          "recommendation": "",
          "severity": "High",
          "jsonPath": [ "$.properties.siteConfig.siteAuthEnabled", "$.properties.siteAuthEnabled" ],
          "matchType": "Boolean",
          "data": {
            "value": true
          }
        },
        {
          "id": "AppService130",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_AuthN_Use_AAD_for_Client_AuthN",
          "isEnabled": true,
          "description": "App Service must authenticate users using Azure Active Directory backed credentials",
          "rationale": "Using the native enterprise directory for authentication ensures that there is a built-in high level of assurance in the user identity established for subsequent access control.All Enterprise subscriptions are automatically associated with their enterprise directory (xxx.onmicrosoft.com) and users in the native directory are trusted for authentication to enterprise subscriptions.",
          "recommendation": "",
          "severity": "High",
          "jsonPath": [ "$.properties.siteConfig.siteAuthSettings.clientId", "$.properties.siteAuthSettings.clientId" ],
          "matchType": "StringWhitespace",
          "data": {
            "value": false
          }
 
        },
        {
          "id": "AppService400",
          "apiVersions": [ "2016-08-01" ],
          "controlId": "Azure_AppService_AuthN_Use_Managed_Service_Identity",
          "isEnabled": true,
          "description": "Use Managed Service Identity (MSI) for accessing other AAD-protected resources from the app service.",
          "rationale": "Managed Service Identity (MSI) allows your app to easily access other AAD-protected resources such as Azure Key Vault. The identity is managed by the Azure platform and eliminates the need to provision/manage/rotate any secrets thus reducing the overall risk.",
          "recommendation": "Go to Azure Portal --> your App Service --> Settings --> Managed Service Identity --> Register with AAD --> ON",
          "severity": "Medium",
          "jsonPath": [ "$.identity.type" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "SystemAssigned",
            "isCaseSensitive": false
          }
        }
      ]
    },
    {
      "featureName": "KubernetesService",
      "supportedResourceTypes": [ "Microsoft.ContainerService/ManagedClusters" ],
      "controls": [
        {
          "id": "KubernetesService150",
          "controlId": "Azure_KubernetesService_Deploy_Use_Latest_Version",
          "isEnabled": true,
          "description": "The latest version of Kubernetes should be used",
          "rationale": "Running on older versions could mean you are not using latest security classes. Usage of such old classes and types can make your application vulnerable.",
          "recommendation": "Refer: https://docs.microsoft.com/en-us/azure/aks/upgrade-cluster.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.kubernetesVersion" ],
          "matchType": "VersionSingleToken",
          "data": {
            "type": "GreaterThanOrEqual",
            "value": "1.14.0",
            "isCaseSensitive": false
          }
        },
        {
          "id": "KubernetesService120",
          "controlId": "Azure_KubernetesService_AuthN_Enabled_AAD",
          "isEnabled": true,
          "description": "AAD should be enabled in Kubernetes Service",
          "rationale": "Using the native enterprise directory for authentication ensures that there is a built-in high level of assurance in the user identity established for subsequent access control.All Enterprise subscriptions are automatically associated with their enterprise directory (xxx.onmicrosoft.com) and users in the native directory are trusted for authentication to enterprise subscriptions.",
          "recommendation": "Refer: https://docs.microsoft.com/en-us/azure/aks/aad-integration to configure AAD in Kubernetes Service.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.aadProfile" ],
          "matchType": "ItemCount",
          "data": {
            "type": "GreaterThan",
            "value": 1
          }
        },
        {
          "id": "KubernetesService110",
          "controlId": "Azure_KubernetesService_Deploy_Enable_Cluster_RBAC",
          "isEnabled": true,
          "description": "Cluster RBAC must be enabled in Kubernetes Service",
          "rationale": "Enabling RBAC in a cluster lets you finely control access to various operations at the cluster/node/pod/namespace scopes for different stakeholders. Without RBAC enabled, every user has full access to the cluster which is a violation of the principle of least privilege. Note that Azure Kubernetes Service does not currently support other mechanisms to define authorization in Kubernetes (such as Attribute-based Access Control authorization or Node authorization).",
          "recommendation": "RBAC flag must be enabled while creating the Kubernetes Service. Existing non-RBAC enabled Kubernetes Service clusters cannot currently be updated for RBAC use. Refer: https://docs.microsoft.com/en-us/azure/aks/aad-integration.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.enableRBAC" ],
          "matchType": "Boolean",
          "data": {
            "value": true
          }
        },
        {
          "id": "KubernetesService220",
          "controlId": "Azure_KubernetesService_Audit_Enable_Logging_and_Monitoring",
          "isEnabled": true,
          "description": "Monitoring must be enabled for Azure Kubernetes Service",
          "rationale": "Auditing enables log collection of important system events pertinent to security. Regular monitoring of audit logs can help to detect any suspicious and malicious activity early and respond in a timely manner.",
          "recommendation": "Refer: https://docs.microsoft.com/en-us/azure/azure-monitor/insights/container-insights-overview.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.addonProfiles.omsagent.enabled" ],
          "matchType": "Boolean",
          "data": {
            "value": true
          }
        }
      ]
    },
    {
      "featureName": "LogicApps",
      "supportedResourceTypes": [ "Microsoft.Logic/workflows" ],
      "controls": [
        {
          "id": "LogicApps150",
          "controlId": "Azure_LogicApps_AuthZ_Provide_Triggers_Access_Control",
          "isEnabled": true,
          "description": "If Logic App fires on an HTTP Request (e.g. Request or Webhook) then provide IP ranges for triggers to prevent unauthorized access",
          "rationale": "Specifying the IP range ensures that the triggers can be invoked only from a restricted set of endpoints.",
          "recommendation": "Do not add IP range $($this.ControlSettings.UniversalIPRange) as this means access to all IPs. Note: In case the IP range is indeterminate (for instance, if the client is a PaaS endpoint), you may need to attest this control. Please refer https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-securing-a-logic-app#set-ip-ranges---logic-app-deployment-template",
          "severity": "High",
          "jsonPath": [ "$.properties.accessControl.triggers.allowedCallerIpAddresses.addressRange" ],
          "matchType": "VerifiableSingleToken",
          "data": {}
        },
        {
          "id": "LogicApps160",
          "controlId": "Azure_LogicApps_AuthZ_Provide_Contents_Access_Control",
          "isEnabled": true,
          "description": "Must provide IP ranges for contents to prevent unauthorized access to inputs/outputs data of Logic App run history",
          "rationale": "Using the firewall feature ensures that access to the data or the service is restricted to a specific set/group of clients. While this may not be feasible in all scenarios, when it can be used, it provides an extra layer of access control protection for critical assets.",
          "recommendation": "Do not add IP range $($this.ControlSettings.UniversalIPRange) as this means access to all IPs. Note: In case the IP range is indeterminate (for instance, if the client is a PaaS endpoint), you may need to attest this control. Please refer https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-securing-a-logic-app#set-ip-ranges---logic-app-deployment-template-1",
          "severity": "High",
          "jsonPath": [ "$.properties.accessControl.contents.allowedCallerIpAddresses.addressRange" ],
          "matchType": "VerifiableSingleToken",
          "data": {}
        }
      ]
    },
    {
      "featureName": "ContainerRegistry",
      "supportedResourceTypes": [ "Microsoft.ContainerRegistry/registries" ],
      "controls": [
        {
          "id": "ContainerRegistry110",
          "controlId": "Azure_ContainerRegistry_AuthZ_Disable_Admin_Account",
          "isEnabled": true,
          "description": "The Admin account in Container Registry should be disabled",
          "rationale": "The Admin user account is designed for a single user to access the registry. Multiple users authenticating with the admin account appear as just one user to the registry. This leads to loss of auditability. Using AAD-based identity ensures that there is a built-in high level of assurance in the user identity established for subsequent access control.",
          "recommendation": "Run command 'Update-AzContainerRegistry -DisableAdminUser -Name '<ContainerRegistryName>' -ResourceGroupName '<RGName>'. Run 'Get-Help Update-AzContainerRegistry -full' for more help. You can add AAD-based SPNs or user accounts to the appropriate RBAC role instead.",
          "severity": "High",
          "jsonPath": [ "$.properties.adminUserEnabled" ],
          "matchType": "Boolean",
          "data": {
            "value": false
          }
        }
      ]
    },
    {
      "featureName": "KeyVault",
      "supportedResourceTypes": [ "Microsoft.KeyVault/vaults" ],
      "controls": [
        {
          "id": "KeyVault140",
          "controlId": "Azure_KeyVault_AuthZ_Grant_Min_Access_policies",
          "isEnabled": true,
          "Description": "All Key Vault access policies must be defined with minimum required permissions to keys and secrets",
          "Rationale": "Granting minimum access by defining Key Vault access policies ensures that applications/users are granted just enough permissions to perform their tasks. This minimizes exposure of the resources in case of user/service account compromise.",
          "Recommendation": "Use command Set-AzKeyVaultAccessPolicy -VaultName '{VaultName}' -ResourceGroupName '{ResourceGroupName}'  -PermissionsToKeys '{PermissionsToKeys}' -PermissionsToSecrets '{PermissionsToSecrets}'  -PermissionsToCertificates '{PermissionsToCertificates}' -ObjectId '{ObjectId}'. Refer:  https://docs.microsoft.com/en-us/powershell/module/az.keyvault/Set-AzKeyVaultAccessPolicy",
          "severity": "Medium",
          "jsonPath": [ "$.properties.accessPolicies" ],
          "matchType": "VerifiableSingleToken",
          "data": {}
        },
        {
          "id": "KeyVault150",
          "controlId": "Azure_KeyVault_AuthZ_Configure_Advanced_Access_Policies",
          "isEnabled": true,
          "Description": "Advanced access policies must be configured on a need basis",
          "Rationale": "Advanced access policy allows Azure services (Azure Resource Manager, Virtual Machine, Disk Encryption etc.) to seamlessly access Key Vault. To avoid unintentional access to Key Vault from Azure services, advanced access policies must be configured only as required.",
          "Recommendation": "Remove any advanced policies that are not required using the command: Remove-AzKeyVaultAccessPolicy -VaultName '{VaultName}' -ResourceGroupName '{ResourceGroupName}' -EnabledForDeployment -EnabledForTemplateDeployment -EnabledForDiskEncryption. Refer: https://docs.microsoft.com/en-us/powershell/module/az.keyvault/Remove-AzKeyVaultAccessPolicy",
          "severity": "Medium",
          "jsonPath": [ "$.properties.enabledForDeployment" ],
          "matchType": "Boolean",
          "data": {
            "value": false
          }
        },
        {
          "id": "KeyVault150",
          "controlId": "Azure_KeyVault_AuthZ_Configure_Advanced_Access_Policies",
          "isEnabled": true,
          "Description": "Advanced access policies must be configured on a need basis",
          "Rationale": "Advanced access policy allows Azure services (Azure Resource Manager, Virtual Machine, Disk Encryption etc.) to seamlessly access Key Vault. To avoid unintentional access to Key Vault from Azure services, advanced access policies must be configured only as required.",
          "Recommendation": "Remove any advanced policies that are not required using the command: Remove-AzKeyVaultAccessPolicy -VaultName '{VaultName}' -ResourceGroupName '{ResourceGroupName}' -EnabledForDeployment -EnabledForTemplateDeployment -EnabledForDiskEncryption. Refer: https://docs.microsoft.com/en-us/powershell/module/az.keyvault/Remove-AzKeyVaultAccessPolicy",
          "severity": "Medium",
          "jsonPath": [ "$.properties.enabledForDiskEncryption" ],
          "matchType": "Boolean",
          "data": {
            "value": false
          }
        },
        {
          "id": "KeyVault150",
          "controlId": "Azure_KeyVault_AuthZ_Configure_Advanced_Access_Policies",
          "isEnabled": true,
          "Description": "Advanced access policies must be configured on a need basis",
          "Rationale": "Advanced access policy allows Azure services (Azure Resource Manager, Virtual Machine, Disk Encryption etc.) to seamlessly access Key Vault. To avoid unintentional access to Key Vault from Azure services, advanced access policies must be configured only as required.",
          "Recommendation": "Remove any advanced policies that are not required using the command: Remove-AzKeyVaultAccessPolicy -VaultName '{VaultName}' -ResourceGroupName '{ResourceGroupName}' -EnabledForDeployment -EnabledForTemplateDeployment -EnabledForDiskEncryption. Refer: https://docs.microsoft.com/en-us/powershell/module/az.keyvault/Remove-AzKeyVaultAccessPolicy",
          "severity": "Medium",
          "jsonPath": [ "$.properties.enabledForTemplateDeployment" ],
          "matchType": "Boolean",
          "data": {
            "value": false
          }
 
        },
        {
          "id": "KeyVault230",
          "controlId": "Azure_KeyVault_SI_Enable_SoftDelete",
          "isEnabled": true,
          "Description": "Soft delete must be enabled to allow recovery of deleted Key Vault and any objects (keys, secrets, etc.) contained in it.",
          "Rationale": "Enabling soft delete feature on Key Vault acts as a safety measure to recover inadvertently or maliciously deleted Key Vault and any objects (keys, secrets, etc.) contained in it.",
          "Recommendation": "Refer: https://docs.microsoft.com/en-us/azure/key-vault/key-vault-soft-delete-powershell to enable soft delete feature on Key Vault.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.enableSoftDelete" ],
          "matchType": "Boolean",
          "data": {
            "value": true
          }
        }
      ]
    },
    {
      "featureName": "VirtualNetwork",
      "supportedResourceTypes": [ "Microsoft.Network/networkInterfaces" ],
      "controls": [
        {
          "id": "VirtualNetwork120",
          "controlId": "Azure_VNet_NetSec_Justify_IPForwarding_for_NICs",
          "isEnabled": true,
          "Description": "Use of IP Forwarding on any NIC in a virtual network should be scrutinized",
          "Rationale": "Enabling IP Forwarding on a VM NIC allows the VM to receive traffic addressed to other destinations. IP forwarding is required only in rare scenarios (e.g., using the VM as a network virtual appliance) and those should be reviewed with the network security team.",
          "Recommendation": "Disable IP Forwarding unless it has been reviewed and approved by network security team. Go to Azure Portal --> Navigate to VM NIC (where IP Forwarding is enabled) --> IP Configurations --> IP Forwarding settings --> Click on 'Disabled'.",
          "Severity": "High",
          "jsonPath": [ "$.properties.enableIPForwarding" ],
          "matchType": "Boolean",
          "data": {
            "value": false
          }
        }
      ]
    },
    {
      "featureName": "ContainerInstances",
      "supportedResourceTypes": [ "Microsoft.ContainerInstance/containerGroups" ],
      "controls": [
          {
              "Id": "ContainerInstances110",
              "ControlID": "Azure_ContainerInstances_NetSec_Justify_PublicIP_and_Ports",
              "isEnabled": true,
              "Description": "Use of public IP address and ports should be carefully reviewed",
              "Rationale": "Public IP address provides direct access over the internet exposing the container to all type of attacks over the public network.",
              "Recommendation": "Add public IP address and ports to a container only as required. Ensure that the resulting data flows are carefully reviewed.",
              "Severity": "High",
              "jsonPath": [ "$.properties.ipAddress" ],
              "matchType": "NullableSingleToken",
              "data": {}
          },
          {
              "Id": "ContainerInstances140",
              "ControlID": "Azure_ContainerInstances_AuthZ_Container_Segregation",
              "isEnabled": true,
              "Description": "A container group must contain only containers which trust each other",
              "Rationale": "Containers hosted in the same container group can monitor traffic of other containers within the group and can also access the file system of the host OS. Hence a container group must not host containers which do not trust each other. In other words, do not mix containers across trust boundaries in the same group.",
              "Recommendation": "Carefully review the role and privileges required by each container in a container group. If the privilege levels and access requirements are different, then consider segregating the containers into separate groups.",
              "Severity": "High",
              "jsonPath": [ "$.properties.containers" ],
              "matchType": "ItemCount",
              "data": {
                  "type": "LesserThan",
                  "value": 2
              }
          }
      ]
    },
    {
      "featureName": "EventHub",
      "supportedResourceTypes": [ "Microsoft.EventHub/namespaces","Microsoft.EventHub/namespaces/AuthorizationRules","Microsoft.EventHub/namespaces/eventhubs/authorizationRules" ],
      "controls": [
        {
          "ControlID": "Azure_EventHub_AuthZ_Use_Min_Permissions_Access_Policies",
          "Description": "Access policies must be defined with minimum required permissions to the Event Hub",
          "Id": "EventHub140",
          "ControlSeverity": "Medium",
          "Automated": "Yes",
          "MethodName": "CheckEventHubAuthorizationRule",
          "Rationale": "Granting minimum access ensures that users are granted just enough permissions to perform their tasks. This minimizes the set of operations that can be preformed on the resource by an attacker in case of access policy key compromise.",
          "Recommendation": "Ensure that client apps use shared access policies with the least required privilege and at the Event Hub scope. For instance, if the client app is only reading events from the event hub (as opposed to sending), then the policy used must only include the 'Listen' claim. Refer: https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-authentication-and-security-model-overview",
          "jsonPath": [ "$.properties.rights" ],
          "matchType": "ItemCount",
          "data": {
            "type":"LesserThan",
            "value":2
          }
        }
     ]
    },
    {
      "featureName": "Search",
      "supportedResourceTypes": [ "Microsoft.Search/searchServices" ],
      "controls": [
        {
          "id": "Search170",
          "controlId": "Azure_Search_Availability_Configure_Three_Replicas",
          "isEnabled": true,
          "description": "Search service must have at least three replicas for high availability",
          "rationale": "High availability can be achieved by adding replicas. Each replica has one copy of an index, so adding one more replica translates to one more index that can be used to service query requests. Minimum of three replicas are required since the azure team has specified three to be the borderline value for the same",
          "recommendation": "Go to Azure Portal --> your Search service --> Settings --> Scale --> Replicas. Ensure that at least 3 replicas are setup.",
          "severity": "High",
          "jsonPath": [ "$.properties.replicaCount" ],
          "matchType": "IntegerValue",
          "data": {
            "type": "GreaterThan",
            "value": 2
          }
        }
      ]
    },
    {
      "featureName": "APIManagement",
      "supportedResourceTypes": [ "Microsoft.ApiManagement/service", "Microsoft.ApiManagement/service/apis"],
      "controls": [
        {
          "id": "APIManagement220",
          "controlId": "Azure_APIManagement_NetSec_Configure_Virtual_Network_For_APIM",
          "isEnabled": true,
          "description": "Consider hosting APIM within a virtual network for improved isolation",
          "rationale": "Azure Virtual Network (VNet) deployment provides enhanced security and isolation for API management instance, as well as backend service, access control policies, and other features to further restrict access.",
          "recommendation": "Where feasible/practical, host the APIM and APIs within an isolated network. For steps to deploy Azure API Management inside a Virtual Network, refer: https://docs.microsoft.com/en-us/azure/api-management/api-management-using-with-vnet.",
          "severity": "Medium",
          "jsonPath": [ "$.properties.virtualNetworkType" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "NotAllow",
            "value": "None",
            "isCaseSensitive": false
          }
        },
        {
          "id": "APIManagement340",
          "controlId": "Azure_APIManagement_AuthN_Use_Managed_Service_Identity",
          "isEnabled": true,
          "description": "Use Managed Service Identity (MSI) for accessing other AAD-protected resources from the API management instance",
          "rationale": "Managed Service Identity (MSI) allows your API Management instance to easily access other AAD-protected resources, such as Azure Key Vault. The identity is managed by the Azure platform and eliminates the need to provision/manage/rotate any secrets thus reducing the overall risk.",
          "recommendation": "Go to Azure Portal --> your API management instance --> Settings --> Managed Service Identity --> Register with AAD --> ON",
          "severity": "Medium",
          "jsonPath": [ "$.identity.type" ],
          "matchType": "StringSingleToken",
          "data": {
            "type": "Allow",
            "value": "SystemAssigned",
            "isCaseSensitive": false
          }
        },
        {
          "id": "APIManagement140",
          "controlId": "Azure_APIManagement_DP_Use_HTTPS_URL_Scheme",
          "isEnabled": true,
          "description": "Backend API(s) must be accessible only over HTTPS via API Management service",
          "rationale": "Use of HTTPS ensures server/service authentication and protects data in transit from network layer eavesdropping attacks.",
          "recommendation": "Run command: Set-AzApiManagementApi -Context {APIContextObject} -Protocols 'Https' -Name '{APIName}' -ApiId '{APIId}' -ServiceUrl '{ServiceURL}'. Run command : Get-AzApiManagementApi -Context '{APIContextObject}' to get the details of existing APIs. Refer https://docs.microsoft.com/en-us/powershell/module/az.apimanagement/set-azapimanagementapi",
          "severity": "High",
          "jsonPath": [ "$.properties.protocols" ],
          "matchType": "StringMultiToken",
          "data": {
            "type": "Equals",
            "value": ["https"],
            "isCaseSensitive": false
          }
        }
      ]
    },
    {
      "featureName": "HDInsight",
      "supportedResourceTypes": [ "Microsoft.HDInsight/clusters" ],
      "controls": [
        {
          "id": "HDInsight110",
          "controlId": "Azure_HDInsight_Deploy_Supported_Cluster_Version",
          "isEnabled": true,
          "description": "HDInsight must have supported HDI cluster version",
          "rationale": "Being on the latest/supported HDInsight version significantly reduces risks from security bugs or updates that may be present in older or retired cluster versions.",
          "recommendation": "Refer: https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-component-versioning?#supported-hdinsight-versions https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-upgrade-cluster",
          "severity": "High",
          "jsonPath": [ "$.properties.clusterVersion" ],
          "matchType": "VersionSingleToken",
          "data": {
            "type": "GreaterThanOrEqual",
            "value": "3.6.0",
            "isCaseSensitive": false
          }
        }
      ]
    }
  ]
}