Azure Security Benchmark
Governance and Strategy

Azure Security Benchmark ASBv3-GS-4: Define and implement network security strategy

Define and implement a network security strategy with documented guidance, policy and standards covering network design, segmentation, perimeter controls and monitoring.

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

What else in your programme already covers this

This control maps to 38 controls across 22 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-19 Segment the Network and Partition the Zones
  • ANSSI-HYG-22 Put in Place a Secure Internet Access Gateway
  • ANSSI-HYG-23 Partition Internet Facing Services from the Rest of the Information System

C5 (Germany) · 3 controls

  • C5-COS-01 Technical safeguards
  • C5-COS-02 Security requirements for connections in the Cloud Service Provider's network
  • C5-COS-07 Documentation of the network topology

FedRAMP High · 3 controls

  • PL-8 Security and Privacy Architectures
  • SC-1 Policy and Procedures
  • SC-7 Boundary Protection

FedRAMP Moderate · 3 controls

  • PL-8 Security and Privacy Architectures
  • SC-1 Policy and Procedures
  • SC-7 Boundary Protection

NIST SP 800-171 Rev 3 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

CIS Controls v8 · 2 controls

  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure

CMMC 2.0 · 2 controls

ISO 27002:2022 · 2 controls

  • 5.1 Policies for information security
  • 8.20 Networks security

PCI DSS 4.0 · 2 controls

  • 1.1.1 1.1.1 Requirement 1 policies and procedures governed
  • 1.2.1 1.2.1 Ruleset configuration standards for NSCs

APRA CPS 234 · 1 control

  • CPS234-19 Information Security Policy Framework
  • AUCDR-IS-2 Secure the network and systems within the data environment
  • CCM-IVS-01 Infrastructure and Virtualization Security Policy and Procedures

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.20 Networks security
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced

SOC 2 · 1 control

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

UK Cyber Essentials · 1 control

  • CE-FW.4 Approve and Document Inbound 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 Governance and Strategy

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

Azure Security Benchmark ASBv3-GS-4 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 38 it maps to, and the evidence behind each claim, over MCP and REST.