Hands-on tutorial

Tutorials · Compliance

One Network, Many Rules: Mapping GDPR, PCI DSS, HIPAA, ISO 27001, NIS2 and SOC 2 to Network Controls

Build one set of network controls that satisfies several frameworks at once: a control map for segmentation, identity, encryption, logging, vulnerability management, resilience and vendor access.

Advanced11 min6 steps

Quick answer

Most frameworks ask for the same core network controls in different words. Building one strong baseline and mapping it to each framework saves effort and keeps evidence consistent.

This guide explains network controls that commonly support compliance. It is not legal advice; confirm your obligations with your legal or compliance adviser.

Before you start

  • A list of the frameworks and regulations that apply to you
  • Current network diagrams and policies
  • An owner for each control

Step by step

  1. List obligations

    Note which frameworks apply and their scope: card data (PCI DSS), health data (HIPAA), EU personal data (GDPR), essential entities (NIS2), certification (ISO 27001, SOC 2).

  2. Define a common control baseline

    Segmentation, MFA and least privilege, encryption in transit, central logging, vulnerability and patch management, secure configuration, backups and resilience, vendor access control.

  3. Map each control to each framework

    Use the table below as a starting point and record evidence for each control: configuration exports, screenshots, reports and reviews.

  4. Choose scope carefully

    Segmentation can shrink the scope of PCI DSS and HIPAA assessments. Document boundaries clearly.

  5. Automate evidence

    Use configuration backups in Git, scheduled scan reports, log retention and NavCloud inventory exports to produce evidence continuously.

  6. Review and test

    Test controls (segmentation tests, restore tests, incident drills) and review rules and accounts on a schedule.

Pro tips

  • One control, many frameworks: avoid parallel projects.
  • Keep a single evidence library organised by control.
  • Re-check the map when frameworks are updated.

Control map across frameworks

ControlGDPRPCI DSS v4.0HIPAAISO 27001:2022NIS2
SegmentationArt. 32Req. 1§164.312(a)A.8.22Art. 21
MFA and least privilegeArt. 32Req. 7–8§164.312(a),(d)A.5.15, A.8.5Art. 21
Encryption in transitArt. 32Req. 4§164.312(e)A.8.24Art. 21
Logging and monitoringArt. 32–33Req. 10§164.312(b)A.8.15, A.8.16Art. 21, 23
Vulnerability and patch managementArt. 32Req. 6, 11§164.308(a)(1)A.8.8Art. 21
Backups and resilienceArt. 32Req. 12.10§164.308(a)(7)A.8.13, A.5.30Art. 21

FAQ

Frequently asked questions

Which framework should we start with?

Start with the one you are legally or contractually required to meet, then extend the same controls to others.

Is ISO 27001 certification required by GDPR?

No, but it is a recognised way to demonstrate a managed security programme.

Stuck on a step?

Ask Navijin technical support or an authorised partner for help with your configuration.