ISO 27001:2022
Technological controls – ISO 27001:2022

ISO 27001:2022 8.22: Segregation of networks

Within its networks the organization is to keep groups of users, information services and information systems apart. Purpose (stated in ISO/IEC 27002:2022): divides the network along security boundaries and governs traffic across them by business need. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.22.

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

What else in your programme already covers this

This control maps to 89 controls across 26 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 · 13 controls

  • 1.2.3 1.2.3 Accurate network diagram of CDE connections
  • 1.2.4 1.2.4 Accurate data-flow diagram for account data
  • 1.3.1 1.3.1 Inbound CDE traffic restricted
  • 1.3.2 1.3.2 Outbound CDE traffic restricted
  • 1.3.3 1.3.3 NSCs between wireless networks and the CDE
  • 1.4.1 1.4.1 NSCs between trusted and untrusted networks
  • 1.4.2 1.4.2 Restricting traffic entering trusted networks from outside
  • 1.4.4 1.4.4 Cardholder data stores not reachable from untrusted networks
  • 1.5.1 1.5.1 Security controls on dual-connected devices
  • 11.4.5 11.4.5 Annual segmentation penetration testing
  • 11.4.6 11.4.6 Service provider segmentation testing every six months
  • 2.2.3 2.2.3 Primary functions with different security levels managed
  • 2.2.4 2.2.4 Only necessary functionality enabled

FedRAMP High · 9 controls

  • AC-4 Information Flow Enforcement
  • CA-9 Internal System Connections
  • SC-22 Architecture and Provisioning for Name/Address Resolution Service
  • SC-39 Process Isolation
  • SC-7 Boundary Protection
  • SC-7(12) Boundary Protection | Host-based Protection (SC-7(12))
  • SC-7(18) Boundary Protection | Fail Secure (SC-7(18))
  • SC-7(3) Access Points
  • SC-7(5) Deny by Default Allow by Exception

FedRAMP Moderate · 9 controls

  • AC-4 Information Flow Enforcement
  • CA-9 Internal System Connections
  • SC-22 Architecture and Provisioning for Name/Address Resolution Service
  • SC-39 Process Isolation
  • SC-7 Boundary Protection
  • SC-7(12) Boundary Protection | Host-based Protection (SC-7(12))
  • SC-7(18) Boundary Protection | Fail Secure (SC-7(18))
  • SC-7(3) Access Points
  • SC-7(5) Deny by Default Allow by Exception

NIST SP 800-53 Rev 5 · 9 controls

CMMC 2.0 · 7 controls

CIS Controls v8 · 5 controls

  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-12.8 Establish and Maintain Dedicated Computing Resources for All Administrative Work
  • CIS-13.4 Perform Traffic Filtering Between Network Segments
  • CIS-3.12 Segment Data Processing and Storage Based on Sensitivity
  • CIS-4.12 Separate Enterprise Workspaces on Mobile End-User Devices

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 4 controls

  • ANSSI-HYG-19 Segment the Network and Partition the Zones
  • ANSSI-HYG-20 Secure Wi-Fi Access Networks and Separate Usage
  • 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

C5 (Germany) · 4 controls

  • C5-COS-04 Cross-network access
  • C5-COS-05 Networks for administration
  • C5-COS-06 Segregation of data traffic in jointly used network environments
  • C5-OPS-24 Separation of Datasets in the Cloud Infrastructure

NIST SP 800-171 Rev 3 · 4 controls

  • 03.01.03 Information Flow Enforcement
  • 03.13.01 Boundary Protection
  • 03.13.04 Information in Shared System Resources
  • 03.13.06 Network Communications - Deny by Default - Allow by Exception

SOC 2 · 4 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal

AWS Well-Architected Security Pillar · 3 controls

ISO 27002:2022 · 3 controls

  • 8.20 Networks security
  • 8.21 Security of network services
  • 8.22 Segregation of networks

Azure Security Benchmark · 2 controls

  • ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy
  • NS-1 Establish network segmentation boundaries

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-22 Network segmentation (Excellent)

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-2 Secure the network and systems within the data environment

COBIT 2019 · 1 control

  • DSS05.02 DSS05.02 Manage network and connectivity security

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2013 · 1 control

ISO 27701:2019 · 1 control

  • 6.10.1 Network security management

NIS2 Directive · 1 control

  • Art.21.2.g Basic cyber hygiene practices and cybersecurity training

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-172 · 1 control

  • 3.13.1e Create Diversity in System Components to Limit Malicious Code Propagation

NIST SP 800-66 Rev 2 · 1 control

UK Cyber Essentials · 1 control

  • CE-SU.4 Remove Out-of-Support Software

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 Technological controls – ISO 27001:2022

You are reading one control. How much of ISO 27001:2022 have you already done?

ISO 27001:2022 8.22 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

If you hold NIST SP 800-53 Rev 584.9% covered · 14 gapsIf you hold ISO 27001:201383.9% covered · 15 gapsIf you hold FedRAMP Moderate80.6% covered · 18 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.2% covered · 24 gapsIf you hold C5 (Germany)69.9% covered · 28 gapsIf you hold NIST Cybersecurity Framework 2.063.4% covered · 34 gaps

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. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll ISO 27001:2022 controls