Tutorials · IT Leadership

How to Map Network Security Controls to ISO 27001 and NIS2

Auditors and regulators ask how your network is protected. Map practical network controls to ISO/IEC 27001:2022 Annex A and to the NIS2 risk-management measures, and collect the evidence.

Advanced18 min6 steps

Before you start

  • Your ISO 27001 scope or NIS2 obligations
  • Network documentation and access to configurations and logs

Step by step

  1. Know the key ISO 27001:2022 controls

    Network-related Annex A controls include 8.20 Networks security, 8.21 Security of network services, 8.22 Segregation of networks, 8.23 Web filtering, 8.15 Logging, 8.16 Monitoring activities, 8.9 Configuration management, 8.8 Management of technical vulnerabilities and 8.13 Information backup.

  2. Know the NIS2 measures

    NIS2 Article 21 requires risk-management measures such as incident handling, business continuity and backups, supply-chain security, secure development and maintenance, vulnerability handling, cryptography, access control and MFA. Article 23 requires an early warning within 24 hours and an incident notification within 72 hours for significant incidents.

  3. Map your controls

    Create a table: control, what you do (VLAN segmentation, firewall rule reviews, 802.1X, MFA for admins, config backups, logging to SIEM), owner and evidence.

  4. Collect evidence

    Diagrams, firewall rule review records, scan reports, patch and firmware records, backup restore tests, log retention settings, training records.

  5. Close the gaps

    Turn missing controls into a prioritised plan with owners and dates.

  6. Review regularly

    Review controls and evidence at least yearly and after major changes or incidents.

Pro tips

  • Supply-chain security includes your network vendors: ask for their vulnerability handling and patch policy.
  • Keep evidence in one place so audits take days, not weeks.