NIS2 UK is not a domestic law: the EU’s Directive (EU) 2022/2555 (NIS2) differs from the UK’s Network and Information Systems Regulations 2018, which took effect on 10 May 2018 UK legislation. For NIS2 UK planning, sector regulators oversee organisations covered by the UK rules. Certain UK providers offering services in the EU may also face NIS2 duties EU directive. As at 30 October 2026, the UK’s proposed reform Bill had not received Royal Assent UK Parliament.
- Scope: Current UK duties cover specified essential and digital services; EU NIS2 may separately apply to UK organisations with covered EU activities.
- Dates: The UK NIS regime is in force. Proposed changes under the Cyber Security and Resilience Bill have no commencement date while it remains a Bill UK Parliament.
- Regulators: Covered UK organisations report to their relevant regulator. The Bill would assign managed service providers to the Information Commission and qualifying data centres to Ofcom UK government guidance data centre factsheet.
- Changes: The Bill would widen UK coverage and introduce earlier incident notification. Those proposed duties must not be mistaken for current UK law.
- Penalties: The current UK maximum is £17 million. The Bill proposes a revised structure with turnover-sensitive maximums enforcement factsheet.
- Outside scope: A UK location alone does not trigger NIS2, and supplying an organisation covered by UK NIS does not automatically bring its suppliers into scope.
📜 NIS2 UK: is the EU directive law here?
No. NIS2 UK is not a separate UK compliance regime. NIS2 is an EU directive, while the binding UK cross-sector regime is the Network and Information Systems Regulations 2018. The UK government intends to reform those regulations through the Cyber Security and Resilience (Network and Information Systems) Bill, not transpose NIS2 wholesale UK government Bill summary.

The distinction matters when someone asks a UK board for a NIS2 compliance plan. For NIS2 UK assessments, we first establish which legal entity provides which service, where it provides that service and which regulator has jurisdiction. A UK operator may have duties under the existing UK regulations, NIS2 as implemented in an EU country, both regimes or neither. Similar security measures do not make the legal tests interchangeable.
What is binding in the UK?
The current UK regulations require covered organisations to take appropriate and proportionate measures to protect their network and information systems. They must report incidents that significantly disrupt their services to the relevant regulator UK government Bill summary. The proposed Bill would add duties, but Parliament still listed it as a Bill rather than an Act at its latest stated update UK Parliament.
For a board paper, separate current obligations from proposed changes in different columns. That simple discipline prevents an EU deadline from being presented as a UK deadline, or a proposed UK duty from being treated as already enforceable. Our earlier UK reform Bill overview provides background, but the Bill’s latest parliamentary status remains the deciding point.
Check the UK regulations and any applicable EU national rules separately. Similar requirements do not mean NIS2 has become UK law.
🗓️ Which UK organisations are covered, and when might EU NIS2 apply?
In a NIS2 UK assessment, current UK coverage depends on the service an organisation provides, not simply its industry label or size. The regulations cover operators involved in essential services and certain digital services, including online marketplaces, online search engines and cloud computing services UK government Bill summary. Organisations should test their actual services against the relevant UK definitions and regulator.

A supplier does not automatically become directly regulated because its customer is covered. Contractual security and incident obligations can still apply, and the supplier may independently qualify under another category. NIS2 UK scope questions often arise for managed service providers because the UK Bill proposes bringing medium and large providers meeting its Relevant Managed Service Provider (RMSP) definition into the regime managed service provider factsheet. That is a proposed expansion, not a current general rule for managed services.
UK companies with EU services
EU exposure needs a separate assessment. The European Commission describes NIS2 as covering medium and large organisations in specified sectors as a general rule, with risk-management and incident-reporting duties for covered entities European Commission NIS2 overview. A UK company cannot assume it is outside EU rules merely because its head office is in Britain. Equally, having EU customers does not, by itself, establish that NIS2 applies.
Article 26 of NIS2 addresses jurisdiction for specified digital and information technology service providers. Certain providers outside the EU that offer services within it must designate an EU representative NIS2 directive. Review the service category, where the entity is established and the national rules applying to its EU operations before deciding whether registration, representation or reporting is required.
⏳ When do the current and proposed UK rules apply?
The Network and Information Systems Regulations 2018 are already in force; the proposed UK reforms are not. NIS2 UK planning therefore needs two tracks: meet any present UK duties now, then monitor the Cyber Security and Resilience Bill for enacted text and commencement arrangements. Parliament’s latest stated update still showed the measure awaiting Royal Assent UK Parliament.

