Organisations that operate in both the EU and the UK will soon answer to two cyber regimes that look alike on paper but differ on who is in scope, who receives an incident report, and how far penalties reach. NIS2 (Directive (EU) 2022/2555) has applied through national laws since 18 October 2024, while the UK is extending its NIS Regulations 2018 through the Cyber Security and Resilience (Network and Information Systems) Bill. This guide compares the two side by side for scope, managed service providers, data centres, supplier designation, reporting clocks, penalties and supervision, then shows how to build one control set and one reporting process that satisfies both. It is for CISOs, GRC and legal teams at operators, MSPs and data centre operators working in both. For each regime on its own, see the NIS2 Directive Guide and the UK Cyber Security and Resilience Bill Guide.
Status, checked 14 November 2026: the UK Bill is not yet law. Published reports (VinciWorks, 29 October 2026; ISACA, 5 November 2026) record that the House of Lords completed Report stage on 26 October 2026, with Third Reading scheduled for 2 November 2026, after which the amended Bill returns to the Commons to consider Lords amendments. Royal Assent had not been given. Lords amendments may be accepted, changed or reversed, and most duties will commence only through secondary legislation after Royal Assent. NIS2 itself is in force; a Commission proposal to amend it (COM(2026) 13) is still in negotiation.
Key takeaways
- The short answer is no, NIS2 does not apply to UK operations as such. But a UK company that provides in-scope services in the EU falls under NIS2 through the Member State where it operates, and some digital providers must appoint an EU representative under Article 26(3).
- The UK Bill is a targeted extension, not a copy. NIS2 uses a sector list plus a size cap across 18 sectors; the UK keeps designation-based operators of essential services and adds named groups: managed service providers, data centres, large load controllers and designated critical suppliers.
- Both start a 24-hour clock, but the reports differ. NIS2 has an early warning at 24 hours, a notification at 72 hours and a final report within one month; the UK Bill has an initial notification at 24 hours and a full report at 72 hours, sent to the regulator with the NCSC informed at the same time, plus customer notification for providers.
- UK maximum penalties are higher. NIS2 sets floors for national maxima of at least EUR 10 million or 2% (essential) and EUR 7 million or 1.4% (important); the Bill proposes up to £17 million or 4% and £10 million or 2%, whichever is higher.
- One control baseline can serve both. Article 21 measures and the NCSC Cyber Assessment Framework cover the same ground; the work that does not merge is scoping, registration and the reporting runbook.
Does NIS2 apply to UK companies?
NIS2 binds entities by the services they provide in the Union, not by nationality. The tests for a UK-headquartered group are:
- EU subsidiaries: an EU-established subsidiary in an Annex I or II sector that meets the medium-sized threshold is in scope under the law of its Member State. See the NIS2 Transposition Tracker for national status.
- Cross-border digital providers: Article 26(1)(b) puts DNS service providers, TLD name registries, cloud computing, data centre, content delivery network, managed service and managed security service providers, and online marketplaces, search engines and social networks under the jurisdiction of the Member State of their main establishment in the Union.
- No EU establishment: Article 26(3) requires those entities, where they are not established in the Union but offer services there, to designate a representative in the Union, established in one of the Member States where the services are offered.
- UK operations only: a UK entity providing services only in the UK is outside NIS2 and inside the UK NIS regime, today the NIS Regulations 2018 and, after commencement, the regime as amended by the Bill.
The reverse also holds. The Bill applies the relevant managed service provider (RMSP) definition whether or not the provider is established in the UK, and overseas RMSPs must appoint a UK representative, according to the government RMSP factsheet. An EU managed service provider with UK customers therefore needs to check both regimes.
Side-by-side comparison
UK entries reflect the Bill and the government factsheets as updated on 3 November 2026, and can change before Royal Assent.
| Criterion | NIS2 (EU) | UK Cyber Security and Resilience Bill |
|---|---|---|
| Legal form | Directive, transposed by each Member State; national laws applied from 18 October 2024 (Art. 41) | Bill amending the NIS Regulations 2018 (SI 2018/506); most measures commence by regulations after Royal Assent |
| How scope is set | Sector (Annex I and II) plus size: medium-sized and above, with some entity types in scope regardless of size | Designated operators of essential services and relevant digital service providers, plus RMSPs, data centres, large load controllers and designated critical suppliers |
| Tiers | Essential and important entities, same duties, different supervision and fine ceilings | Categories by entity type; two penalty bands set by type of breach, not by entity tier |
| Managed service providers | Annex I sector 9, ICT service management (business to business): managed service providers and managed security service providers | RMSPs: any provider of managed services in the UK that is not a small or micro enterprise |
| Data centres | Annex I sector 8, data centre service providers, subject to the size cap | New data infrastructure sector regulated by Ofcom; rated IT load of 1 MW or more, enterprise data centres at 10 MW or more |
| Suppliers | Supply chain security is a duty of the in-scope entity (Art. 21(2)(d) and 21(3)) | Regulators can designate an individual critical supplier, including a small firm, which then carries duties directly |
| First report | Early warning within 24 hours of becoming aware of a significant incident (Art. 23(4)(a)) | Initial notification within 24 hours of becoming aware: entity name, affected service, brief details |
| Follow-up | Notification within 72 hours; intermediate report on request; final report within one month of the notification | Full report within 72 hours, so far as known |
| Recipient | National CSIRT or competent authority | The regulator, with the NCSC informed at the same time |
| Customers | Recipients of services informed of significant incidents likely to affect them, where appropriate (Art. 23(1)) and of significant cyber threats (Art. 23(2)) | RDSPs, RMSPs and data centres identify customers likely to be adversely affected, notify them and keep them updated |
| Maximum fines | At least EUR 10m or 2% (essential), at least EUR 7m or 1.4% (important), whichever is higher | Up to £17m or 4% (higher band), up to £10m or 2% (lower band), whichever is higher |
| Management | Art. 20: management bodies approve the measures, oversee implementation, can be held liable, and must follow training | The government factsheets describe duties on the regulated entity rather than a separate management body duty; check the final Act |
Scope in depth: MSPs, data centres and suppliers
Managed service providers
NIS2 defines a managed service provider as an entity that provides services related to the installation, management, operation or maintenance of ICT products, networks, infrastructure, applications or other network and information systems, on the customer's premises or remotely (Art. 6(39)). The UK RMSP factsheet uses a narrower contractual test: a service provided under contract for the ongoing management of a customer's IT systems, such as support and maintenance, monitoring or active administration, that connects to or accesses the customer's systems. The UK factsheet expressly excludes firms that install or integrate systems without any later management, software vendors selling products (including ad hoc remote patching), advisory consultancies, OT-only providers, data centre services and public electronic communications providers.
- Threat model both regimes target: standing, privileged, remote access into many customers at once, often through remote monitoring and management tooling.
- Where the scope answers diverge: an integrator that installs and hands over may fall within the NIS2 definition (installation) but outside the UK RMSP definition. A medium-sized SOC provider is in both.
- Size test: NIS2 counts the undertaking with partner and linked enterprises under Recommendation 2003/361/EC; the UK excludes small and micro enterprises. Confirm how each regime counts group headcount and turnover before concluding you are out.
Data centres
NIS2 lists data centre service providers in Annex I; recital 35 says the term should not apply to in-house corporate data centres. The UK takes a capacity-based approach: facilities of 1 MW rated IT load or more, and enterprise data centres run solely for the owner's own IT at 10 MW or more, regulated by Ofcom, with notification to Ofcom within three months of designation and a statutory code of practice. A large enterprise campus can therefore be out of NIS2 (in-house) but in the UK regime (10 MW and above). The data centre sector has its own UK incident reporting criteria, which include impact on the data centre service through a customer's systems.
Suppliers
Under NIS2 the in-scope entity carries supply chain risk through contracts and assessment of each direct supplier. The UK adds a direct lever: a regulator may designate a critical supplier whose disruption would have a significant impact, after consulting it, with appeal to the First-tier Tribunal. A small specialist supplier with no NIS2 exposure can become a regulated UK entity. A separate national security vendor risk framework, added to the factsheets on 3 November 2026, would let government direct operators of essential services about a vendor's goods or services. For supplier controls, see the NIS2 Supply Chain Security Guide.
Incident reporting: two clocks, one event
Both regimes start a 24-hour clock on awareness, but the trigger, content and recipients differ.
| Step | NIS2 Article 23 | UK Bill (incident reporting factsheet) | Runbook action for dual operators |
|---|---|---|---|
| Trigger | Significant incident: severe operational disruption or financial loss, or considerable damage to others | Has adversely affected or is affecting systems, impact has been, is or is likely to be significant, and relates to all or part of the UK | Assess both tests in parallel at triage; record the decision and time for each jurisdiction |
| 24 hours | Early warning, indicating whether unlawful or malicious action is suspected and whether there could be cross-border impact | Initial notification: name, affected service, brief details | Pre-drafted templates per jurisdiction sharing one fact sheet |
| 72 hours | Notification updating the early warning with an initial assessment, severity, impact and indicators of compromise where available | Full report: when it occurred, whether ongoing, nature, whether caused by another regulated entity, actual or likely impact | One incident record feeds both; reconcile facts before sending |
| Later | Intermediate report on request; final report within one month of notification, or progress report if ongoing | Further significance thresholds to come in secondary legislation and regulator guidance | Track the NIS2 one-month deadline as a separate ticket |
| Customers | Inform affected service recipients where appropriate | RDSPs, RMSPs and data centres notify affected customers and keep them updated | Maintain one customer-to-service map covering both regions |
Personal data breaches add a third clock under GDPR in the EU and UK GDPR in the UK, each to its own regulator. See the EU Incident Reporting Clocks and the Cyber Incident Reporting Requirements Map.
Worked scenario: an MSP headquartered in Manchester with a Dublin subsidiary detects ransomware staging on its remote management platform at 09:00, before any encryption. Under the UK Bill, ransomware pre-positioning is described in the factsheet as in scope, so the UK entity decides by early afternoon whether the impact is likely to be significant and sends an initial notification to the Information Commission, with the NCSC informed, within 24 hours. The Irish subsidiary assesses the NIS2 significance test for its own customers; if met, it sends an early warning to the Irish CSIRT within 24 hours. Both entities identify affected customers.
Penalties, supervision and management accountability
| Aspect | NIS2 | UK (today and under the Bill) |
|---|---|---|
| Fine ceilings | Member States set maxima of at least EUR 10m or 2% (essential) and EUR 7m or 1.4% (important) of worldwide turnover (Art. 34(4) and (5)); national laws may go higher | Today: three bands of £1m, £8.5m and £17m. Bill: up to £17m or 4% (security and incident notification duties) and up to £10m or 2% (for example, failing to register), whichever is higher |
| Turnover basis | Total worldwide annual turnover of the undertaking in the preceding financial year | Meaning of undertaking and turnover to be set in secondary legislation after consultation |
| Supervision style | Proactive for essential entities (Art. 32), after the fact for important entities (Art. 33) | Sector regulators (for example Ofcom for digital and data infrastructure, the Information Commission for RDSPs and RMSPs) with cost recovery through charging schemes |
| Individuals | Management bodies can be held liable; temporary bans on managerial functions for essential entities as a last resort (Art. 32(5)) | Enforcement aimed at the regulated entity; appeals to the First-tier Tribunal |
For NIS2 board duties, see the NIS2 Management Liability Executive Briefing. A UK board should still adopt the NIS2 approval and training record across the group: it costs little and gives UK regulators the same evidence of oversight.
One control set for both: a mapping
The substantive security duties converge. UK competent authorities mostly assess operators against the NCSC Cyber Assessment Framework (CAF), whose four objectives cover managing security risk, protecting against cyber attack, detecting events and minimising impact. NIS2 Article 21(2) lists ten minimum measures. A single control catalogue mapped to both, with evidence held once, removes most duplicate effort.
| NIS2 Art. 21(2) | NCSC CAF objective and principle | NIST CSF 2.0 | ISO/IEC 27001:2022 Annex A |
|---|---|---|---|
| (a) Risk analysis and security policies | A1 Governance, A2 Risk management | GV.RM, ID.RA | A.5.1 |
| (b) Incident handling | D1 Response and recovery planning | RS.MA, RS.CO | A.5.24 to A.5.26 |
| (c) Business continuity and crisis management | B5 Resilient networks and systems, D1 | RC.RP | A.5.29, A.5.30 |
| (d) Supply chain security | A4 Supply chain | GV.SC | A.5.19 to A.5.22 |
| (e) Secure acquisition, development, vulnerability handling | B4 System security | ID.RA, PR.PS | A.8.8, A.8.25 to A.8.29 |
| (f) Assessing effectiveness | A2 Risk management, D2 Lessons learned | ID.IM | A.5.35, A.5.36 |
| (g) Cyber hygiene and training | B6 Staff awareness and training | PR.AT | A.6.3 |
| (h) Cryptography | B3 Data security | PR.DS | A.8.24 |
| (i) HR security, access control, asset management | A3 Asset management, B2 Identity and access control | ID.AM, PR.AA | A.5.9, A.5.15 to A.5.18, A.6.1 |
| (j) MFA and secured communications | B2 Identity and access control | PR.AA | A.8.5 |
For deeper crosswalks, see the ISO 27001 to NIS2 and DORA Mapping Guide and the NCSC Cyber Assessment Framework (CAF) Guide. For digital providers, NIS2 Implementing Regulation (EU) 2024/2690 adds detailed technical requirements; see the NIS2 Implementing Regulation 2024/2690 Guide.
Where identity fits
Both regimes put MSPs in scope for the same reason: provider identities with standing admin rights into customer estates. NIS2 Article 21(2)(j) names multi-factor or continuous authentication, and CAF principle B2 covers identity and access control. For a dual operator the practical baseline is the same in both places: phishing-resistant MFA for technicians, separate administrative identities per customer tenant, just-in-time elevation, vaulted API keys and service account credentials for RMM and automation, and full session logging. The UK government also plans to consult on agentic AI resilience measures under the Bill's powers, covering monitoring of AI agents' actions and evidence preservation after agent-caused incidents, so agent identities belong in the same inventory. See the RMM Tool Security Guide and the Third-Party Access Guide.
How to run a dual-jurisdiction programme
- Map entities to regimes. List every legal entity, the services it provides and where. Tag each as NIS2 essential, NIS2 important, UK OES, RDSP, RMSP, data centre, or out of scope, with the reasoning and the date.
- Settle jurisdiction and representatives. For Article 26 entity types, identify the EU main establishment or appoint an EU representative; for RMSPs without UK establishment, plan a UK representative and Information Commission registration within three months of commencement.
- Build one control catalogue. Map controls to Article 21 and the CAF using the table above; assess once, with evidence tagged to both.
- Write one reporting runbook with two branches. A shared triage and fact log, then jurisdiction-specific significance tests, templates, recipients and deadlines. Include customer notification.
- Exercise it. Run a tabletop where one incident hits both regions and measure time to each decision. See the Tabletop Exercise Guide.
- Keep current processes live. Until UK commencement regulations are made, the NIS Regulations 2018 72-hour duty still applies to OES and RDSPs; run the 24-hour step as good practice alongside it rather than replacing it.
- Track change. Watch the Commons consideration of Lords amendments, UK consultations on thresholds and turnover, national NIS2 transposition, and the NIS2 amending proposal. See the NIS2 Amending Directive Proposal 2026.
Decision guidance
- UK-only MSP, no EU customers: plan for the RMSP regime if medium or large; NIS2 does not apply.
- UK MSP with EU customers but no EU establishment: NIS2 Article 26(3) representative duty applies to managed service providers offering services in the Union; take legal advice on which Member State.
- EU group with UK data centres: check the 1 MW and 10 MW tests; enterprise facilities excluded from NIS2 can be in UK scope.
- Small specialist supplier: NIS2 size cap likely excludes you, but a UK regulator may designate you as a critical supplier; prepare contract-ready evidence.
Measuring readiness
- Percentage of legal entities with a dated scope decision for both regimes.
- Median time from detection to each jurisdiction's notification decision in exercises (target well under 24 hours).
- Percentage of controls with evidence tagged to both Article 21 and a CAF principle.
- Percentage of customers mapped to services and entities (for customer notification in both regions).
- Percentage of critical suppliers with incident notification clauses that meet the shorter of the two clocks.
Common failure patterns
- Assuming one programme fits both: controls converge, but scoping and reporting do not. A team that copies the NIS2 early warning template to the UK regulator misses the UK customer notification step.
- Treating the UK Bill as UK NIS2: NIS2 sector breadth (manufacturing, food, postal, research) has no UK counterpart in the Bill; UK designation of individual suppliers has no NIS2 counterpart.
- Using the wrong MSP definition: integrators and software vendors can sit inside one definition and outside the other.
- Waiting for Royal Assent: the 24-hour decision rights, contacts and customer maps take months; supply chain compromise through providers, as in the Marks and Spencer cyberattack, is exactly what both regimes target.
- Ignoring group turnover: NIS2 fines reference undertaking turnover, and the UK definition is still to be set.
Practitioner checklist
- Record the UK Bill's stage and the date checked; re-check when the Commons considers Lords amendments and at Royal Assent.
- Produce a dated entity-by-regime scope register covering NIS2 tiers and UK categories.
- Confirm EU main establishment or representative under Article 26 and plan any UK representative.
- Maintain one control catalogue mapped to Article 21(2)(a) to (j) and CAF principles.
- Build one incident runbook with jurisdiction branches, templates and named reporting owners.
- Keep the NIS Regulations 2018 72-hour process live until UK commencement.
- Map customers to services in both regions for customer notification.
- Update supplier contracts to the 24-hour clock and assess designation risk for critical suppliers.
- Include technician, service account and AI agent identities in the privileged access inventory.
Standards and references
- EUR-Lex: Directive (EU) 2022/2555 (NIS2 Directive)
- UK Parliament: Cyber Security and Resilience (Network and Information Systems) Bill, stages
- UK Parliament: Cyber Security and Resilience (Network and Information Systems) Bill
- GOV.UK: Cyber Security and Resilience Bill factsheets
- GOV.UK: Incident reporting factsheet
- GOV.UK: Relevant managed service providers factsheet
- GOV.UK: Enforcement factsheet
- GOV.UK: Data centres factsheet
- VinciWorks: Lords Report stage amendments (29 October 2026)
- ISACA: Five takeaways from Lords Report stage (5 November 2026)
This guide summarises NIS2 and the UK Cyber Security and Resilience Bill as at 14 November 2026 and is not legal advice. Related NHI Mgmt Group resources: NIS2 Directive Guide · UK Cyber Security and Resilience Bill Guide · Global Cybersecurity Regulatory Map · NIS2 vs Cyber Resilience Act · UK GDPR vs EU GDPR