The UK Cyber Security and Resilience Bill turns cyber resilience at managed service providers, data centres and their critical suppliers into a regulated duty, with penalties of up to £17 million or 4% of worldwide turnover, so boards in those sectors need to know now whether they are in scope and what they will have to evidence. This briefing is written for directors, non-executives and senior leaders who need a short view of the Bill as it stands. It does not repeat the clause-by-clause detail: for that, read our UK Cyber Security and Resilience Bill Guide.
Status as of 18 Nov 2026: the Cyber Security and Resilience (Network and Information Systems) Bill had not received Royal Assent at the time of writing; check bills.parliament.uk for the current stage. It was introduced to Parliament on 12 November 2025, carried over into the 2026-27 session and reintroduced in the House of Commons at Report Stage as Bill 002 (dated 14 May 2026), according to the Parliament bill page. Most duties will start only through secondary legislation after Royal Assent. Clause numbers, thresholds and dates may change. This briefing is not legal advice.
Key takeaways
- Medium and large managed service providers (MSPs) and qualifying data centres are brought into the UK NIS regime for the first time. Large load controllers (for example, EV charging aggregators) and regulator-designated critical suppliers join them.
- Incident reporting tightens to an initial notice within 24 hours and a fuller report within 72 hours, with the NCSC informed at the same time. Data centres, MSPs and digital service providers must tell customers who are likely to be affected.
- Penalties move to two bands: up to £10 million or 2% of worldwide turnover, and up to £17 million or 4% for serious breaches such as failing security or reporting duties.
- In November 2026 the government published two new proposals under the Bill's powers: agentic AI resilience measures and a vendor risk management framework with direction powers. Both would come later, through secondary legislation.
- Most of the work is identity and supplier work: who has privileged access to customer environments, which service accounts and automation tools can change production, and how fast you can tell a customer what happened.
- The board's job now is to confirm scope, name an accountable executive, fund a 24-hour reporting capability and ask for evidence, not reassurance.
The Bill at a glance
| Topic | What the government says | When |
|---|---|---|
| New entities | Medium and large MSPs, qualifying data centres, large load controllers, designated critical suppliers | Secondary legislation after Royal Assent |
| Security duty | Appropriate and proportionate measures, all-hazards and risk-based | Cross-sector duties applied by sector regulators |
| Incident reporting | Initial notice in 24 hours, full report in 72 hours, NCSC informed, customers told where likely affected | Secondary legislation |
| Penalties | Standard band up to £10m or 2%; higher band up to £17m or 4%, whichever is higher | With the enforcement provisions |
| Government powers | Statement of strategic priorities, directions to regulators and regulated entities on national security grounds, power to add sectors | Priorities statement two months after Royal Assent; directions by regulation |
| Proposed add-ons (Nov 2026) | Agentic AI resilience measures; vendor risk management directions | Consultation, then affirmative statutory instruments |
Sources: the gov.uk summary factsheet and enforcement factsheet.
The risk in one paragraph
The Bill exists because the UK's 2018 NIS Regulations did not cover the companies that now hold the keys to essential services: the MSPs that run other organisations' IT and the data centres that host it. One compromised MSP can reach hundreds of customers through remote management tools, shared admin accounts and automation credentials. Parliament is closing that gap by making these providers regulated in their own right, with duties to manage risk, report incidents fast and tell customers. For a board, the risk is twofold: the operational risk of being the route into a customer, and the regulatory risk of being unable to show a regulator that you managed it.
Who is in scope
The government's summary of the Bill describes four groups that come in, alongside the existing operators of essential services and relevant digital service providers:
- Managed service providers. Medium and large MSPs are brought into scope, regulated by the Information Commission. Small and micro providers are expected to be outside the duty, but the size tests sit in secondary legislation that has not been made.
- Data centres. Data centres become an essential service in a new data infrastructure sector, covering medium and large data centres and enterprise data centres that meet thresholds, with Ofcom as regulator.
- Large load controllers. Organisations that manage electrical load for smart appliances, such as EV charge points, come in with enhanced cyber requirements.
- Critical suppliers. Regulators will be able to designate suppliers to essential and digital services as critical, an approach the government says is modelled on the financial services critical third parties regime.
Boards should not wait for thresholds before acting. If your organisation manages IT, security or cloud services for other businesses, or hosts their systems, assume you may be in scope and plan accordingly. If you buy from such providers, expect their contracts and assurance packs to change. Our NIS2 vs UK Cyber Security and Resilience Bill comparison helps groups that operate in both the UK and the EU.
Key obligations the board will be asked about
A risk-based security duty
In-scope organisations must take appropriate and proportionate measures to manage risks to their network and information systems. The government describes the duty as all-hazards: it covers physical security and operational resilience, not only cyber attack. In practice regulators are expected to lean on the NCSC Cyber Assessment Framework, which already underpins NIS oversight in the UK.
Incident reporting in 24 and 72 hours
More kinds of incident become reportable, including incidents that have not yet caused significant disruption. An initial notification is due within 24 hours and a fuller report within 72 hours, with the NCSC informed at the same time, per the summary factsheet. MSPs, data centres and digital service providers must also inform customers likely to have been affected. That customer duty is the one most boards underestimate: it needs a customer impact map ready before the incident, not built during it.
Registration and cost recovery
MSPs and digital service providers will need to register with their regulator. Failure to notify registration falls in the standard penalty band. Regulators gain powers to recover the full cost of their NIS work through charging schemes, so in-scope firms should budget for fees as well as compliance spend.
Government directions
The Secretary of State gains powers to direct regulators and regulated entities to take targeted, proportionate action against imminent threats to national security, and to set a statement of strategic priorities that regulators must pursue. A board should know who in the business would receive and act on a direction, and how quickly.
Enforcement and penalties
The enforcement factsheet sets out a simplified two-band structure:
- Higher band: up to £17 million or 4% of an undertaking's worldwide turnover, whichever is higher, for more serious breaches. The government's examples are breaches of incident notification and security duties.
- Standard band: up to £10 million or 2% of worldwide turnover, whichever is higher, for less serious breaches, such as failing to notify registration as a relevant digital or managed service provider.
The process runs from a notice of intention to impose a penalty, through possible enforcement notices requiring corrective action and representations, to a final penalty decision. Appeals go to the First-tier Tribunal. How "undertaking" and turnover are measured will be set in secondary legislation, which matters for groups with UK subsidiaries of larger parents.
The proposed vendor risk management directions carry their own ceiling: the vendor risk management factsheet describes penalties of up to 10% of turnover for an undertaking, or £17 million for other regulated entities, with continuing breaches capped at £100,000 a day.
What changed in November 2026
On 3 November 2026 the government updated its factsheets and added two new ones. Neither is in force; both would be made by secondary legislation after Royal Assent.
Agentic AI resilience measures
The agentic AI resilience measures factsheet proposes using the Bill's powers to amend the NIS Regulations so regulated entities can handle incidents where AI agents cause a loss of control over their systems. The four proposals are: security and resilience requirements such as monitoring agent actions and agent risk assessments; notifying other affected organisations, not just customers; preserving evidence of what the agents did and how the organisation tried to control them; and powers for ministers to task government experts to review agentic loss of control incidents. All four would be consulted on and use the affirmative procedure. For boards, the message is clear: AI agents are being treated as operators inside your network, and you will be expected to know what they can touch. Our AI Agent Platforms and MCP Executive Briefing covers the oversight questions.
Vendor risk management
The vendor framework applies initially to operators of essential services, which now include data centres. It has three parts: non-statutory guidance on vendor risk, including at procurement; a voluntary route for operators to refer vendor concerns to government; and a power for the Secretary of State to direct an operator to stop buying, stop using or remove a vendor's goods or services, or to put mitigations in place, where necessary and proportionate for national security. MSPs and digital service providers are outside it unless they are also operators of essential services. Directions about a vendor could still force an operator to replace an MSP's tooling or service, so suppliers should expect tougher procurement questions.
What it means for security and identity teams
Most of what a regulator will test sits in access and identity, because that is how MSP compromises spread. The areas a board should expect its security team to own:
- Privileged access into customer estates. Remote monitoring and management tools, shared technician accounts and standing admin rights are the main path from one MSP to many customers. Expect to show named, individual and time-bound access.
- Non-human identities. Service accounts, API keys, automation tokens and agent credentials often hold more access than any technician. They need an owner, an inventory and rotation. Our Secrets Management Executive Briefing sets out the board view.
- Customer impact mapping. To meet the customer notification duty you must know, for any tool, account or platform, which customers it reaches.
- Logging and evidence. A 72-hour report and the proposed agentic evidence duty both depend on logs that are kept, searchable and tied to identities.
- Supplier assurance. Critical supplier designation and vendor directions mean your own suppliers need the same scrutiny you will face.
Five questions for the board to ask
- Are we, or any group company, likely to be a relevant managed service provider, a data centre operator, a large load controller or a critical supplier, and who has signed off that view?
- If an incident started tonight, who would decide by tomorrow evening whether it is reportable, and who would send the 24-hour notice and the customer notices?
- How many people and how many service accounts, API keys and automation tools can reach customer environments, and how many of them have standing access?
- Which suppliers could, if compromised, cause a reportable incident at us, and what evidence do we hold about their controls?
- Where are AI agents acting in our environment or our customers', what can they change, and could we reconstruct what they did?
Red flags in management answers
- "We will look at it after Royal Assent." Reporting and customer notification processes take months to build and rehearse.
- "Our ISO certificate covers it." A certificate shows a management system exists; it does not show that a 24-hour decision can be made.
- "Our tooling vendor handles access." Shared or vendor-held admin accounts are exactly the exposure the Bill targets.
- No answer, or a very rough one, to how many non-human credentials reach customer systems.
- Incident playbooks that name only internal escalation and do not mention regulators, the NCSC or customers.
What good looks like
- A written scope assessment, reviewed by legal counsel, refreshed when thresholds are published.
- One accountable executive for NIS compliance, with a deputy, and a board reporting line.
- A reporting decision tree, a 24-hour notice template and customer notice templates, tested in an exercise.
- A current inventory of human and machine access into customer environments, with owners and expiry.
- Self-assessment against the Cyber Assessment Framework, with gaps funded and tracked.
- Supplier tiering that identifies who could cause a reportable incident, with contract clauses for notification and audit.
Metrics to track
| Metric | Why it matters |
|---|---|
| Time from detection to reportability decision, measured in exercises | Tests whether the 24-hour notice is achievable |
| Share of privileged access to customer estates that is standing rather than just-in-time | Main lateral path in MSP compromises |
| Non-human credentials reaching customer systems with no named owner | Unowned credentials are rarely rotated or revoked |
| Customers mapped to each shared tool and platform | Needed for customer notification |
| Critical suppliers with current assurance evidence | Supports supplier and vendor duties |
| Cyber Assessment Framework outcomes achieved | Likely regulator yardstick |
Where to invest first: a 90-day plan
- Days 1 to 30: scope assessment, accountable executive named, inventory of tools and accounts with access into customer environments, supplier tiering started.
- Days 31 to 60: reporting decision tree and templates drafted, customer impact map built for the top shared platforms, standing technician and service account access reduced.
- Days 61 to 90: tabletop exercise against the 24 and 72-hour clocks, Cyber Assessment Framework self-assessment, budget request for gaps, board report on readiness.
Keep an eye on the government consultation on implementation, which the summary factsheet says will be followed by secondary legislation and an adjustment period. For incident handling at board level, see our Cyber Incident Readiness Executive Briefing.
Common failure patterns
- Treating the Bill as a data protection matter and routing it only to the privacy team, when the regulator will test operational security.
- Assuming the 72-hour report is the deadline, and missing the 24-hour initial notice.
- Building customer notification lists by hand during an incident.
- Counting technicians but not service accounts, RMM agents and API tokens when sizing privileged access.
- Ignoring group structure, so turnover-based penalties land on a parent that never assessed its UK exposure.
- Waiting for thresholds and then having too little time to build and test processes before the adjustment period ends.
Practitioner checklist
- Record a scope assessment for each UK entity, with the reasoning and the date.
- Name an accountable executive and a deputy for NIS compliance.
- Draft and test a reportability decision tree aligned to 24 and 72-hour clocks.
- Prepare regulator, NCSC and customer notification templates.
- Inventory every human and non-human identity that can reach customer environments, with owner and expiry.
- Remove shared technician accounts and move standing admin access to just-in-time.
- Map customers to each shared tool, platform and data centre hall.
- Tier suppliers and add notification and audit clauses for critical ones.
- Inventory AI agents, their permissions and their logs.
- Run a Cyber Assessment Framework self-assessment and report gaps to the board.
- Track the implementation consultation and secondary legislation.
Standards and references
- UK Parliament: Cyber Security and Resilience (Network and Information Systems) Bill
- gov.uk: Cyber Security and Resilience Bill factsheets
- gov.uk: Summary of the Bill factsheet
- gov.uk: Enforcement factsheet
- gov.uk: Agentic AI resilience measures factsheet
- gov.uk: Vendor risk management factsheet
- NCSC: Cyber Assessment Framework
Related NHI Mgmt Group resources: UK Cyber Security and Resilience Bill Guide · NIS2 vs UK Cyber Security and Resilience Bill · Global Cybersecurity Regulatory Map · NIS2 Management Liability Executive Briefing