Physical Compliance with NIS2 Directive Requirements
NIS2 requires essential and important entities to implement appropriate technical measures for network security, access control, and incident handling. Control provides physical enforcement that demonstrably exceeds directive requirements.
Key threats addressed
NIS2 raises the bar from configured controls to demonstrably effective controls, with personal accountability at board level. Control replaces software-only segmentation with hardware-enforced zone boundaries and produces continuous, signed evidence of separation, access governance and incident handling that auditors can verify directly.
NIS2
NIS2 requires appropriate and proportionate measures. For essential services that underpin national infrastructure, appropriate means physical, not just logical.
Art. 21
Full Article 21 requirements coverage
100%
Physical network segmentation enforcement
24hr
Incident notification capability support
Full
Automated compliance evidence generation
NIS2 demands demonstrable security measures.
Proportionate Measures
NIS2 requires measures proportionate to the risk. For essential services, this means demonstrating that security measures go beyond standard software controls.
Network Segmentation
Article 21 requires network segmentation, but many organisations rely on VLAN-based separation that can be bypassed through misconfiguration.
Management Accountability
NIS2 introduces personal liability for management bodies. Demonstrating appropriate measures requires evidence that goes beyond compliance checklists.
Pain points
- Firewall rule sets drift between audits, leaving unmonitored gaps in segmentation.
- VLAN-based separation cannot be evidenced as continuously effective.
- Incident reporting timelines collapse without out-of-band recovery infrastructure.
- Boards face personal liability and need verifiable proof, not policy attestations.
The Scenario
Scenario: NIS2 Audit with Physical Evidence
An essential entity faces its first NIS2 compliance audit. The assessor examines network segmentation controls and finds that existing firewall-based segmentation, while configured correctly today, has experienced three misconfiguration incidents in the past year that temporarily created paths between zones. Each incident violated NIS2 requirements for the duration it existed. The organisation cannot demonstrate continuous compliance. With Control, the organisation presents physical zone boundary evidence showing continuous, unbroken zone separation. Conduit activations are logged with multi-party authorisation records. The assessor can verify that physical boundaries were maintained at all times, providing evidence of continuous compliance.
"Our auditor asked us to prove that our network segmentation had been continuously effective for the past twelve months. With firewall logs, we could show configuration at a point in time. We could not prove there had been no gaps between audits."
Where NIS2 Article 21 measures meet Control modules.
NIS2 Article 21 names the measures essential and important entities must implement. Control provides the physical enforcement layer that turns those measures into evidence rather than intent.
Reference: Directive (EU) 2022/2555 (NIS2), Article 21(2)(a) to (j), with cross-reference to NCSC CAF outcomes.
Risk and security policies (Art. 21(2)(a)-(b))
-
21(2)(a)
Risk analysis and information security policies
Continuous attestation of conduit state provides the evidence behind the policy.
Validate
Archive -
21(2)(b)
Incident handling
Firebreak severs governed conduits on alert; restoration is an evidenced Execute event.
Firebreak
Execute
Continuity and supply chain (Art. 21(2)(c)-(d))
-
21(2)(c)
Business continuity and crisis management
Offline recovery copies remain reachable even when the live network is gone.
Archive
Transfer -
21(2)(d)
Supply chain security
Vendor reach is severed by default and opened only as a time-bound, scoped session.
Firebreak
Relay
Lock
Acquisition, development, vulnerability (Art. 21(2)(e)-(f))
-
21(2)(e)
Security in acquisition, development, and maintenance
Maintenance windows are governed Relay sessions with multi-party approval.
RelayExecute -
21(2)(f)
Effectiveness of measures
Validate provides continuous, signed evidence that boundaries hold.
Validate
Hygiene, cryptography, access (Art. 21(2)(g)-(i))
-
21(2)(g)
Cyber hygiene and training
Named access removes shared, evergreen credentials from the workflow.
Lock
Unlink -
21(2)(i)
Human resources security and access control
Trust is revoked at the boundary when relationships end.
UnlinkLock
Authentication and communications (Art. 21(2)(j))
-
21(2)(j)
Multi-factor and secured communications
Cross-zone reach uses named, scoped, time-bound conduits.
LockRelay
Isolate
Modules & symbols
ValidateIntegrity checkArchiveDisconnected copyFirebreakPhysical severExecuteApproved actionTransferControlled moveRelayTime-bound pathLockNamed accessUnlinkRemove trustIsolateZone boundaryFeatured In
Key Capabilities
EU Data Sovereignty
Data residency within UK and EU jurisdictions supports NIS2 requirements for appropriate data handling and sovereignty.
Management Accountability
Documented multi-party authorisation and governance processes demonstrate management oversight required by Article 20.
Continuous Evidence
Automated compliance logging generates continuous NIS2 evidence, eliminating gaps between point-in-time assessments.
Incident Response
Physical zone isolation capabilities support the rapid incident containment required by NIS2 notification timelines.
Audit-Ready Records
Tamper-proof logs provide complete audit trails for every network boundary state, access authorisation, and incident response action.
Recovery Assurance
Verified control-plane baselines demonstrate business continuity capability that exceeds NIS2 operational restoration requirements.
Demo to Live
Adoption Guide
NIS2 Gap Assessment
Map your current security measures against NIS2 Article 21 requirements to identify where physical enforcement strengthens your compliance position.
Compliance Architecture Design
Design physical zone boundaries and access controls that satisfy and exceed NIS2 requirements for your entity classification.
Evidence Validation
Deploy Control in a representative environment to validate compliance evidence generation and prepare for your first NIS2 assessment.
Full Compliance Deployment
Organisation-wide deployment with continuous compliance evidence, multi-party governance, and verified control-plane baseline assurance.
NIS2 Gap Assessment
Map your current security measures against NIS2 Article 21 requirements to identify where physical enforcement strengthens your compliance position.
Compliance Architecture Design
Design physical zone boundaries and access controls that satisfy and exceed NIS2 requirements for your entity classification.
Evidence Validation
Deploy Control in a representative environment to validate compliance evidence generation and prepare for your first NIS2 assessment.
Full Compliance Deployment
Organisation-wide deployment with continuous compliance evidence, multi-party governance, and verified control-plane baseline assurance.
Explore More
DORA Framework
Digital operational resilience for financial services.
Learn more about DORA FrameworkControl for Critical Infrastructure
National-grade security for essential services.
Learn more about Control for Critical InfrastructureISO 27001 Framework
Information security management and Annex A controls.
Learn more about ISO 27001 FrameworkQuestions