Part 2: The NIS Regulations.

Part 2 would amend the NIS Regulations 2018. It brings data centres, large load controllers and managed service providers into scope, lets regulators designate critical suppliers, replaces incident reporting with a 24-hour initial and 72-hour full notification, adds customer notification, and rewrites cost recovery, information powers and penalties.

Clauses 3 to 23HL Bill 62, printed Checked
Last updated Status: not yet law. The Commons considers the Lords amendments on 24 November 2026.Sources: UK Parliament · HL Bill 62 · NIS Regulations 2018
Where this stands

This is a Bill, not law. It has not received Royal Assent, so every duty described here is proposed. Lords stages complete (Third Reading 2 November 2026). The Commons has not yet considered the Lords amendments.

Clause numbers, subsections and page numbers refer to HL Bill 62 (as amended on Report, printed 26 October 2026), checked against the Parliament Bills API on 9 November 2026. Numbers can change if the Commons amends or rejects Lords amendments.

Part 2 · Clauses 3 to 23Clause table

ClauseHeadingWhat it doesWho it affects
3Identification of operators of essential servicesApplies OES identification to operators outside the UK and excludes public telecoms networks and services.Operators of essential services (OES), including non-UK operators
4Data centres to be regulated as essential servicesAdds a data infrastructure subsector regulated by Ofcom, with 1 MW and 10 MW (enterprise) thresholds.Data centre operators at or above the thresholds
5Operators of data centre services: Crown application etcApplies the data centre rules to the Crown, with exceptions for the intelligence agencies and secret/top secret work.Government and Crown data centres; commercial providers hosting classified material
6Designation of large load controllers as operators of an essential serviceMakes load control an essential service where a controller has 300 MW or more of potential electrical control.Load controllers of EVs, charge points, heat pumps, batteries and virtual power plants
7Digital servicesRedefines cloud computing and creates "relevant digital service providers" (RDSPs).Cloud providers, online marketplaces and online search engines (not micro or small)
8Duties of relevant digital service providersUpdates RDSP security duties and requires regard to Information Commission guidance.RDSPs
9Managed service providersDefines "managed service" and "relevant managed service provider" (RMSP), regulated by the Information Commission.Managed service providers (not micro or small), including non-UK providers
10Duties of managed service providers to manage risksRequires RMSPs to take appropriate and proportionate security measures (new regulation 14B).RMSPs
11Digital or managed service providers: meaning of “subject to public authority oversight”Defines when a digital or managed service provider counts as under public authority oversight.Public bodies and publicly controlled companies that provide digital or managed services
12Critical suppliersLets regulators designate critical suppliers to OES, RDSPs and RMSPs (new regulations 14H to 14L).Suppliers to regulated organisations, of any size and wherever established
13Provision of information by operators of data centre servicesRequires in-scope data centre operators to give their regulator contact and ownership details within 3 months.Data centre operators that are OES
14Provision of information by providers of digital or managed services etcRegistration with the Information Commission for RDSPs and RMSPs, 7-day change notices and UK representatives.RDSPs and RMSPs, including those based outside the UK
15Reporting of incidents by regulated personsReplaces incident reporting: initial notification within 24 hours, full notification within 72 hours, copied to the CSIRT.OES (including data centres), RDSPs and RMSPs
16Notification of incidents to customersAfter a full notification, data centres, RDSPs and RMSPs must notify UK customers likely to be adversely affected.Data centre OES, RDSPs and RMSPs, and their UK customers
17Powers to impose chargesLets regulators recover their costs through published charging schemes and invoiced charges.All persons regulated by a NIS enforcement authority
18Sharing and use of information under the NIS Regulations etcReplaces the information-sharing rules, including sharing with GCHQ, law enforcement and listed overseas authorities.Regulators; indirectly every regulated person whose information they hold
19GuidanceSets what regulators' guidance must cover and requires consistency with the code of practice and Government guidance.Regulators; regulated persons who rely on their guidance
20Powers to require informationReplaces regulation 15 with information notices that can reach regulated and unregulated persons.Regulated persons and anyone likely to hold relevant information
21Financial penaltiesTwo penalty caps: greater of £10m and 2% of turnover, or greater of £17m and 4%, by type of failure.OES, RDSPs, RMSPs and anyone given an information or enforcement notice
22Enforcement and appealsIntroduces Schedule 1 (inspections, enforcement notices, appeals and civil proceedings).OES, RDSPs, RMSPs, critical suppliers and recipients of information notices
23Minor and consequential amendments etcIntroduces Schedule 2 (minor and consequential amendments).Mainly drafting; see Schedule 2

Chapter 1Persons regulated under the NIS Regulations

Clause 3Identification of operators of essential services

Affects: Operators of essential services (OES), including non-UK operatorsOfficial text: HL Bill 62, PDF page 8bills.parliament.uk#clause-3
What the Bill says

Clause 3 would amend regulation 8 of the NIS Regulations (identification of operators of essential services):

  • new regulation 8(1ZA): the deeming rule in regulation 8(1) would apply whether or not the person is established in the UK;
  • regulation 8(1A) would be replaced so that regulation 8(1) does not apply to the provision of a public electronic communications network or service (as defined in section 151(1) of the Communications Act 2003);
  • new regulation 8(3A): a competent authority could designate a person under regulation 8(3) whether or not it is established in the UK.
What this means in practice (our interpretation)

Our reading: a foreign-headquartered operator that meets a Schedule 2 threshold in the UK could not argue it is outside the regime because it has no UK establishment. Public telecoms networks and services stay with the separate telecoms security regime under the Communications Act 2003 rather than being regulated twice.

Clause 4Data centres to be regulated as essential services

Affects: Data centre operators at or above the thresholdsOfficial text: HL Bill 62, PDF page 9bills.parliament.uk#clause-4
What the Bill says

Clause 4(2) would add a "Data infrastructure" subsector to the table in Schedule 1 to the NIS Regulations, with the Office of Communications (Ofcom) as designated competent authority for the United Kingdom.

Clause 4(3) would insert a new paragraph 11 into Schedule 2 to the NIS Regulations setting the thresholds:

  • a data centre service provided in the UK otherwise than on an enterprise basis: rated IT load of 1 megawatt or more;
  • a data centre service provided in the UK on an enterprise basis: rated IT load of 10 megawatts or more.

A "data centre service" is the provision of a physical structure that contains an area for housing, connecting and operating IT equipment and provides supporting infrastructure (electricity, environmental control, security or resilience). A service is "enterprise" if the data centre is owned or managed by a person for its own undertaking and its sole purpose is to provide IT services for that undertaking. "Rated IT load" is the maximum electrical power available for IT equipment in the data centre. A "structure" can be a building, part of a building or a group of structures.

What this means in practice (our interpretation)

Our reading: colocation and other third-party facilities are caught from 1 MW; a data centre run solely for its owner's own business is caught only from 10 MW. Because "structure" includes a group of structures, it is not clear from the clause alone how separate halls or buildings on one site will be aggregated; expect Ofcom guidance on this.

These thresholds sit in Schedule 2 to the NIS Regulations, not in Schedule 2 to the Bill. The Bill's own Schedule 2 is "Minor and consequential amendments".

Not settled by the text. How multiple buildings or halls are counted towards rated IT load is not spelled out beyond "references to a structure include references to a group of structures".

Clause 5Operators of data centre services: Crown application etc

Affects: Government and Crown data centres; commercial providers hosting classified materialOfficial text: HL Bill 62, PDF page 10bills.parliament.uk#clause-5
What the Bill says

Clause 5 would insert regulation 8(7ZA) and (7ZB) into the NIS Regulations. Regulation 8(1) and (3) would apply to data centre services provided by or on behalf of the Crown, except:

  • where the provider is the Security Service, the Secret Intelligence Service or GCHQ; or
  • to the extent the service is provided on a commercial basis on behalf of His Majesty's Government for storing, processing or transmitting material classified "secret" or "top secret".
What this means in practice (our interpretation)

Our reading: a commercial provider that hosts both classified Government workloads and ordinary customers would be outside the regime only "to the extent" of the classified service. The rest of its data centre service would still count.

Clause 6Designation of large load controllers as operators of an essential service

Affects: Load controllers of EVs, charge points, heat pumps, batteries and virtual power plantsOfficial text: HL Bill 62, PDF page 10bills.parliament.uk#clause-6
What the Bill says

Clause 6 would amend paragraph 1 of Schedule 2 to the NIS Regulations (electricity subsector). The threshold for the essential service of load control would be a load controller that carries on activities for system-balancing purposes and whose potential electrical control over the relevant energy smart appliances it manages is 300 megawatts or more.

Potential electrical control is the maximum flow into, plus the maximum flow out of, all those appliances taken together that can be achieved in response to its load control signals, using manufacturers' stated electrical capacity.

Relevant energy smart appliances are electric vehicles, charge points, electrical heating appliances (listed types of heat pump, direct electric hot water cylinders, electric storage heaters, heat batteries), battery energy storage systems and virtual power plants.

Where an intermediary sends signals on behalf of a load controller, the appliances count as managed by the load controller only, unless the intermediary can adjust or process the signals and is authorised to do so, in which case both are treated as managing them and the intermediary is also treated as a load controller.

What this means in practice (our interpretation)

Our reading: this targets aggregators and platforms that can switch large fleets of domestic and commercial devices at once, because a compromise could move hundreds of megawatts of demand. Inflow and outflow are added together, so a battery fleet counts in both directions.

Clause 7Digital services

Affects: Cloud providers, online marketplaces and online search engines (not micro or small)Official text: HL Bill 62, PDF page 12bills.parliament.uk#clause-7
What the Bill says

Clause 7 would amend regulation 1 of the NIS Regulations. A "relevant digital service" would be an online marketplace, an online search engine or a cloud computing service.

A "cloud computing service" would be a digital service that enables access to a scalable and elastic pool of shareable computing resources, with broad remote access, on demand and self-service, potentially distributed across locations, and not provided solely for the provider's own business; and which is not a managed service. Each term ("broad remote access", "scalable", "elastic", "shareable") is defined in new regulation 1(2A).

A relevant digital service provider (RDSP) would be a person that provides a relevant digital service in the UK (whether or not established here), is not designated as a critical supplier for that service, is not a micro or small enterprise (Commission Recommendation 2003/361/EC), and is either not subject to public authority oversight or derives more than half its income from commercial activities.

New regulation 1(3A): providing a public electronic communications network or service does not by itself make someone a provider of a relevant digital service.

What this means in practice (our interpretation)

Our reading: the cloud definition is tied to the classic on-demand, multi-tenant model and expressly excludes managed services, so a provider whose offer is really ongoing management of a customer's systems should look at clause 9 instead. The Explanatory Notes (written for HL Bill 32) describe the size test as 50 or more staff and more than EUR 10 million turnover or balance sheet total.

Clause 8Duties of relevant digital service providers

What the Bill says

Clause 8 would amend regulation 12(2) of the NIS Regulations so the RDSP's measures must prevent and minimise the impact of incidents affecting "the security of network and information systems referred to in paragraph (1)", replacing wording about ensuring continuity of services, and would omit regulation 12(2)(c).

New regulation 12(2A): an RDSP must have regard to relevant guidance issued by the Information Commission when carrying out its regulation 12(1) duties.

What this means in practice (our interpretation)

Our reading: the core duty in regulation 12(1), to take appropriate and proportionate measures to manage risks, stays. What changes is that Information Commission guidance becomes something an RDSP must be able to show it considered. Schedule 2 separately revokes the retained EU implementing regulation (EU) 2018/151 on digital service provider security.

Clause 9Managed service providers

Affects: Managed service providers (not micro or small), including non-UK providersOfficial text: HL Bill 62, PDF page 14bills.parliament.uk#clause-9
What the Bill says

Clause 9 would add new regulation 1(3B) to (3D). A "managed service" is a service provided under a contract for ongoing management of a customer's IT systems (support and maintenance, monitoring, active administration or other activities), delivered by the provider connecting to or otherwise accessing network and information systems the customer relies on. It does not matter whether access is on the customer's premises or remote.

Providing a data centre service, or a public electronic communications network or service, is not by itself a managed service.

A relevant managed service provider (RMSP) would be a person that provides a managed service in the UK (whether or not established here), is not designated as a critical supplier for that service, is not a micro or small enterprise, and is either not subject to public authority oversight or derives more than half its income from commercial activities.

Clause 9(6) to (8) would make the Information Commission the competent authority for RMSPs (regulation 3(2) and (4)).

What this means in practice (our interpretation)

Our reading: the test is about ongoing management with access to the customer's systems, not about the label "MSP". Managed security providers (SOC, MDR), outsourced IT support and remote monitoring businesses are the obvious cases. The Explanatory Notes give operational technology examples: remotely managing IT systems that monitor OT would be in scope; supplying OT kit with no IT management would not.

Clause 10Duties of managed service providers to manage risks

What the Bill says

Clause 10 would insert a new Part 4A into the NIS Regulations. New regulation 14B(1): an RMSP must identify and take appropriate and proportionate measures to manage the risks posed to the security of the network and information systems it relies on to provide managed services in the UK.

Regulation 14B(2): the measures must, having regard to the state of the art, ensure a level of security appropriate to the risk, and prevent and minimise the impact of incidents. Regulation 14B(3): an RMSP must have regard to relevant Information Commission guidance.

What this means in practice (our interpretation)

Our reading: this mirrors the RDSP duty. "State of the art" and "appropriate and proportionate" leave room for judgement, so the Information Commission's guidance and any code of practice under clause 37 will set the practical bar. Failure to comply with regulation 14B(1) would carry the higher maximum penalty (clause 21).

Clause 11Digital or managed service providers: meaning of “subject to public authority oversight”

Affects: Public bodies and publicly controlled companies that provide digital or managed servicesOfficial text: HL Bill 62, PDF page 16bills.parliament.uk#clause-11
What the Bill says

Clause 11 would insert regulation 1(3E). A person is subject to public authority oversight if it is subject to the management or control of one or more UK public authorities, or of a board more than half of whose members are appointed by UK public authorities. A UK public authority is a person exercising functions of a public nature in the UK.

What this means in practice (our interpretation)

Our reading: read with clauses 7 and 9, a publicly controlled provider is outside the RDSP or RMSP definition unless more than half of its income comes from commercial activities. A council-owned IT company selling mainly to the open market could therefore still be in scope.

Clause 12Critical suppliers

Affects: Suppliers to regulated organisations, of any size and wherever establishedOfficial text: HL Bill 62, PDF page 16bills.parliament.uk#clause-12
What the Bill says

Clause 12 would insert a new Part 4B into the NIS Regulations. Under regulation 14H, a designated competent authority could designate a person (P) that supplies goods or services directly to an OES it regulates, relies on network and information systems for that supply, and whose systems incident could disrupt essential services (or digital or managed services) with a likely significant impact on the economy or day-to-day functioning of society. The Information Commission could do the same for suppliers to RDSPs and RMSPs.

In deciding, the regulator must have regard to whether the customer could get the goods or services elsewhere (14H(3)) and the likely nature, scale and duration of disruption (14H(4)), and must consider whether the risk could be managed through the customer's own duties or by another regulator (14H(6)). A supplier can be designated whether or not it is established in the UK, and supply outside the UK counts.

Regulation 14I: a person cannot be designated for a service for which it is already an OES, RDSP or RMSP.

Regulation 14J: before designating, the regulator must consult relevant other regulators, give P written notice with reasons and a reasonable period for representations, and have regard to them; then give a notice confirming the decision and the date it takes effect.

Regulation 14K: a regulator may revoke a designation if the criteria are no longer met. A designated supplier that has reasonable grounds to believe it could no longer be designated must notify the regulator in writing, with evidence, as soon as practicable.

Regulation 14L: regulators must co-ordinate with each other on designation and supervision, unless the burden would be disproportionate to the benefit.

What this means in practice (our interpretation)

Our reading: there is no size exemption, so a small specialist supplier could be designated. We found no provision in HL Bill 62 that itself imposes security or incident-reporting duties on critical suppliers. Clause 30(5)(d) treats critical suppliers as "regulated persons" for regulations under clause 29, and clause 69(5) ties the commencement of this clause to the first such regulations that impose requirements on activity-critical suppliers, so the substantive duties are expected to come from those regulations.

Designation and revocation decisions would be appealable to the First-tier Tribunal (Schedule 1, new regulation 19A(2B)).

Not settled by the text. The duties a designated critical supplier would have to meet are not in the Bill; they depend on regulations under clause 29 that have not been published.

Chapter 2Provision of information and reporting of incidents

Clause 13Provision of information by operators of data centre services

What the Bill says

Clause 13 would insert regulation 8ZA. A data centre OES must, within 3 months of becoming deemed or designated as an OES, give its designated competent authority its name, proper address, directors (or partners) and up-to-date contact details, so the authority can maintain its list of OES. Changes must be notified in writing as soon as reasonably practicable and within 7 days.

Clause 13(3) extends regulation 8A (nomination of a UK representative by an OES based outside the UK) to the data infrastructure subsector.

What this means in practice (our interpretation)

Our reading: data centre operators do not "register" with the Information Commission; they notify Ofcom, their competent authority. Missing the deadline would be a standard-maximum failure under clause 21.

Clause 14Provision of information by providers of digital or managed services etc

Affects: RDSPs and RMSPs, including those based outside the UKOfficial text: HL Bill 62, PDF page 23bills.parliament.uk#clause-14
What the Bill says

Clause 14(2) would update regulation 14 (RDSP registration): details must include proper address, directors or partners and which relevant digital services are provided; changes must be notified within 7 days. The registration date is 3 months after clause 14 comes into force for existing RDSPs, or 3 months after first meeting the conditions otherwise. The Information Commission must send the register to GCHQ within 4 months of commencement and annually.

Clause 14(3) to (8) would update regulation 14A: an RDSP with its principal office outside the UK must nominate a UK representative and notify the Information Commission within 3 months, with changes notified within 7 days.

Clause 14(9) would insert regulation 14C (RMSP registration, on the same pattern) and regulation 14D (UK representatives for RMSPs based outside the UK).

What this means in practice (our interpretation)

Our reading: for providers already in scope on the commencement day, the practical deadline is three months from the day clause 14 is brought into force by regulations under clause 69(3). That date has not been set.

Clause 15Reporting of incidents by regulated persons

Affects: OES (including data centres), RDSPs and RMSPsOfficial text: HL Bill 62, PDF page 27bills.parliament.uk#clause-15
What the Bill says

Clause 15(2) would widen the definition of "incident" in regulation 1(2) to cover adverse effects on the "operation or" security of network and information systems.

Clause 15(3) would replace regulation 11 (OES other than data centres) and insert regulations 11A (data centres) and 11B (what regulators and the CSIRT may do with notifications). Clause 15(5) would insert regulations 12A and 12B for RDSPs, and clause 15(7) regulations 14E and 14F for RMSPs.

For each type of regulated person, an incident is notifiable if it has affected or is affecting the operation or security of the systems relied on to provide the service and its UK impact has been, is or is likely to be significant, having regard to factors including disruption, number of users, duration, geographical area, compromise of data, impact on users' systems, and impact on the economy or day-to-day functioning of society. Data centres have their own test in regulation 11A(3): a significant impact on the operation or security of the systems relied on to provide the data centre service, or a significant impact on the operation or security of the data centre service itself through an effect on those systems or on customers' systems.

The regulated person must give its regulator an initial notification (name, service and brief details) within 24 hours of first becoming aware, and a full notification (timing, nature, impact including cross-border impact, any linked incident at another regulated person, and other helpful information, so far as known) within 72 hours of that time. Both must be in writing in the form the regulator determines, and a copy must go to the CSIRT at the same time.

The regulator or CSIRT may tell the public about an incident, or direct the reporting organisation to do so, after consultation; may share information with other regulated persons to prevent similar incidents; and must report annually to the SPOC, by 1 July, on the number and nature of incidents notified.

What this means in practice (our interpretation)

Our reading: the 24-hour clock runs from awareness that a notifiable incident has occurred or is occurring, not from when the incident started. The full notification is due 72 hours from the same starting point, not 72 hours after the initial one. Because the definition still turns on an incident having an effect on the operation or security of systems, a blocked attempt with no effect would not on its own be notifiable.

The CSIRT is the person designated under regulation 5 of the NIS Regulations, which in practice is GCHQ acting through the NCSC.

Clause 16Notification of incidents to customers

Affects: Data centre OES, RDSPs and RMSPs, and their UK customersOfficial text: HL Bill 62, PDF page 39bills.parliament.uk#clause-16
What the Bill says

Clause 16 would insert regulation 11C (data centre OES), 12C (RDSPs) and 14G (RMSPs). After giving a full notification, the provider must, as soon as reasonably practicable, take reasonable steps to establish which of its UK customers are likely to be adversely affected, then notify them.

In deciding who is likely to be affected, it must take into account actual or likely disruption to the service it provides to the customer, likely compromise of data relating to the customer, and any other impact on the customer's systems. The notice must describe the nature of the incident and explain why the customer is likely to be affected. The provider must then give such updates as it considers necessary.

What this means in practice (our interpretation)

Our reading: this applies to data centres, digital and managed service providers, not to other OES such as energy or water operators. The trigger is the full notification, so in practice customer notices will follow the regulatory report rather than precede it. Failing to notify carries the higher maximum penalty; failing to give updates carries the standard maximum (clause 21).

Chapter 3Other amendments

Clause 17Powers to impose charges

Affects: All persons regulated by a NIS enforcement authorityOfficial text: HL Bill 62, PDF page 41bills.parliament.uk#clause-17
What the Bill says

Clause 17 would insert a new Part 5A (regulations 20A to 20C). A NIS enforcement authority could impose periodic charges under a published charging scheme for its relevant costs, including costs of functions under Parts 3 and 4 of the Bill and preparatory costs incurred before the clause comes into force. The scheme must specify the functions, chargeable periods, amount or method, when and how to pay, and a start date at least 14 days after publication.

A charge need not relate to functions exercised in relation to the payer. Before making or revising a scheme (other than minor revisions) the authority must consult such regulated persons as it considers appropriate. Where turnover is used, the authority's figure prevails in a disagreement. Charges are recoverable as a civil debt, and the authority must publish a statement of charges received, outstanding and costs.

Regulation 20C: an authority could also invoice a regulated person for costs of exercising a function in relation to it, but not for appeals, civil proceedings it brings, or functions covered by its charging scheme.

What this means in practice (our interpretation)

Our reading: in-scope organisations should budget for an annual fee as well as compliance costs. Because charges need not relate to work done on the payer, the regime can spread a regulator's general costs across everyone it regulates.

Clause 18Sharing and use of information under the NIS Regulations etc

Affects: Regulators; indirectly every regulated person whose information they holdOfficial text: HL Bill 62, PDF page 44bills.parliament.uk#clause-18
What the Bill says

Clause 18(1) would require competent authorities to send the lists they keep under regulation 3(3)(c) and (d) to GCHQ to help it exercise its functions, within 4 months of clause 18(1) coming into force and then annually. Clause 18(2) would let the SPOC deal with relevant authorities in any country outside the UK, not only EU member states.

