Skip to content

[RULE] AZ-NET-013: Azure Firewall not enabled on Virtual Network #91

@aav-wh

Description

@aav-wh

Objective

Add a new scanner rule to detect Virtual Networks that do not have an Azure Firewall deployed.

Background

A VNet without an Azure Firewall relies solely on Network Security Groups for perimeter defence. NSGs provide no deep packet inspection, threat intelligence filtering, or centralised traffic logging. This leaves the network vulnerable to lateral movement and data exfiltration that appears legitimate at the port level.

Real-World Breach Scenario

Attackers who bypass NSG rules have no secondary inspection layer to stop them. Without Azure Firewall, malicious outbound traffic such as data exfiltration or C2 communication cannot be detected or blocked at the network perimeter.

Compliance Mapping

  • CIS Azure Benchmark: 6.4
  • NIST CSF: PR.AC-5
  • ISO 27001: A.13.1.1
  • SOC 2: CC6.6

Deliverables

  • scanner/rules/az_net_013.py — scan() function using Azure SDK
  • playbooks/cli/fix_az_net_013.sh — deploy Azure Firewall guidance
  • compliance/frameworks/cis_azure_benchmark.json — add AZ-NET-013 entry
  • compliance/frameworks/nist_csf.json — add AZ-NET-013 entry
  • compliance/frameworks/iso27001.json — add AZ-NET-013 entry
  • compliance/frameworks/soc2.json — add AZ-NET-013 entry

Severity

HIGH

Category

Network

Metadata

Metadata

Assignees

No one assigned

    Labels

    new-ruleAdding a new misconfiguration scan rule

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    📋 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions