# UK law for managed service providers — Cyber Security and Resilience Bill

> No single UK law covers everything an MSP does. The Cyber Security and Resilience Bill (CSRB) would regulate medium and large MSPs directly for the first time, while UK GDPR, the Computer Misuse Act, contract law and your customers’ sector rules already apply.

Canonical page: https://cybersecurityandresiliencebill.com/guides/uk-law-for-managed-service-providers
Updated: 2026-11-09

Status checked 13 November 2026: the Bill passed the House of Lords on 2 November 2026 and returns to the Commons, which is due to consider the Lords amendments on 24 November 2026. On 4 November 2026 the Commons extended its carry-over, so it lapses if not passed by the end of 29 April 2027. It is not yet law. References are to HL Bill 62 (as amended on Report), so wording and numbering may still change in the final Act. This guide is general information, not legal advice.

## Key points

- There is no Managed Services Act; MSPs are covered today by UK GDPR, the Computer Misuse Act, contracts and customer rules.
- The Bill would make medium and large MSPs relevant managed service providers, regulated by the Information Commission.
- RMSPs would register, manage security risks, report significant incidents within 24 and 72 hours and notify affected customers.
- Processors can be fined directly: the ICO fined Advanced £3.07 million in 2025 after a ransomware attack.
- Contract notice periods must be short enough for you and your customers to meet the new reporting deadlines.

## Is there a Managed Services Act in the UK?

No. No single UK law is written just for managed service providers (MSPs). Today an MSP is covered by general laws: UK GDPR, the Computer Misuse Act 1990, contract law and the rules its customers pass down. The Cyber Security and Resilience Bill (CSRB) would add the first MSP-specific regime by amending the NIS Regulations 2018.

This guide maps every layer. For the step-by-step duties under the Bill, use the [MSP compliance checklist](/guides/msp-compliance-checklist).

## Which laws apply to an MSP?

Five layers apply to most MSPs, and four of them already apply today. The table shows what each one asks of you.

