Skip to main content
Compliance

Cyber Security and Resilience Bill: What MSPs Need to Know

What the UK Cyber Security and Resilience Bill means for MSPs: who is in scope, the duties to expect, a scoping checklist and what to do now.

G
GetCybr vCISO Notes
··9 min read
MSP security lead reviewing UK Cyber Security and Resilience Bill scope and incident reporting duties for client services

Key Takeaways

The UK Cyber Security and Resilience (Network and Information Systems) Bill would bring medium and large managed service providers into the scope of the NIS Regulations 2018, with the Information Commission as regulator. As of 21 November 2026 it is still a Bill. This guide sets out, from the official government and Parliament sources, who would be in scope, the duties the government expects to apply (registration, incident reporting, security measures), a checklist for working out whether your practice is a relevant managed service provider, and practical steps to take before the detail is set in secondary legislation.

If you run managed IT or managed security for UK customers, the Cyber Security and Resilience (Network and Information Systems) Bill is the first UK legislation that would regulate your business as an MSP. It is still a Bill, and much of the detail is yet to be written. This guide sets out what the official sources say today, what they leave open, and what a sensible practice can do before the rules are final.

At a glance

  • Status as of 21 November 2026: a Bill, not law. Parliament’s record lists Lords third reading on 2 November 2026 and Commons consideration of Lords amendments on 24 November 2026. Royal Assent is not shown.
  • Regulator for MSPs: the Information Commission (formerly the Information Commissioner’s Office).
  • Who is in scope: medium and large managed service providers that meet the definition of a “relevant managed service provider”. Small and micro enterprises are exempt unless designated as critical suppliers.
  • What changes compared with the NIS Regulations 2018: MSPs, which are not currently regulated as a class, would be brought in. Incident reporting widens, with a 24-hour initial notification and a 72-hour fuller report. Relevant MSPs would also have to tell affected customers.
  • What is still open: the detailed security requirements and the incident thresholds, which the government says will come in secondary legislation after consultation.

What the Bill does

The Bill reforms and adds to the Network and Information Systems (NIS) Regulations 2018. The government’s summary groups the changes under three pillars. The one that matters most to MSPs is expanded scope. In the government’s words, cyber criminals are exploiting “managed service providers, data centres and critical parts of supply chains” to reach the organisations those firms serve, and the summary says “medium and large managed service providers will be brought into scope”.

Other changes in the same Bill affect MSPs indirectly:

  • Incident reporting widens. More forms of harmful breach would have to be reported to regulators where they have the potential to cause significant impacts, with “initial notification within 24 hours and a fuller report within 72 hours”, and the NCSC informed at the same time.
  • Critical suppliers. Regulators would be able to designate critical suppliers to essential and digital services. The government compares this to the critical third parties regime in financial services.
  • Enforcement and cost recovery. The summary says the maximum financial penalty will be amended and that regulators will be able to recover the costs of their NIS duties. It does not give penalty figures in the pages we read, so this guide does not either.
  • Future-proofing. The government is taking powers to change the regime in secondary legislation, for example by bringing more sectors into scope or updating security requirements.

Which MSPs are in scope

The government’s factsheet on relevant managed service providers says the Bill will define one as “a person who provides managed services in the UK (whether or not the person is established in the UK) and is not a small and micro enterprise”. It adds that entities subject to public authority oversight and “deriving less than half their income from activities of a commercial nature” are exempted.

“Managed services” are defined by reference to a contract for “ongoing management of information technology systems for the customer”, where the provider is “connecting to or otherwise obtaining access to network and information systems relied on by the customer”. It does not matter whether that access is on the customer’s premises or remote. The factsheet says this can include IT outsourcing such as remote support, helpdesks and management of applications, and managed security services such as a security operations centre or SIEM.

The factsheet also gives examples of services that would not count: a software company selling software as a product, even where it provides ad-hoc patch updates remotely; a company that installs or integrates systems but does not manage them afterwards; and a consultancy giving business advice by email, phone or in person.

Small and micro enterprise MSPs are exempt from this measure, but the factsheet says they “can be designated as critical suppliers, provided that they meet the conditions for designation”. So a small MSP that is important to an essential service should not assume it is out of reach.

Duties MSPs should expect