A Bill can change before enactment. Even after Royal Assent, individual provisions may depend on commencement arrangements. No organisation should turn the proposed notification periods or newly proposed provider categories into a binding UK deadline yet. Boards can approve preparatory work without presenting an uncommenced requirement as law.
EU changes also need status checks
The European Commission proposed targeted amendments to NIS2 on 20 January 2026 and described them as proposals, not adopted changes European Commission NIS2 overview. That proposal is separate from both the existing EU directive and the UK Bill. An organisation operating across borders should record which rule applies in each jurisdiction and the version used for its assessment.
We recommend keeping a dated legal obligations register with an owner for each relevant service and entity. Record whether a requirement is in force, proposed or awaiting commencement, then check it when the law changes. The register gives incident responders and directors one agreed position instead of competing interpretations drawn from a policy draft, a supplier questionnaire or an old board presentation.
Prepare for proposed reform, but enforce current duties against the law in force rather than an expected commencement date.

🧩 What would the Cyber Security and Resilience Bill change?
The Bill would expand who is regulated and change incident reporting under the existing UK NIS framework. Its proposals include qualifying data centres, certain managed service providers and earlier notification of reportable incidents. Until enacted and commenced, organisations must distinguish these proposals from the obligations that already apply.
| Area | Current UK position | Bill proposal | Practical preparation |
|---|---|---|---|
| Managed services | Managed services are not generally regulated as such under UK NIS. | Bring medium and large providers meeting the RMSP definition into scope managed service provider factsheet. | Map services and assess whether the proposed definition fits. |
| Data centres | No general minimum cyber security or operational resilience requirements apply to data centres under this regime. | Designate qualifying data centres as essential services, with Ofcom as operational regulator data centre factsheet. | Identify facilities, operators and dependencies. |
| Incident reporting | Qualifying incidents are generally notified to the regulator within 72 hours after awareness. | Add an initial notification within 24 hours and a full report within 72 hours incident reporting factsheet. | Test alert escalation and evidence collection. |
| Customer notification | Assess existing duties according to the service and contract. | Require specified data centre and service providers to tell customers about breaches likely to affect them incident reporting factsheet. | Identify customer contacts and approval owners. |
The proposed customer notification duty deserves particular attention. Reporting to a regulator and informing customers are different decisions, with different audiences and operational consequences. Our cyber risk assessment guidance explains how to identify service dependencies before a reporting question becomes urgent. For NIS2 UK planning, map those dependencies to each legal entity rather than treating a group-wide security policy as proof that every service is covered.
📌 NIS2 UK reporting deadlines: which clock applies?
The applicable reporting clock depends on the regime and whether an incident meets its notification test. Under the current UK approach, a qualifying incident is generally notified to the regulator within 72 hours of awareness. The UK Bill proposes an initial notification within 24 hours and a full report within 72 hours incident reporting factsheet.
Those proposed UK notices would go to the relevant regulator, with the National Cyber Security Centre (NCSC) receiving incident information at the same time. The Bill would also capture certain harmful events likely to have substantial UK effects before service disruption occurs incident reporting factsheet. Response plans should therefore assess both observed disruption and the likely effect of a developing incident.
The EU sequence is different
For a significant incident under NIS2, Article 23 requires an early warning within 24 hours of awareness, an incident notification within 72 hours and a final report no later than one month after that notification NIS2 directive. Those EU requirements are not the current UK reporting timetable. A UK entity with EU duties needs a jurisdiction-specific escalation route, not one generic deadline in its incident plan.
We would define who confirms awareness, who assesses reportability and who can submit a notice if the usual approver is unavailable. Record the facts known at each decision point; an initial report need not pretend that an investigation is finished. Rehearse communication between security, legal, operations and customer teams so evidence can be gathered while the organisation contains the incident.
🚨 What are the penalties and who enforces the rules?
UK NIS enforcement sits with the relevant regulator, and the current maximum financial penalty is £17 million. The Cyber Security and Resilience Bill proposes a simpler two-band structure and maximums that take regulated entities’ turnover into account enforcement factsheet. Its proposed penalty model is not an enacted replacement for the current cap.
For newly proposed UK categories, the Information Commission would regulate RMSP duties, while Ofcom would act as operational regulator for qualifying data centres managed service provider factsheet data centre factsheet. Existing operators must identify their present sector regulator. A provider should not assume that the regulator handling its personal data obligations also handles every NIS duty.
Do not import EU fines into UK advice
NIS2 Article 34 requires EU member states to provide maximum fines for essential entities of at least €10 million or 2 per cent of worldwide annual turnover, whichever is higher NIS2 directive. That is an EU requirement, not the current UK NIS penalty. The fine applicable to an EU operation depends on the relevant national rules and the entity’s classification.
Penalty exposure is only one reason to document decisions. Regulators also need to understand what an organisation knew, how it assessed risk and what it did to protect the service. Under the UK Bill’s proposals, mitigating action and patterns of non-compliance would inform proportionate penalty decisions enforcement factsheet. Keep records that show how controls work in practice, not just when a policy was approved.
📋 How should UK organisations prepare for NIS2 and UK reform?
Start with a service-by-service scope assessment, then prepare incident reporting and risk controls against the rules that actually apply. For NIS2 UK planning, keep the EU and UK assessments separate. A single group policy may support both sides of NIS2 UK planning, but it cannot answer distinct questions about jurisdiction, service definitions, regulators and notification duties.

