ISO 27002:2022
Technological controls – ISO 27002:2022

ISO 27002:2022 8.20: Networks security

Networks and network devices are to be secured, managed and controlled so that information in systems and applications is protected. Purpose: protect information in networks and the facilities that support it from being compromised through the network. Guidance: implement controls that secure information in networks and protect connected services from unauthorized access, considering: the kinds and classification of information the network can carry; responsibilities and procedures for managing network equipment and devices; current documentation including network diagrams and device configuration files for routers, switches and similar; where suitable, keeping network operations under different responsibility from running ICT systems (5.3); controls protecting the confidentiality and integrity of data over public, third-party or wireless networks and protecting connected systems and applications (5.22, 8.24, 5.14, 6.6), plus measures for availability of network services and connected computers; logging and monitoring that records and detects security-relevant actions (8.15, 8.16); close coordination of network management so service is optimized and controls are applied consistently across the infrastructure; authenticating systems on the network; restricting and filtering system connections, for example with firewalls; detecting, restricting and authenticating equipment and devices connecting to the network; hardening network devices; separating network administration channels from other traffic; being able to isolate critical subnetworks temporarily if the network is attacked; and disabling vulnerable network protocols. Apply suitable security to virtualized networks, including software-defined networking and SD-WAN, which can help by logically separating communications over shared physical networks, especially for distributed systems. Other information: see the ISO/IEC 27033 series and ISO/IEC TS 23167.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 148 controls across 33 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 · 17 controls

  • 1.1.1 1.1.1 Requirement 1 policies and procedures governed
  • 1.2.1 1.2.1 Ruleset configuration standards for NSCs
  • 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.2.6 1.2.6 Security features for insecure services in use
  • 1.2.7 1.2.7 Six-monthly review of NSC configurations
  • 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
  • 1.4.2 1.4.2 Restricting traffic entering trusted networks from outside
  • 1.4.3 1.4.3 Anti-spoofing measures at trusted boundary
  • 1.4.4 1.4.4 Cardholder data stores not reachable from untrusted networks
  • 1.4.5 1.4.5 Internal IP and routing disclosure limited
  • 1.5.1 1.5.1 Security controls on dual-connected devices
  • 11.2.1 11.2.1 Detect authorized and rogue wireless access points
  • 11.5.1 11.5.1 IDS/IPS monitoring of CDE traffic
  • 6.4.2 6.4.2 Automated web attack detection and prevention

FedRAMP High · 14 controls

  • CA-9 Internal System Connections
  • CM-7(1) Periodic Review
  • SA-4(9) Acquisition Process | Functions, Ports, Protocols, and Services in Use (SA-4(9))
  • SC-10 Network Disconnect
  • 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(4) External Telecommunications Services
  • SC-7(5) Deny by Default Allow by Exception
  • SC-7(7) Split Tunneling for Remote Devices
  • SC-8 Transmission Confidentiality and Integrity
  • SC-8(1) Cryptographic Protection
  • SI-4(4) Inbound and Outbound Communications Traffic

FedRAMP Moderate · 14 controls

  • CA-9 Internal System Connections
  • CM-7(1) Periodic Review
  • SA-4(9) Acquisition Process | Functions, Ports, Protocols, and Services in Use (SA-4(9))
  • SC-10 Network Disconnect
  • 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(4) External Telecommunications Services
  • SC-7(5) Deny by Default Allow by Exception
  • SC-7(7) Split Tunneling for Remote Devices
  • SC-8 Transmission Confidentiality and Integrity
  • SC-8(1) Cryptographic Protection
  • SI-4(4) Inbound and Outbound Communications Traffic