As the factsheet describes them, relevant managed service providers would have to:

  • Register with the Information Commission, giving the entity’s name, contact information and an address for service of documents, and appoint a UK representative if based overseas. The factsheet says that once the regulations are commenced a relevant MSP “will have three months to register”.
  • Manage security risk. Take appropriate and proportionate measures to manage risks to the networks and information systems the managed service relies on, and to prevent and minimise the impact of incidents. The level of security must be proportionate to the risk, having regard to the state of the art.
  • Report significant incidents to the Information Commission. The incident reporting factsheet gives three criteria: the incident has adversely affected the operation or security of the systems relied on to provide the managed service; its impact is or is likely to be significant; and it relates to the whole or part of the UK.
  • Tell customers. After a full notification, relevant MSPs would have to identify customers likely to have been adversely affected, notify them, and keep them updated for the duration of the incident.

Two things are not yet fixed. The factsheet says “additional security and resilience requirements” and the “thresholds at which an incident will be considered to have had a significant impact” will come through secondary legislation, introduced at the same time as commencement. The government has also said a business adjustment period will be communicated before new or updated duties come into force. This guide gives no commencement date because the official pages do not.

Are you a relevant managed service provider?

These are scoping questions, not legal conclusions. Answer them for each service line, because the factsheet judges a service rather than a whole firm.

  • Do you provide services to UK customers under a contract, whether or not your company is established in the UK?
  • Does the contract cover the ongoing management of a customer’s IT systems, such as support and maintenance, monitoring or active administration?
  • Do you connect to, or otherwise obtain access to, the customer’s networks or systems, on site or remotely?
  • Do you only sell software, run one-off installations or give advice, with no ongoing management afterwards?
  • Is your business a small or micro enterprise under the definition in the Bill, and have you checked that definition with an adviser?
  • Are you subject to public authority oversight and do you earn less than half your income from commercial activities?
  • If you are small, could a customer that supplies an essential service rely on you enough for a regulator to consider designating you as a critical supplier?

If you answer yes to the first three and the exemptions do not clearly apply, treat the service line as likely to be in scope and plan accordingly.

What to do now

Nothing here is a requirement yet. These steps are sensible preparation, and each is useful whatever the final rules say.

  1. Map your managed services. List each contracted service, the customers it covers and the access path you use to reach their systems. The definition turns on ongoing management and access, so this map is the evidence for a scoping decision.
  2. Check the size test. Establish whether the practice is medium or large, or small or micro, using the definition in the Bill text rather than a rule of thumb, and record who reviewed it.
  3. Rehearse incident reporting. Decide who judges whether an incident is significant, who sends a 24-hour notification, who prepares a 72-hour report and who tells affected customers. A tabletop exercise against your own tooling, such as RMM and PSA platforms, will show the gaps.
  4. Self-assess against a recognised framework. The NCSC Cyber Assessment Framework is an outcomes-based framework that was “originally developed to support cyber oversight and regulatory activities” and can also be used by any organisation seeking a structured approach to cyber risk. The factsheets we read do not say which framework the Information Commission will use for MSPs, so treat the CAF as a structure to practise against, not as the stated standard.
  5. Review supplier assurance. Note which suppliers hold privileged access into your environment and which of your customers will ask you for evidence. A baseline such as Cyber Essentials is a common request from UK customers.
  6. Watch the consultation and secondary legislation. The government has said it intends to consult on implementation proposals. Re-check the status and the factsheets before advising any client.

Where GetCybr fits

GetCybr is multi-tenant GRC software for MSPs: one platform holds many client organisations, each with its own data, frameworks and reports. The GRC software for MSPs page explains the model. For the steps above, that means you can keep each client’s service map, assessments and evidence separate, and run the same structured assessment across clients. The frameworks catalogue lists the NCSC Cyber Assessment Framework (version 4.0) alongside other frameworks, and white-label client reports are included.

GetCybr does not make a practice compliant with the Bill. Scoping, duties and registration remain your decisions, taken with legal advice, and the final requirements are not yet published.

Sources

Read on 21 November 2026. Quotations in this guide are taken from these pages.

General information, not legal advice.

Next step

If you run compliance services across many MSP clients, you can become a partner.

Run compliance and vCISO work for every client

MSPs: put the repeatable assessment, roadmap, and reporting work on GetCybr while your team stays in control of every client relationship.