The Cyber Security and Resilience (Network and Information Systems) Bill is the UK government’s update to the NIS Regulations 2018. It would bring medium and large managed service providers, data centres, large load controllers and designated critical suppliers into regulation, introduce 24-hour incident reporting and raise maximum fines. As at 10 November 2026 it is still a Bill, not an Act.
The Bill matters well beyond the organisations it names. Managed service providers and data centres sit underneath almost every UK business, so their new duties will show up in your contracts, your supplier reviews and the incident notifications you receive. This guide covers where the Bill has reached, what it changes and who should be preparing now.
Executive Summary & Key Takeaways
- The Bill is in the House of Lords. Report stage is scheduled for 26 October 2026, and it has not received Royal Assent.
- Medium and large managed service providers (MSPs) will be regulated for the first time, by the Information Commission (the ICO).
- Regulators will be able to designate critical suppliers, including small and micro businesses, if their failure could cause significant disruption.
- Regulated organisations will need to send an initial incident notification within 24 hours and a full report within 72 hours.
- Most duties will only start once secondary legislation is made after Royal Assent, so there is time to prepare, but not unlimited time.
Where the Bill is in Parliament
The Bill was introduced in the House of Commons on 12 November 2025 and had its second reading on 6 January 2026, when a carry-over motion was also agreed. It was carried over and reintroduced in the new session on 14 May 2026, completed its Commons report stage and third reading on 16 June 2026, and had its Lords second reading on 14 July 2026. Lords Committee stage took place in Grand Committee on 1, 3 and 7 September 2026, and Lords Report stage is scheduled for 26 October 2026 (UK Parliament, retrieved 10 November 2026).
After Report stage the Bill still needs a Lords third reading, Commons consideration of any Lords amendments and Royal Assent. Until then its text can change, so treat everything below as the government’s stated intent rather than settled law.
Royal Assent will not switch everything on at once. The government says future-proofing powers will apply from day one, the statement of strategic priorities and information sharing from month two, and the measures most businesses care about, including the MSP, data centre, critical supplier and incident reporting provisions, through later secondary legislation. The government has said it intends to consult on implementation proposals in 2026 and will give affected organisations an adjustment period (GOV.UK, retrieved 10 November 2026).
What the Bill changes
The current NIS Regulations cover operators of essential services in energy, transport, health, drinking water and digital infrastructure, plus some digital services such as online marketplaces, search engines and cloud computing. The Bill keeps that federated model, with sector regulators, and adds new groups.
| model | What it means | Regulator |
|---|---|---|
| Managed service providers | Medium and large providers of ongoing IT management for business customers | Information Commission (ICO) |
| Data centres | Data infrastructure becomes a NIS sector; data centres above capacity thresholds become essential services | Ofcom |
| Large load controllers | Organisations managing electrical load for smart appliances, such as EV charging | DESNZ and Ofgem |
| Designated critical suppliers | Suppliers whose disruption could significantly affect the economy or society | The regulator of the entity they supply |
Source: GOV.UK, retrieved 10 November 2026.
The ICO’s functions passed to the new Information Commission on 30 September 2026, though it continues to be known as the ICO (GOV.UK, retrieved 10 November 2026).
The Bill also gives the Secretary of State powers to set strategic priorities for regulators, to add sectors and update security requirements through secondary legislation, and to direct regulators or regulated entities in response to national security threats.
Who will it affect?
Managed service providers
This is the largest new group. A “relevant managed service provider” is one that provides managed services in the UK, whether or not it is established here, and is not a small or micro enterprise. A managed service means ongoing management of a customer’s IT systems under contract, through a connection to or access to those systems, whether on site or remote (GOV.UK, retrieved 10 November 2026).
The government’s examples make the line clearer. In scope: outsourced IT support and helpdesks, managed firewalls, intrusion detection and incident response, security operations centre services, and ongoing configuration and monitoring of a customer’s cloud service. Out of scope: business consultancy delivered by email, phone or meetings, one-off installation with no ongoing management, and software sold as a product, even with occasional remote patches.
In-scope MSPs will need to register with the regulator within three months of the provisions commencing, appoint a UK representative if based overseas, take appropriate and proportionate security measures and report significant incidents.
Data centres and critical suppliers
Data centre operators above the defined thresholds will have to notify Ofcom, implement proportionate security and resilience measures and report incidents, including those affecting the continuity of the data centre service.
Critical supplier designation is the measure most likely to surprise smaller businesses. A regulator can designate a supplier that provides goods or services directly to a regulated organisation, relies on network and information systems to do so, and whose disruption could have a significant impact on the economy or day-to-day life in the UK. Small and micro businesses are exempt from the MSP measure but can still be designated (GOV.UK, retrieved 10 November 2026).
Customers of regulated suppliers
Most organisations will feel the Bill second-hand. The government has committed to setting out, in secondary legislation, duties on regulated entities to manage supply chain risk, such as contractual requirements, security checks and continuity plans (GOV.UK, retrieved 10 November 2026). Expect your MSP, data centre and cloud contracts to change, and expect to be told when an incident at a supplier has likely affected you.
Financial services is not one of the NIS sectors. The government says the Bill will sit alongside sector regimes such as the Financial Services and Markets Act 2023. But a bank or insurer that outsources IT to an in-scope MSP will still see the effects through that supplier.
Incident reporting and penalties
Today, regulators generally hear about incidents only once they have caused significant disruption. The Bill widens reporting to incidents that are likely to have a significant impact, such as ransomware or attackers pre-positioning in a network, even before services are affected. Regulated organisations will send a light-touch initial notification to their regulator within 24 hours of becoming aware of an incident, with the NCSC informed at the same time, followed by a fuller report within 72 hours. Data centres, MSPs and digital service providers will also need to tell customers who have likely been affected (GOV.UK, retrieved 10 November 2026). The thresholds for what counts as significant will be set in secondary legislation.
Penalties move to two bands: up to £17 million or 4% of worldwide turnover, whichever is higher, for more serious breaches, and up to £10 million or 2% for less serious ones. The current maximum is £17 million. How turnover is defined will be set in secondary legislation (GOV.UK, retrieved 10 November 2026).
This sits alongside, not instead of, other reporting duties. A personal data breach still needs assessing under UK GDPR, and organisations with EU operations may also face NIS2 timelines.
What to do before the rules commence
You do not need to wait for secondary legislation to make sensible decisions. The work that pays off under any final wording is:
- Scoping. Decide whether you are likely to be a relevant MSP, a data centre above threshold, or a candidate for critical supplier designation, and record the reasoning.
- Incident readiness. Check that your process could produce a short notification within 24 hours of becoming aware of an incident, and that you know who would make the call.
- Supplier visibility. Identify which of your own suppliers are likely to come into scope, and which contracts will need updating.
- Evidence. Gather the policies, test results and control evidence a regulator or customer would ask for.
Common mistakes
- Assuming “not law yet” means “nothing to do”. Customers are already asking MSPs and data centres how they will comply, and procurement cycles are longer than the commencement timetable.
- Confusing consultancy with managed services. The test is ongoing management through access to the customer’s systems, not the label on the contract.
- Assuming small means safe. Small and micro businesses are excluded from the MSP measure but can still be designated as critical suppliers.
- Building a separate incident process. One process that captures the right facts early can serve the new NIS timelines, UK GDPR and any sector regime.
Frequently asked questions
When will the new duties actually apply?
Not until after Royal Assent and, for most measures, not until the relevant secondary legislation is made. The government has said it will consult first and give organisations an adjustment period, but has not published commencement dates for the main duties.
We are a small MSP. Are we exempt?
Small and micro enterprises are outside the managed service provider measure. However, a regulator can still designate you as a critical supplier if you meet the designation conditions, and your regulated customers are likely to pass security requirements down to you in contracts.
Does the Bill cover cyber security providers?
Ongoing managed security services, such as firewall management, intrusion detection, security monitoring and incident response delivered through a connection to the customer’s systems, are among the government’s in-scope examples. Advisory work delivered without ongoing management of the customer’s systems is not.
Will we have to report the same incident to several bodies?
Possibly. The Bill sends notifications to your NIS regulator with the NCSC informed at the same time. A personal data breach may separately need reporting to the ICO, and sector regulators such as the FCA have their own rules. Plan one process that feeds each of them.
Getting started
The Bill is still moving through Parliament, but its direction is clear: more of the supply chain regulated, faster reporting and higher penalties. If you think you are in scope, or your customers are already asking, our NIS2 and UK NIS regulation team can help you confirm scope and build evidence that works for both regimes. Our guide to third-party cyber risk covers the supplier side. For a view on your position, talk to our team.

Jared Henderson
Writing about cyber security and technology at Falx.





