UK cybersecurity

The Lords Are Right That the Cyber Bill Is Too Narrow, but Wider Scope Needs Resourced Regulators

A Lords committee calls the UK government complacent on state-backed cyber threats. The fix is wider scope with regulator capacity behind it, not more statute.

UK Cyber Security and Resilience Bill People of Internet Research · UK 4% Maximum fine, % turnover Or £17m, whichever is higher, for … 24 hrs Initial incident notification Down from 72 hours under the curre… 202-155 Lords vote for annual review Amendment 163 defeated the governm… 194-155 Lords vote for threat register Amendment 164 on a register of for… peopleofinternet.com
UK Cyber Security and Resilience Bill People of Internet Research · UK 4% Maximum fine, % turnover 24 hrs Initial incident notification 202-155 Lords vote for annual review 194-155 Lords vote for threat register peopleofinternet.com

Key Takeaways

On 16 November 2026, eight days before a major vote on the Cyber Security and Resilience Bill, the House of Lords National Resilience Committee published a report calling the UK "underprepared" for "potentially catastrophic risks", including cyberattacks from Russia, China and Iran. It said the government "appears complacent", according to The Record's coverage. It also said the bill "would provide useful baseline requirements" but that "its scope is limited".

The strongest case for the committee

The case for acting faster is serious. The committee argues that the public lacks "a full picture of the level and frequency of current sub-threshold hostility" from the three states. It lists cyberattacks, proxy violence and threats to undersea cables and pipelines. The bill has been in development for more than five years, and it was introduced to the Commons on 12 November 2025. Over that time, adversaries have not waited for Parliament. A regime that covers too few entities leaves the weakest link in a supply chain unregulated, and attackers target the weakest link. The committee's call to "widen the scope of cyber security regulation" has force.

What the bill actually does

The bill reforms the Network and Information Systems Regulations 2018. Government factsheets describe a two-stage incident reporting model. Regulated entities must give an initial notification "within 24 hours of becoming aware" and a full report after 72 hours. The current regime allows 72 hours for the first notification. The bill also makes ransomware and pre-positioning attacks reportable, rather than only incidents with an immediate service impact. It brings in relevant managed service providers and data centres alongside the existing operators of essential services.

The enforcement factsheet sets maximum penalties at up to £17 million or 4% of worldwide turnover, whichever is higher, for more serious breaches. For less serious breaches the maximum is £10 million or 2%. The same page says the aim "is not the widespread use of fines". It also says that how turnover is determined, and what counts as a "significant" incident, will be set in secondary legislation after consultation.

The Lords have already pushed back

In October, peers defeated the government twice. VinciWorks reports that Amendment 163, tabled by Lord Birt, passed 202 to 155. It would require a review of the legislation within 12 months of Royal Assent, followed by annual reviews. Amendment 164 passed 194 to 155. It would require the government to establish and maintain a register of foreign powers presenting cyber threats to the UK. ISACA's analysis notes that both remain subject to further parliamentary consideration.

Where the committee's logic stops

The diagnosis is persuasive. The remedy needs more care, and three points matter.

Scope without capacity is a paper exercise. The committee itself says regulators need "sufficient resources and capacity to enforce requirements effectively". That sentence matters more than the call to widen scope. A statute that adds entity types but leaves sector regulators short of technical staff produces compliance paperwork, not resilience. Companies spend money on lawyers and audits, and the attacker keeps the advantage. Ministers should resource the regulators already responsible before they add new categories.

Annual statutory review is a reasonable discipline, and a good one for fast-moving technology. Regulation tied to a 2018 regime should be tested against evidence. The review amendment is the kind of evidence-based feedback loop we favour. It should ask whether the 24-hour notification rule produces useful intelligence or only noise. It should not become a standing invitation to ratchet obligations upward.

A register of hostile states is a policy choice with trade-offs. The government's stated objection, as reported, is that a country list can create false certainty. Attackers route through third countries and criminal proxies, and a fixed list can lag behind them. A register also carries commercial costs. Firms that operate in several markets would have to treat suppliers differently depending on a list that diplomats, not security engineers, would shape. If a register is built, its purpose should be narrow, and it should feed risk assessment rather than blanket procurement bans.

What proportionate looks like

The committee's strongest demand is transparency: the government should "stop being squeamish about telling it straight to the public". Honest threat reporting costs little and helps firms prioritise spending. It also supports the innovation-friendly alternative to heavy prescription, which is for the state to share intelligence and for firms to adopt outcome-based security standards.

A proportionate approach would do four things. First, publish regular, plain-language threat assessments, with detail on sub-threshold hostility. Second, fund regulators before extending scope. Third, set the secondary-legislation thresholds for "significant" incidents through real consultation, so firms are not flooded with reporting duties that exceed the value of the data. Fourth, accept the review clause and use it to ask what is working.

The committee is right that the government has been slow, and its criticism should be heard. The risk is that Parliament reads "underprepared" as a case for more legislation. The better reading is that the bill is a sound baseline that is short of capacity, openness and a feedback mechanism. Those can be added without turning a resilience statute into a general compliance burden on every digital business.

Sources & Citations

  1. The Record: British government 'complacent' on cyber threats
  2. GOV.UK: Bill factsheet on enforcement
  3. GOV.UK: Bill factsheet on incident reporting
  4. VinciWorks: Government defeated twice as Lords demand stronger protections
  5. ISACA: Five key takeaways from Lords Report Stage