CIS Controls v8 · 13 controls

  • CIS-12.1 Ensure Network Infrastructure is Up-to-Date
  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-12.3 Securely Manage Network Infrastructure
  • CIS-12.7 Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise’s AAA Infrastructure
  • CIS-13.3 Deploy a Network Intrusion Detection Solution
  • CIS-13.4 Perform Traffic Filtering Between Network Segments
  • CIS-13.8 Deploy a Network Intrusion Prevention Solution
  • CIS-13.9 Deploy Port-Level Access Control
  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • CIS-4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure
  • CIS-4.4 Implement and Manage a Firewall on Servers
  • CIS-4.5 Implement and Manage a Firewall on End-User Devices
  • CIS-4.9 Configure Trusted DNS Servers on Enterprise Assets
  • ASBv3-GS-4 Define and implement network security strategy
  • ASBv3-NS-4 Deploy intrusion detection/intrusion prevention systems (IDS/IPS)
  • ASBv3-NS-6 Deploy web application firewall
  • ASBv3-NS-7 Simplify network security configuration
  • ASBv3-NS-8 Detect and disable insecure services and protocols
  • LT-4 Enable network logging for security investigation
  • NS-1 Establish network segmentation boundaries
  • NS-2 Secure cloud services with network controls
  • NS-3 Deploy firewall at the edge of enterprise network
  • NS-5 Deploy DDOS protection
  • ISM-0518 Maintaining network documentation
  • ISM-0520 Blocking unauthorised network devices
  • ISM-1006 Protecting network management traffic
  • ISM-1013 RF shielding for classified wireless
  • ISM-1304 Default network device credentials
  • ISM-1338 Low-power access point deployment
  • ISM-1439 Protecting origin servers behind CDNs
  • ISM-1862 Protecting WAF origin servers

CMMC 2.0 · 8 controls

NIST SP 800-53 Rev 5 · 8 controls

  • 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-20 Secure Wi-Fi Access Networks and Separate Usage
  • ANSSI-HYG-21 Use Secure Protocols Wherever They Exist
  • ANSSI-HYG-22 Put in Place a Secure Internet Access Gateway
  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • 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.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected
  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied
  • ASD37-08 Deny direct internet connectivity (Excellent)
  • ASD37-25 Software firewall - inbound (Very Good)
  • ASD37-26 Software firewall - outbound (Very Good)
  • ASD37-32 Network-based IDS/IPS (Limited)

C5 (Germany) · 4 controls

  • C5-COS-01 Technical safeguards
  • C5-COS-04 Cross-network access
  • C5-COS-06 Segregation of data traffic in jointly used network environments
  • C5-COS-07 Documentation of the network topology

ISO 27001:2022 · 4 controls

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

UK Cyber Essentials · 4 controls

MTCS (Singapore) · 3 controls

  • 14.5 Physical port protection
  • 24.4 Network protection
  • A.25 Disclosure: Network resiliency and elasticity

NIST SP 800-171 Rev 3 · 2 controls

  • 03.13.01 Boundary Protection
  • 03.13.06 Network Communications - Deny by Default - Allow by Exception

SOC 2 · 2 controls

  • 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
  • E8-PATCHOS-ML3 Patch Operating Systems (ML3)
  • B.1.4 B.1.4 Security convergence of physical and information security risk management
  • AUCDR-IS-2 Secure the network and systems within the data environment

DORA · 1 control

HIPAA Security Rule · 1 control

IEC 62443 · 1 control

  • 62443-2-4-SP-04 Service Provider Wireless and Remote Access Practices

ISO 27701:2019 · 1 control

  • 6.10.1 Network security management

NIS2 Directive · 1 control

  • Art.21.2.j Multi-factor or continuous authentication, secured communications and secured emergency communications

NIST SP 800-172 · 1 control

  • 3.5.1e Identification of Systems, Components, and Devices
  • P2-4.4.1 P2-4.4.1 No wireless use by 3DS components
  • MTSA-Vendor-Remote-Access Third Party and Vendor Remote Access

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 27002:2022

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

ISO 27002:2022 8.20 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27002:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27002:2022 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. 180 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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