
ByAhsan Nadeem@ashtech52Lead Full-Stack Engineer
A Cyber Security and Resilience Bill MSP check starts with one fact: it isn't law yet, and there is no compliance date. On 4 November 2026 the Bill is back in the Commons for MPs to consider Lords amendments, with no sitting date listed. Medium and large managed service providers should plan for registration, security duties and 24-hour incident reporting.
This is general information, not legal advice. Confirm the current text and stage on the official Bill page and in the government's factsheets.
Smaller firms are not automatically clear. The small and micro exemption closes only one of three routes: directly, by designation as a critical supplier, or through a customer's contract. A 20-person IT company can be outside the regulated MSP definition and still be designated, or still be asked to prove its security by a customer who is regulated.
Buying managed IT rather than selling it? The end of the action section gives three questions to put to any provider, whether or not you use our managed IT support.
Where the Bill stands on 4 November 2026
The Bill has been through both Houses once and is waiting for the Commons to respond to the Lords' changes.
- 16 June 2026: Commons third reading, seven months after first reading.
- 26 October 2026: Lords report stage, with two government defeats.
- 2 November 2026: Lords third reading. The record says the Bill was passed and returned to the Commons with amendments.
- 3 November 2026: the Lords amendments were printed as Bill 175, and Parliament's record was updated to show "Consideration of Lords amendments", with no sitting date.
- 4 November 2026: Parliament's record lists a carry-over motion in the Commons, the procedure that lets an unfinished Bill continue into the next session. Consideration of Lords amendments remains the next stage, still with no sitting date.
Royal Assent will not switch most of this on. The government's summary splits commencement into three stages.
When | What starts |
|---|---|
On Royal Assent | Powers to update the regime, and the post-implementation review |
Two months after | Statement of strategic priorities, information sharing |
By secondary legislation, at a time ministers set | MSP duties, critical suppliers, incident reporting, cost recovery, data centres, directions |
So there is no MSP compliance date to quote yet, and anyone giving you one is guessing. On 26 October the minister told the Lords that the government would consult on security and resilience requirements "in the coming months", and on critical suppliers in 2027.
Cyber Security and Resilience Bill MSP test: three routes
Run these in order. Being clear of one tells you nothing about the next.
Route | Who it catches | Does size matter? | How you find out |
|---|---|---|---|
1. In scope | Medium and large firms providing managed services in the UK | Yes, small and micro firms are out | You assess yourself and register |
2. Designated | A supplier to a regulated entity whose failure could cause significant national or regional harm | No | The regulator consults you |
3. By contract | Any supplier to a regulated or security-conscious customer | No | A questionnaire or a contract clause |
Route one: are you a relevant managed service provider?
The government's factsheet, updated on 3 November, describes a service with four features. It is under a contract with a customer. It involves ongoing management of IT systems, such as support, monitoring or active administration. You connect to or access systems the customer relies on. And it makes no difference whether that happens on site or remotely.
Data centre services and public electronic communications networks are carved out.
Probably in scope, if you are above the size line | Probably out of scope |
|---|---|
Managing a customer's backups, monitoring, routers and firewalls | Tax, legal or accountancy consultancy with no system connection |
Ongoing firewall management, intrusion detection and incident response | Installing or integrating a system, then walking away |
Remotely managing IT systems that monitor operational technology | Selling a software product, even with occasional remote patches |
Ongoing configuration and monitoring of a customer's cloud | Operational technology supply with no extra IT management |
These are the government's examples, and each is hypothetical.
The grey area was tested at report stage. Lord Clement-Jones called the clause a "regulatory dragnet" and proposed excluding consultancy, training, software support without privileged access, and basic help desks. The minister said those types are not expected to meet both limiting characteristics: access to the customer's systems, and a contract for ongoing management. Lord Clement-Jones withdrew the amendment, so the wording stands. The minister's view is a statement of intent, not a line in the Bill, and the factsheet lists IT remote support and helpdesks among its examples of IT outsourcing, so a help desk with admin rights should not assume it is safe.
The size line is less simple than "50 staff"
The factsheet doesn't define small or micro. The existing NIS Regulations use Commission Recommendation 2003/361/EC, and one specialist glossary says clause 9(4) of the Bill does the same. We haven't checked that against the Bill print, so check that clause yourself.
The European Commission's summary sets a small enterprise at under 50 staff, plus either turnover or balance sheet total of €10m or less. Headcount must be met, and only one of the money tests.
Your firm | Result on those ceilings |
|---|---|
8 staff, €1.5m turnover, €1m balance sheet | Micro, outside route one |
40 staff, €8m turnover | Small, outside route one |
40 staff, €12m turnover, €8m balance sheet | Small, because the balance sheet passes |
40 staff, €12m turnover, €11m balance sheet | Not small, so assume in scope |
60 staff, €4m turnover | Not small on headcount, so assume in scope |
30 staff, owned by a 500-person group | Check it: group data may have to be counted |
Note a mismatch. The impact assessment of November 2025 counted firms with at least 50 UK staff and over €10m turnover. That different test produced its estimate of 556 to 1,019 newly regulated MSPs, out of 12,867 in the UK. A 60-person firm on €4m would be missed by that count but caught by the Recommendation. If you are near the line, ask a lawyer. We couldn't read the May 2026 version of the assessment, so these figures may have moved.
What route one means in practice
- Register with the Information Commission, the ICO's successor, within three months of the regulations starting.
- Manage risk with appropriate and proportionate measures, having regard to the state of the art. Technical detail comes later in regulations.
- Report incidents: an initial notice within 24 hours of becoming aware, then a full report within 72 hours, to the regulator and the NCSC at the same time.
- Tell customers likely to be harmed, and keep them updated while the incident lasts.
- Expect regulator charges. Regulators can recover their full costs from regulated entities, but no amounts are published and the cost recovery factsheet doesn't single out MSPs.
Under the enforcement factsheet, the higher penalty band reaches £17m or 4% of worldwide turnover, whichever is higher, and covers matters such as security and incident duties. The lower band reaches £10m or 2%, and covers matters such as failing to register. These are ceilings. The factsheet says not every breach ends in a penalty, and remedial steps count.
What it might cost: the government's own estimate
This is the government's November 2025 estimate per organisation, not a quote. It borrows survey data from digital service providers as a proxy, and the total is our addition.
Item | Central estimate |
|---|---|
Internal security staff cost, per year | £64,460 |
External security cost, per year | £28,175 |
Compliance reporting, per year | £519 |
Recurring total, per year | £93,154 |
One-off contract change (40 hours at £34, plus 22% overheads) | About £1,659 |
Treat it as an average across firms of very different sizes. It leaves out regulator charges, which aren't set, and your own gap may be far smaller or larger.
Route two: designation as a critical supplier, including small firms
A regulator can designate a supplier if all four conditions are met:
- It supplies goods or services directly to an essential service operator, digital service provider or managed service provider under the same regulator.
- It relies on network and information systems to do so.
- An incident on those systems could disrupt essential, digital or managed services.
- The likely effect of that disruption on the economy or daily life, in all or part of the UK, is significant.
The regulator must also consider whether alternatives realistically exist, and whether another framework already covers the risk. Small and micro firms are expressly included. The government's example is Synnovis, the pathology supplier hit in June 2024. It says that disrupted more than 11,000 appointments and operations, with the company estimating its financial losses at £32.7m.
This route is narrow. The impact assessment expects only a small number of suppliers to be captured, and it could not estimate how many small MSPs that means. You would get a say: the regulator has to consult you and weigh your representations, you can appeal to the First-tier Tribunal, and you can later ask for removal. Duties will be no tougher than those on regulated MSPs, and details will follow consultation.
Quick self-test. Would a regulated customer stop delivering a public-facing service within days if you went down? Could it switch to someone else within that time? If the answers are yes and no, keep a record of the alternatives and the size of your role. You may need that evidence.
One more thing to watch. At report stage the minister described a possible gap, where small MSPs don't directly serve regulated entities but are still high risk. She floated using a delegated power in clause 29, subject to consultation, to let the Information Commission bring individual firms in. It's only a proposal, but it shows the size exemption is not fixed.
Route three: duties arriving through customer contracts
This route is our reading of the sources, not a clause in the Bill. We found no statutory duty that passes directly to an undesignated supplier. The pressure is commercial, and it already exists.
- The NCSC's Cyber Assessment Framework, which the impact assessment gives as an example of how regulated firms report compliance, expects relevant supplier contracts to carry security obligations and to define who owns what.
- Stronger supply chain duties may follow. The impact assessment says the government will be able to set them for essential service operators and digital service providers through secondary legislation.
- Ministers have asked big firms to act. A letter dated 13 October 2025 told leading UK companies to require Cyber Essentials in their supply chains. The April 2026 pledge pack asks signatories to audit coverage and take a risk-based approach to requiring it.
- Regulated MSPs will have clauses of their own. The impact assessment budgets for every in-scope MSP to redraft its client contract, and a regulated MSP may well ask its subcontractors for matching promises.
The new vendor risk factsheet
A factsheet added on 3 November sets out a framework aimed at vendors with third-country links. Ministers could direct an essential service operator not to buy from a vendor, to stop using it, to remove its product or to put mitigations in place, where that is necessary and proportionate for national security.
MSPs are not in scope of those directions for their managed services. But a vendor can lose a customer because the customer received one. The vendor should be consulted where reasonably practicable, and it can seek judicial review.
If you sell to a regulated operator, it would be sensible to prepare answers on who owns your company, where your staff sit and which tools can reach customer systems.
Why this attention on suppliers? Trusted access makes them useful to attackers. Our breakdown of the ConnectWise SkyKick breach, one of October's cyber attacks, shows how one supplier app reached into customer tenants.
Based outside the UK? The representative duty
The definition turns on where the service is provided. It doesn't matter where you are established. An overseas firm providing managed services in the UK, above the size line, must appoint a UK representative as well as meet the other duties.
Two points remain open in what we could read. The impact assessment counted UK staff, but the Commission's summary of the ceilings doesn't limit them that way, so ask for advice if your UK team is small and your global team isn't. The critical supplier factsheet also doesn't say whether overseas suppliers can be designated. Route three applies wherever you sit.
What the Lords changed, and what could still be reversed
Numbers are those used at Lords report stage. We haven't read Bill 175 itself, so this comes from the Hansard text as reproduced by TheyWorkForYou.
Change | Result | Who pushed it | Effect on MSPs |
|---|---|---|---|
Incident means an event with "an actual adverse impact" (Amendment 6) | Agreed, no vote | Government | Fewer false alarms; ransomware and pre-positioning that compromised a system still count |
Mandatory near-miss reports for data centres removed | Agreed | Government | Voluntary scheme planned for all regulated entities |
Stronger duty to update customers during an incident | Agreed | Government | Applies to you if regulated, with the same enforcement |
Review of the regime within 12 months, then repeated (Amendment 163) | Agreed, 202 to 155 | Lord Birt | Could widen scope later |
Register of foreign powers posing cyber risks (Amendment 164) | Agreed, 194 to 155 | Lord Markham, Conservative | Could sharpen supplier country questions |
Vote counts are as announced. The division lists show two fewer on each side.
The first three are the government's own changes. The two defeats are less safe. On the register, the minister told peers it "can create false certainty", and VinciWorks, a compliance publisher, says the government may seek to reverse it. Nobody can say more until the Commons debates it.
What to do before the secondary legislation lands
These steps are useful whichever way the final text goes.
Step | Who | Evidence to keep |
|---|---|---|
Run the three routes, and write down your answers | Owner or director | One-page note, dated |
Do the size sums with group figures, if relevant | Finance | Headcount, turnover, balance sheet |
List each service, with whether it gives ongoing access | Service lead | Service-by-service table |
List who holds admin rights to customer systems, and through which tools | Technical lead | Access register |
Draft a 24-hour first notice and a 72-hour report, then rehearse them | Incident lead | Templates, exercise notes |
Work out how you'd identify affected customers quickly | Service lead | Customer-to-system map |
Read client contracts for incident and audit clauses | Commercial or legal | List of clashes with 24 and 72 hours |
Get Cyber Essentials if customers will ask for it | Owner | Certificate |
Fix cheap, visible gaps, such as email authentication | Technical lead | DNS records, reports |
Respond when the consultation opens | Owner or trade body | Your response |
If you buy managed IT, turn this round. Ask your provider which route it thinks it is on, who holds admin rights to your systems and how fast it would tell you about an incident.
Frequently asked questions
Has the Cyber Security and Resilience Bill become law?
No. On 4 November 2026 it is a Bill. The Lords finished on 2 November, and the Commons must now consider their amendments. No sitting date is listed. Even after Royal Assent, MSP duties begin only when secondary legislation brings them into force. Check the official Bill page for the latest stage.
Does it apply to small IT companies?
Not directly, as a regulated MSP, if you are a small or micro enterprise. You could still be designated as a critical supplier if you meet the conditions, and customers may impose security terms by contract. The minister has also floated a way to bring individual high-risk small firms in, subject to consultation.
What counts as a managed service?
A service under contract for the ongoing management of a customer's IT systems, where you connect to or access systems it relies on, on site or remotely. Examples include outsourced IT support, infrastructure management and managed security. One-off installation and selling a software product are given as examples of what falls outside.
Do overseas MSPs have to comply?
Yes, if they provide managed services in the UK and are not small or micro enterprises. The definition applies whether or not the provider is established in the UK, and overseas providers must appoint a UK representative. How group and non-UK staff are counted is worth checking with a lawyer.
How fast must incidents be reported?
Regulated MSPs must give an initial notice within 24 hours of becoming aware of a significant incident, and a fuller report within 72 hours. The regulator and NCSC are told at the same time. Affected customers must then be told and kept updated. Thresholds for "significant" will come in secondary legislation.
When must MSPs register?
Within three months of the relevant regulations starting. No date has been set, because those regulations will follow Royal Assent and consultation. Registration means giving the Information Commission your name, contact details and an address for service, and other categories may be added.
Whether you supply managed IT or buy it, book a free consultation and bring your routes note or your provider's answers. We'll go through the services and access with you. Legal questions remain for your solicitor.
Sources
- UK Parliament bills API, Bill 4035: stages (read 4 November 2026)
- UK Parliament, Cyber Security and Resilience (Network and Information Systems) Bill
- UK Parliament bills API, Bill 4035: publications
- GOV.UK, Bill factsheets (updated 3 November 2026)
- GOV.UK, Summary of the Bill
- GOV.UK, Relevant managed service providers
- GOV.UK, Incident reporting
- GOV.UK, Designating critical suppliers
- GOV.UK, Vendor risk management
- GOV.UK, Enforcement
- GOV.UK, Cost recovery
- DSIT, final stage impact assessment (12 November 2025)
- DSIT, Research on managed service providers 2025
- Hansard via TheyWorkForYou, Lords report stage, Amendment 2 (26 October 2026)
- Hansard via TheyWorkForYou, Lords report stage, Amendment 6
- Hansard via TheyWorkForYou, Lords report stage, Amendment 163
- Hansard via TheyWorkForYou, Lords report stage, Amendment 164
- Hansard via TheyWorkForYou, Lords third reading (2 November 2026)
- Legislation.gov.uk, NIS Regulations 2018, regulation 1
- European Commission, SME definition
- NCSC, Cyber Assessment Framework, principle A4: supply chain
- GOV.UK, Ministerial letter on cyber security (13 October 2025)
- GOV.UK, Government Cyber Resilience Pledge information pack (April 2026)
- VinciWorks, secondary source on the Lords votes (29 October 2026)
- Precursor Security glossary, secondary and commercial source on clause 9(4)