- List each legal entity, the services it provides, the countries it serves and the systems those services depend on.
- Identify current UK NIS duties, possible EU NIS2 duties and proposed UK Bill duties in separate entries.
- Assign an owner for security measures, incident classification, regulator contact and customer communication.
- Test how an incident moves from detection to legal assessment, management approval and an accurate notification.
- Retain evidence of decisions, control operation, exercises and improvements rather than relying on policy statements alone.
For specified EU digital infrastructure and service providers, Commission Implementing Regulation (EU) 2024/2690 sets out detailed risk-management requirements in its annex EU implementing regulation. The European Union Agency for Cybersecurity publishes guidance with practical advice and examples of implementation evidence EU technical guidance. Neither document turns the EU requirements into UK domestic law.
Our cyber security strategy work can help turn a scope decision into owned controls and an improvement plan. ISO 27001 consultancy can support a documented management approach, but certification does not establish NIS2 or UK NIS compliance by itself. For operational measures, the UK cyber protection guide offers a useful starting point. Legal classification still comes first.
Map entities, services and jurisdictions before selecting a control framework or setting an incident-reporting deadline.
❓ Frequently asked questions
Does NIS2 apply in the UK after Brexit?
NIS2 is not UK domestic law after Brexit. Covered UK organisations must assess the Network and Information Systems Regulations 2018, while organisations with specified EU activities may separately have NIS2 duties under applicable EU national rules UK legislation NIS2 directive. For NIS2 UK questions, location alone does not settle the issue; the service and jurisdiction matter.
What is the UK equivalent of NIS2?
The closest existing cross-sector UK regime is the Network and Information Systems Regulations 2018. The Cyber Security and Resilience Bill proposes to reform and extend that regime rather than copy NIS2 directly UK government Bill summary. Some measures resemble EU requirements, but organisations should assess the UK definitions, regulators and reporting tests on their own terms.
When will the Cyber Security and Resilience Bill become law?
No enactment or commencement date should be assumed. Parliament still listed the measure as a Bill at its stated update on 30 October 2026 UK Parliament. Royal Assent and any applicable commencement arrangements must be checked before treating its new duties as binding. Existing UK NIS obligations continue to apply in the meantime.
Do UK managed service providers need to comply with NIS2?
Not solely because they provide managed services from the UK. The UK Bill proposes bringing medium and large providers meeting its RMSP definition into domestic NIS scope managed service provider factsheet. A provider may also need an EU NIS2 assessment if it offers a covered service there, or a current UK assessment if it independently provides an already regulated digital service.
Does a UK company need an EU representative for NIS2?
Some do, but not every UK company with EU customers. Article 26 requires certain covered digital and information technology service providers outside the EU that offer services within it to designate an EU representative NIS2 directive. Check the precise service category, establishment and applicable jurisdiction before appointing one or deciding the requirement does not apply.
Are the NIS2 reporting deadlines already binding on UK operators?
No. NIS2’s EU reporting sequence is not automatically a UK duty. The current UK regime generally requires notification of a qualifying incident to the regulator within 72 hours of awareness; the UK Bill proposes an earlier initial notice within 24 hours incident reporting factsheet. An operator with separate EU duties must assess those deadlines independently.
What fines apply if an organisation breaches NIS2?
The answer depends on which law and entity are involved. The current UK NIS maximum is £17 million, while proposed UK reforms would change the penalty structure enforcement factsheet. EU NIS2 sets minimum requirements for the maximum fines available under member states’ rules. Those EU thresholds should not be presented as current UK penalties.
Contact Us












