Azure Security Benchmark
Network Security

Azure Security Benchmark NS-1: Establish network segmentation boundaries

Establish network segmentation boundaries using virtual networks, subnets, and network security groups to isolate workloads based on sensitivity and function.

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

What else in your programme already covers this

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

  • ANSSI-HYG-04 Identify the Most Sensitive Information and Servers and Maintain a Network Diagram
  • ANSSI-HYG-07 Authorise Network Connection Only for Managed Equipment
  • ANSSI-HYG-17 Enable and Configure the Local Firewall on Workstations
  • ANSSI-HYG-19 Segment the Network and Partition the Zones
  • ANSSI-HYG-23 Partition Internet Facing Services from the Rest of the Information System
  • ANSSI-HYG-28 Use a Dedicated and Partitioned Network for Administration

FedRAMP High · 5 controls

  • AC-4 Information Flow Enforcement
  • AC-4(21) Physical or Logical Separation of Information Flows
  • CA-9 Internal System Connections
  • SC-7 Boundary Protection
  • SC-7(5) Deny by Default Allow by Exception

FedRAMP Moderate · 5 controls

  • AC-4 Information Flow Enforcement
  • AC-4(21) Physical or Logical Separation of Information Flows
  • CA-9 Internal System Connections
  • SC-7 Boundary Protection
  • SC-7(5) Deny by Default Allow by Exception

PCI DSS 4.0 · 5 controls

  • 1.3.1 1.3.1 Inbound CDE traffic restricted
  • 1.3.2 1.3.2 Outbound CDE traffic restricted
  • 1.4.1 1.4.1 NSCs between trusted and untrusted networks
  • 11.4.5 11.4.5 Annual segmentation penetration testing
  • 2.2.3 2.2.3 Primary functions with different security levels managed

C5 (Germany) · 4 controls

  • C5-COS-02 Security requirements for connections in the Cloud Service Provider's network
  • C5-COS-03 Monitoring of connections in the Cloud Service Provider's network
  • C5-COS-06 Segregation of data traffic in jointly used network environments
  • C5-PSS-10 Software Defined Networking

CIS Controls v8 · 4 controls

  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-13.4 Perform Traffic Filtering Between Network Segments
  • CIS-3.12 Segment Data Processing and Storage Based on Sensitivity
  • CIS-4.4 Implement and Manage a Firewall on Servers

CMMC 2.0 · 4 controls

NIST SP 800-172 · 4 controls

  • 3.1.3e Employ Secure Information Transfer Solutions
  • 3.13.1e Create Diversity in System Components to Limit Malicious Code Propagation
  • 3.13.4e Physical and Logical Isolation Techniques
  • 3.14.3e Include Systems in Scope of Enhanced Requirements or Segregate into Purpose-Specific Networks

NIST SP 800-53 Rev 5 · 4 controls

  • ASD37-08 Deny direct internet connectivity (Excellent)
  • ASD37-22 Network segmentation (Excellent)
  • ASD37-25 Software firewall - inbound (Very Good)

NIST SP 800-171 Rev 3 · 3 controls

  • 03.01.03 Information Flow Enforcement
  • 03.13.01 Boundary Protection
  • 03.13.06 Network Communications - Deny by Default - Allow by Exception

UK Cyber Essentials · 3 controls

ISO 27001:2022 · 2 controls

  • 8.20 Networks security
  • 8.22 Segregation of networks

ISO 27002:2022 · 2 controls

  • 8.20 Networks security
  • 8.22 Segregation of networks
  • 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.IR-01 Networks and environments are protected from unauthorized logical access and usage

NIST SP 800-161 Rev 1 · 2 controls

  • CBPR-PR-30 Specific proportional safeguards in place
  • AUCDR-IS-2 Secure the network and systems within the data environment

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.10.1 Network security management

SOC 2 · 1 control

  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary

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 NS-1 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 69 it maps to, and the evidence behind each claim, over MCP and REST.