Clause 18(3) would replace regulation 6 and add 6A and 6B. NIS enforcement authorities could share information with each other, the Secretary of State, relevant law-enforcement authorities, the CSIRT and other UK public authorities for purposes including the Regulations, cyber security and resilience generally, national security, and the prevention, detection, investigation and prosecution of crime. Disclosures to overseas law-enforcement or regulators are limited to Australia, Canada, EEA states, New Zealand, Switzerland and the United States.

Onward disclosure is restricted; disclosures must be relevant and proportionate; and nothing authorises a disclosure prohibited by the Investigatory Powers Act 2016. The Information Commission could use NIS information for its other functions where necessary and proportionate (regulation 6B).

Clause 18(4) makes similar changes to regulation 7 (Northern Ireland).

What this means in practice (our interpretation)

Our reading: anything you give a NIS regulator, including incident reports, could reach the NCSC, other regulators and in some cases police or listed foreign authorities. Regulation 6B means information given to the Information Commission as NIS regulator could inform its data protection work.

Clause 19Guidance

Affects: Regulators; regulated persons who rely on their guidanceOfficial text: HL Bill 62, PDF page 49bills.parliament.uk#clause-19
What the Bill says

Clause 19 would amend regulation 3. Competent authority guidance must in particular cover security measures under regulation 10, OES incident reporting under regulation 11, and the data centre duties in regulations 8ZA, 11A and 11C. Information Commission guidance must cover RDSP and RMSP security measures, registration, incident reporting and customer notification.

Regulators must have regard to any code of practice under clause 37 so their guidance is consistent with it, and must co-ordinate and consult each other on guidance about critical suppliers. New regulation 3A: regulators must have regard to relevant guidance published by the Secretary of State.

What this means in practice (our interpretation)

Our reading: expect sector guidance to be the main practical source for what "appropriate and proportionate" means, with the code of practice sitting above it.

Clause 20Powers to require information

Affects: Regulated persons and anyone likely to hold relevant informationOfficial text: HL Bill 62, PDF page 51bills.parliament.uk#clause-20
What the Bill says

Clause 20 would replace regulation 15 and add regulation 15A. A competent authority or the Information Commission could, by written information notice, require a person it regulates, or any other person (other than the SPOC or CSIRT) likely to hold the information, to provide information or documents it reasonably requires for its functions. Listed purposes include establishing whether someone is in scope or should be designated, assessing security, investigating incidents, assessing measures, identifying failures, and setting penalties or charges.

A notice must say what is sought and why, the form, the deadline and the consequences of not complying. Notices to unregulated persons can be general and published. The power includes requiring a person to obtain, generate, collect or retain information, applies to persons outside the UK and to information stored outside the UK, and does not extend to legally privileged communications.

What this means in practice (our interpretation)

Our reading: the regulator can use these powers before deciding whether you are in scope, so a supplier or a company that believes it is out of scope could still receive a notice. Failing to comply with an information notice would carry the higher maximum penalty under clause 21, not the standard one.

Clause 21Financial penalties

Affects: OES, RDSPs, RMSPs and anyone given an information or enforcement noticeOfficial text: HL Bill 62, PDF page 54bills.parliament.uk#clause-21
What the Bill says

Clause 21 would amend regulation 18. A penalty must be appropriate and proportionate, having regard to the impact of the failure, steps taken to remedy or mitigate it, and the person's compliance history.

Standard maximum (new regulation 18(8)): for an undertaking, the greater of £10,000,000 and 2% of worldwide turnover; otherwise £10,000,000. It applies to failures listed in regulation 18(10), including OES notification and representative duties (regulations 8(2), 8ZA, 8A), copying notifications to the CSIRT (11(8), 11A(8), 12A(7), 14E(7)), RDSP and RMSP registration and representative duties (14, 14A, 14C, 14D), onward-disclosure restrictions and customer update duties (11C(5), 12C(4), 14G(4)).

