You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Guidance**: Use Windows Defender on your individual batch nodes in the case of Windows operating systems, or provide your own anti-malware solution if you are using Linux.
327
327
328
-
**Azure Security Center monitoring**: Currently not available
328
+
**Azure Security Center monitoring**: Yes
329
329
330
330
**Responsibility**: Customer
331
331
@@ -468,7 +468,7 @@ How to monitor users identity and access activity in Azure Security Center:
### 3.13: Provide Microsoft with access to relevant customer data during support scenarios
556
+
### 3.13: <div>Provide Microsoft with access to relevant customer data during support scenarios<br></div>
557
557
558
558
**Guidance**: Not available; Customer Lockbox not yet supported for Azure Batch. List of Customer Lockbox supported services: https://docs.microsoft.com/azure/security/fundamentals/customer-lockbox-overview#supported-services-and-scenarios-in-general-availability
559
559
@@ -616,9 +616,9 @@ How to secure Azure Storage Accounts:
**Azure Security Center monitoring**: Currently not available
733
+
**Azure Security Center monitoring**: Yes
734
734
735
735
**Responsibility**: Customer
736
736
@@ -753,7 +753,7 @@ Optionally, if you have a Rapid7, Qualys, or any other vulnerability management
753
753
754
754
**Guidance**: Microsoft to maintain and update base Azure Batch Pool node images. Ensure Azure Batch Pool nodes' operating system remains patched for the duration of the cluster lifetime which may require enabling automatic updates, monitoring the nodes, or performing periodic reboots.
755
755
756
-
**Azure Security Center monitoring**: Currently not available
756
+
**Azure Security Center monitoring**: Yes
757
757
758
758
**Responsibility**: Shared
759
759
@@ -790,7 +790,7 @@ Optionally, if you have a Rapid7, Qualys, or any other vulnerability management
790
790
**Guidance**: Use Azure Resource Graph to query/discover all resources (such as compute, storage, network, etc.) within your subscription(s). Ensure that you have appropriate (read) permissions in your tenant and are able to enumerate all Azure subscriptions as well as resources within your subscriptions.
791
791
792
792
793
-
Although classic Azure resources may be discovered via Resource Graph, it is highly recommended to create and use Azure Resource Manager resources going forward.
793
+
Although classic Azure resources may be discovered via Resource Graph, it is highly recommended to create and use Azure Resource Manager (ARM) resources going forward.
Use Azure Resource Graph to query/discover resources within your subscription(s). Ensure that all Azure resources present in the environment are approved.
869
870
871
+
870
872
How to configure and manage Azure Policy: https://docs.microsoft.com/azure/governance/policy/tutorials/create-and-manage
871
873
874
+
872
875
How to create queries with Azure Graph: https://docs.microsoft.com/azure/governance/resource-graph/first-query-portal
873
876
874
877
**Azure Security Center monitoring**: Currently not available
@@ -903,16 +906,15 @@ How to create queries with Azure Graph: https://docs.microsoft.com/azure/governa
903
906
904
907
**Guidance**: Use Azure policy to put restrictions on the type of resources that can be created in customer subscription(s) using the following built-in policy definitions:
### 6.11: Limit Users' Ability to interact with Azure Resource Manager via Scripts
931
+
### 6.11: <div>Limit Users' Ability to interact with Azure Resource Manager via Scripts</div>
930
932
931
933
**Guidance**: Use Azure Conditional Access to limit users' ability to interact with Azure Resource Manager by configuring "Block access" for the "Microsoft Azure Management" App.
932
934
933
935
934
-
How to configure Conditional Access to block access to Azure Resource Manager:
How to configure Conditional Access to block access to Azure Resource Manager: https://docs.microsoft.com/azure/role-based-access-control/conditional-access-azure-management
937
937
938
938
**Azure Security Center monitoring**: Currently not available
939
939
@@ -951,8 +951,7 @@ This is not applicable to Azure Batch, as users (non-administrators) of the Azur
951
951
952
952
### 6.13: Physically or Logically Segregate High Risk Applications
953
953
954
-
**Guidance**: Not available,
955
-
954
+
**Guidance**: Not applicable,
956
955
Benchmark is intended for web applications running on Azure App Service or IaaS instances.
957
956
958
957
**Azure Security Center monitoring**: Not applicable
@@ -968,10 +967,14 @@ Benchmark is intended for web applications running on Azure App Service or IaaS
968
967
**Guidance**: Use Azure Policy aliases in the "Microsoft.Batch" namespace to create custom policies to audit or enforce the configuration of your Azure Batch accounts and pools.
969
968
970
969
971
-
How to view available Azure Policy Aliases:https://docs.microsoft.com/powershell/module/az.resources/get-azpolicyalias?view=azps-3.3.0
### 7.5: Securely Store Configuration of Azure Resources
1013
1018
1014
-
**Guidance**: If using custom Azure policy definitions for your Azure Batch accounts, pools, or related resources, use Azure DevOps/Repos to securely store and manage your code.
1019
+
**Guidance**: If using custom Azure policy definitions for your Azure Batch accounts, pools, or related resources, use Azure Repos to securely store and manage your code.
1020
+
1021
+
1022
+
How to store code in Azure DevOps:
1015
1023
1016
-
How to store code in Azure DevOps: https://docs.microsoft.com/azure/devops/repos/git/gitworkflow?view=azure-devops
**Guidance**: If using custom images for your Azure Batch pools, use Role-based access control (RBAC) to ensure only authorized users may access the images.
1027
1038
1028
1039
1029
-
Understand RBAC in Azure: https://docs.microsoft.com/azure/role-based-access-control/rbac-and-directory-admin-roles
**Guidance**: Use Azure Policy aliases in the "Microsoft.Batch" namespace to create custom policies to audit or enforce the configuration of your Azure Batch instance. You may also use any built-in policies created specifically for Azure Batch or the resources used by Azure Batch, such as:
1062
1078
1063
1079
- Subnets should be associated with a Network Security Group
1064
-
-Storage Accounts should use a virtual network service endpoint
1080
+
-Storage Accounts should use a virtual network service endpoint
1065
1081
- Diagnostic logs in Batch accounts should be enabled
1066
1082
1067
1083
How to view available Azure Policy Aliases: https://docs.microsoft.com/powershell/module/az.resources/get-azpolicyalias?view=azps-3.3.0
@@ -1100,7 +1116,7 @@ How to provide Key Vault authentication with a managed identity:
0 commit comments