Azure Security Benchmark
Network Security

Azure Security Benchmark ASBv3-NS-7: Simplify network security configuration

Use centralised tooling to simplify and manage network security configuration across a complex environment rather than maintaining rules device by device.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 24 controls across 14 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 3 controls

  • 1.2.1 1.2.1 Ruleset configuration standards for NSCs
  • 1.2.7 1.2.7 Six-monthly review of NSC configurations
  • 1.2.8 1.2.8 NSC configuration files secured and consistent

CIS Controls v8 · 2 controls

  • CIS-12.3 Securely Manage Network Infrastructure
  • CIS-4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure
  • CCM-IVS-01 Infrastructure and Virtualization Security Policy and Procedures
  • CCM-IVS-03 Network Security

FedRAMP High · 2 controls

  • CM-6 Configuration Settings
  • SC-7(5) Deny by Default Allow by Exception

FedRAMP Moderate · 2 controls

  • CM-6 Configuration Settings
  • SC-7(5) Deny by Default Allow by Exception

ISO 27001:2022 · 2 controls

  • 8.20 Networks security
  • 8.9 Configuration management

ISO 27002:2022 · 2 controls

  • 8.20 Networks security
  • 8.9 Configuration management
  • NIST-CSF-ID.AM-03 Representations of the organization's authorized network communication and internal and external network data flows are maintained
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied

NIST SP 800-53 Rev 5 · 2 controls

  • ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies

C5 (Germany) · 1 control

  • C5-COS-07 Documentation of the network topology

CMMC 2.0 · 1 control

UK Cyber Essentials · 1 control

  • CE-FW.5 Remove or Disable Unused Rules

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Network Security

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-NS-7 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 24 it maps to, and the evidence behind each claim, over MCP and REST.