Higher maximum (new regulation 18(9)): for an undertaking, the greater of £17,000,000 and 4% of worldwide turnover; otherwise £17,000,000. It applies to failures listed in regulation 18(11), including security duties (regulations 10, 12(1), 14B(1)), incident notification and its timing and form (11, 11A, 12A, 14E), directions to inform the public, customer notification (11C(2)(b), 12C(1)(b), 14G(1)(b)), inspection directions and requirements (regulation 16), information notices (17(2ZB)) and enforcement notice requirements (17(3A)).

New regulation 18(2A) and (2B) would let the Information Commission penalise RMSPs, and any regulator penalise a person who fails to comply with its information notice or enforcement notice.

What this means in practice (our interpretation)

Our reading: "4% of turnover" is a cap, not a tariff, and the turnover is worldwide. Failing to answer an information notice or to co-operate with an inspection sits in the higher band. These caps apply to the NIS Regulations only: regulations under clause 29 may set caps up to the greater of £17m and 10% (clause 33), and Part 4 directions have their own penalties (clause 54).

Clause 22Enforcement and appeals

Affects: OES, RDSPs, RMSPs, critical suppliers and recipients of information noticesOfficial text: HL Bill 62, PDF page 58bills.parliament.uk#clause-22
What the Bill says

Clause 22 gives effect to Schedule 1, which contains further amendments to the NIS Regulations on enforcement and appeals. See Schedule 1 below.

Clause 23Minor and consequential amendments etc

What the Bill says

Clause 23 gives effect to Schedule 2, which contains minor and consequential amendments to the NIS Regulations and other enactments. See Schedule 2 below.

SchedulesSchedules introduced by this Part

Schedule 1Enforcement and appeals

What the Bill says

Paragraph 2 amends regulation 16 (inspections) to cover RMSPs, requires an inspector to give notice of the consequences of non-compliance before inspecting, protects privileged communications, and confines powers over premises, equipment and people to the UK (documents and information can be stored anywhere).

Paragraph 3 rewrites regulation 17 (enforcement notices): new grounds for OES and RDSPs matching the new duties, a new regulation 17(2ZA) for RMSPs, a new 17(2ZB) for any person failing to comply with an information notice, steps that may be required outside the UK, and a duty to comply with an enforcement notice whether or not a penalty has been paid.

Paragraphs 4 and 5 amend regulations 19A and 19B so that RMSPs, and any person designated as a critical supplier or served with an information-notice enforcement or penalty notice, can appeal to the First-tier Tribunal, including against designation and revocation decisions.

Paragraphs 6 and 7 amend regulation A20 (civil proceedings) and regulation 23 (general considerations for enforcement) so they apply to any person served with an enforcement notice.

What this means in practice (our interpretation)

Our reading: the enforcement toolkit is the existing 2018 one, extended to the new categories. The new right to appeal a critical supplier designation is the main new protection for suppliers.

Schedule 2Minor and consequential amendments etc

What the Bill says

Paragraphs 1 to 14 amend the NIS Regulations: new definitions of "CSIRT" and "SPOC"; omission of regulation 2 (the NIS national strategy) and regulation 3(6); "principal office" in place of "head office" for OES representatives with 7-day change notices; removal from regulation 10(2) of the words "with a view to ensuring the continuity of those services"; omission of regulations 21 and 25; and a rewritten regulation 24 on serving documents, including by email (treated as given at 9am on the next working day).

Paragraph 15: regulations 2 and 3(6) continue to have effect until the first statement of strategic priorities is designated under clause 25.

Paragraph 16 amends Schedule 15 to the Enterprise Act 2002; paragraph 17 revokes Commission Implementing Regulation (EU) 2018/151.

What this means in practice (our interpretation)

This is the Bill's Schedule 2. It does not contain the data centre or sector thresholds: those are in Schedule 2 to the NIS Regulations, amended by clauses 4 and 6. Citing "Schedule 2" for the 1 MW threshold without saying "to the NIS Regulations" is ambiguous.

Get ready

Know where you stand before the duties land.

Take the free readiness assessment to see how your organisation measures up against the Cyber Security and Resilience Bill, or talk to our team about a plan.