| Layer | Applies today? | What it means for an MSP | Who enforces it |
|---|---|---|---|
| The Bill, as a [relevant managed service provider](/glossary/relevant-managed-service-provider) | Not yet | Registration, security duties, incident reporting, customer notices | Information Commission |
| UK GDPR and Data Protection Act 2018 | Yes | Security of personal data and breach notification | Information Commission (the ICO's successor) |
| [Computer Misuse Act 1990](/guides/computer-misuse-act-explained) | Yes | Your access to customer systems must stay within your authority | Police and prosecutors |
| Contract law | Yes | Your service agreement sets most day-to-day liability | Courts |
| Your customers' sector rules | Yes, through contracts | Customers pass their regulators' requirements on to you | Their regulators, via your customer |

## Will the Bill regulate my MSP?

If you are medium or large and manage customers' IT under contract with access to their systems, probably yes. The Bill, as amended on Report (HL Bill 62), inserts a definition of "managed service" into regulation 1 of the NIS Regulations through clause 9.

A managed service is one provided under a contract for the "ongoing management of information technology systems for the customer", through support and maintenance, monitoring, active administration or other activities. You must also connect to, or otherwise access, systems the customer relies on. It doesn't matter whether that access is on site or remote.

You are a relevant managed service provider (RMSP) if you meet all of these tests:

- You provide a managed service in the UK, whether or not you are established here.
- You are not a [micro or small enterprise](/guides/does-the-bill-apply-to-small-businesses) under Commission Recommendation 2003/361/EC.
- You pass the [public authority oversight](/glossary/public-authority-oversight) test.
- You aren't designated as a critical supplier for that service.

Data centre services and public electronic communications networks and services don't count as managed services. If you're unsure which category fits, see [OES vs RDSP vs RMSP](/guides/oes-vs-rdsp-vs-rmsp).

## What would the Bill require of an RMSP?

The Bill would create six core duties, all overseen by the Information Commission. The regulation numbers below are the ones the Bill inserts into the NIS Regulations.

| Duty | Regulation (Bill clause) | What it requires |
|---|---|---|
| Security | 14B (cl 10) | Appropriate and proportionate measures, having regard to the state of the art, and to Information Commission guidance |
| Registration | 14C (cl 14) | Name, address, directors and contact details within three months of the duty starting |
| UK representative | 14D (cl 14) | Required if your principal office is outside the UK |
| Incident reporting | 14E (cl 15) | Initial notice within 24 hours and full notice within 72 hours, both from first awareness, copied to the [CSIRT](/guides/what-is-a-csirt) |
| Customer notices | 14G (cl 16) | Tell likely affected UK customers after the full notice, then give them updates you consider necessary |
| Information and inspection | Powers to require information (cl 20) | Respond to information notices and allow inspections |

Two changes made by the Lords matter for MSPs:

- **Incidents mean actual effects.** HL Bill 62 drops the earlier "capable of having" wording. An incident would be an event with an actual adverse effect on the operation or security of systems, so near misses would not be mandatory reports. See [what counts as a significant incident](/guides/what-is-a-significant-incident).
- **Customer updates.** After notifying affected customers, you would have to give them "such updates about the incident and its impact" as you consider necessary (new regulation 14G(4)).

Penalties would follow regulation 18 as amended by clause 21. Serious failures, including security and incident notification failures, would carry a maximum of the greater of £17 million and 4% of turnover. Administrative failures such as registration would carry the greater of £10 million and 2%.

## How does UK GDPR apply to an MSP?

Most MSPs act as processors for customer personal data and as controllers for their own staff and contacts. As a processor, UK GDPR expects three things:

- A contract with each customer that covers the Article 28 terms
- Appropriate technical and organisational security under Article 32
- Notice to the customer of a personal data breach without undue delay, under Article 33(2)

Your customer, as controller, normally has to tell the regulator within 72 hours where the breach is reportable. Their clock may depend on how fast you tell them. For how the two regimes run side by side, see [incident reports under the Bill and UK GDPR](/guides/incident-reporting-and-uk-gdpr).

### The Advanced case: a processor fined directly

In March 2025 the ICO fined Advanced Computer Software Group £3,076,320 as a processor, following a 2022 ransomware attack on its health and care subsidiary. Attackers got in through a customer account that didn't have multi-factor authentication. The breach affected 79,404 people.

The ICO had proposed £6.09 million in August 2024. It reduced the fine after considering Advanced's representations and its engagement with the NCSC, National Crime Agency and NHS. Advanced accepted the final amount.

For MSPs the lesson is that processor status doesn't shield you. Gaps in multi-factor authentication, vulnerability scanning and patching were at the centre of the case.

## Where does the Computer Misuse Act come in?

Your access to customer systems is lawful because you have authority for it. Under section 17(5), access is unauthorised if you aren't entitled to control it and don't have consent from someone who is. Section 1 makes knowingly unauthorised access an offence.

In practice:

- Write the scope of your access into the contract.
- Remove access when staff leave or a contract ends.
- Get written authority before unusual work, such as [penetration testing](/guides/is-penetration-testing-legal-uk).
- Check who can authorise work on third-party platforms, such as a cloud tenant your customer doesn't own.

## What should my contracts cover?

Between you and your customer, the contract usually decides who bears the cost of an incident. Statute sets duties, but contract allocates loss. Review these terms:

| Term | Why it matters under the Bill |
|---|---|
| Security responsibilities | Shows which measures sit with you under regulation 14B |
| Incident notice period | Must be fast enough for both of you to meet 24-hour and 72-hour deadlines |
| Liability caps and exclusions | The Unfair Contract Terms Act 1977 can limit them |
| Audit and evidence rights | Regulated customers will ask for proof |
| Exit and access removal | Stops stale access, which is a common route in |

See [who is liable when an MSP's client is breached](/guides/msp-client-breach-liability) and [managed security services contracts](/guides/managed-security-services-contract).

## How do customers' rules reach me?

Through contracts. Your customer's regulator may not regulate you, but its expectations arrive as clauses and questionnaires. Examples:

- **Financial services:** [FCA and PRA rules](/guides/fca-pra-cyber-requirements) on outsourcing and third parties. EU financial customers must also put [DORA's](/guides/does-dora-apply-to-uk-firms) Article 30 terms into ICT contracts.
- **Health:** [NHS standards](/guides/nhs-cyber-standards) such as the Data Security and Protection Toolkit.
- **Operators regulated under the Bill:** supply chain expectations, and possibly [critical supplier designation](/whos-affected/critical-suppliers).
- **EU customers:** [NIS2](/guides/does-nis2-apply-to-uk-companies) supply chain duties.

If your contract promises compliance with a named standard, you can be held to it even where the underlying rule doesn't apply to you.

## Worked example

*This is our illustration, not a regulator's view.*

A UK MSP with 120 staff and £14 million turnover runs remote monitoring and patching for a regional NHS trust and a building society.

- **The Bill:** it is above the small enterprise ceiling and provides ongoing management with system access, so it is likely to be an RMSP once the duties start.
- **UK GDPR:** it is a processor for both customers' personal data.
- **Contracts:** the trust's contract may refer to NHS standards, and the building society's to its outsourcing obligations.
- **Incident:** a compromise of its remote tool could trigger a 24-hour notice to the Information Commission, prompt notices to both customers under UK GDPR and the contracts, and customer notices under regulation 14G.

## Common mistakes

1. **Assuming "we're only a processor" ends the analysis.** The Advanced fine shows processors can be fined directly.
2. **Checking size for one company only.** Linked and partner businesses can count towards the small enterprise limits.
3. **Setting contract notice periods longer than 24 hours.** Your customer may need your information for their own deadlines.
4. **Leaving accounts without multi-factor authentication.** This was the entry point in the Advanced case.

## What to do first

1. Decide whether each legal entity in your group meets the RMSP definition.
2. Check data processing agreements against Article 28.
3. Audit customer-facing access, starting with accounts without multi-factor authentication.
4. Align contract incident notice periods with the 24-hour and 72-hour clocks.
5. Make one list of the compliance promises in your customer contracts.

## Sources

- [Cyber Security and Resilience Bill, HL Bill 62 (as amended on Report)](https://bills.parliament.uk/publications/68323/documents/8979)
- [ICO: Advanced Computer Software Group penalty notice](https://ico.org.uk/action-weve-taken/enforcement/2025/03/advanced-computer-software-group-limited/)
- [Tech Monitor: ICO fines Advanced £3.07m after NHS data breach](https://www.techmonitor.ai/technology/cybersecurity/uk-ico-fines-advanced-computer-3-07m-after-nhs-data-breach)
- [UK GDPR, Article 33](https://www.legislation.gov.uk/eur/2016/679/article/33)
- [Computer Misuse Act 1990, section 17](https://www.legislation.gov.uk/ukpga/1990/18/section/17)
- [DORA, Article 30 (article-by-article copy)](https://www.digital-operational-resilience-act.com/Article_30.html)

## Frequently asked questions

### Is there a Managed Services Act in the UK?

No. No UK law is written only for managed service providers. The nearest thing is the Cyber Security and Resilience Bill, which would amend the NIS Regulations 2018 so that medium and large MSPs become relevant managed service providers with their own registration, security and reporting duties.

### Are MSPs regulated in the UK today?

Not as a category. The NIS Regulations 2018 do not cover managed service providers. General laws already apply, though: UK GDPR when an MSP processes personal data for customers, the Computer Misuse Act for its access to customer systems, and the terms of its customer contracts.

### Can the regulator fine an MSP directly under UK GDPR?

Yes, where the MSP has its own UK GDPR obligations as a processor. In March 2025 the ICO fined Advanced Computer Software Group £3,076,320 after a 2022 ransomware attack that began through a customer account without multi-factor authentication. The ICO had proposed £6.09 million.

### Which regulator would oversee MSPs under the Bill?

The Information Commission (the ICO's successor). It would keep the register of relevant managed service providers, receive their incident notifications, issue guidance on security measures and enforce penalties of up to the greater of £17 million and 4% of turnover.

### Who is liable when an MSP’s customer is breached?

It depends on the facts and the contract. Regulatory duties sit separately on each regulated organisation, so both may have to report. Liability between the MSP and customer usually turns on the contract terms, the cause of the breach and data protection law. Take legal advice on a specific incident.

