💼 7.4 Ensure Subnets Are Associated with Network Security Groups (Automated)

• ID: /frameworks/cis-azure-v7.0.0/07/04

Stats

not available

Description

Each subnet must have an associated network security group to filter its traffic; an unassociated subnet's Network security group setting shows None. GatewaySubnet, AzureFirewallSubnet, and RouteServerSubnet do not support a network security group, and Microsoft reserves AzureFirewallManagementSubnet for the firewall's management traffic, so all four are out of scope. Prerequisites: (Only if using Azure Bastion) Before associating a network security group with AzureBastionSubnet, add every inbound and outbound rule Azure Bastion requires; Azure rejects the association otherwise, and a later deny rule that shadows them breaks Bastion connections.

Similar

• Sections
  • /frameworks/cis-azure-v6.0.0/07/11

Similar Sections (Take Policies From)

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS Azure v6.0.0 → 💼 7.11 Ensure Subnets Are Associated with Network Security Groups (Automated)			1		no data

Similar Sections (Give Policies To)

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS Azure v6.0.0 → 💼 7.11 Ensure Subnets Are Associated with Network Security Groups (Automated)			1		no data

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance

Policies (1)

Policy	Logic Count	Flags	Compliance
🛡️ Azure Network Subnet without Network Security Group🟢	1	🟢 x6	no data