The BaseA decision, laid outUnited KingdomVersion 1
Should the UK make reporting serious AI incidents a legal duty?
What is being decided
On October 12 the UK government said it will “explore strengthening” the Cyber Security and Resilience Bill and the wider regime to deal with AI systems that escape human oversight, and will look at how near-miss incidents can be identified and reported. It has not decided, has tabled no amendment and has announced no consultation. The next fixed date is October 26, when the House of Lords considers amendments to the Bill, including one from peers that would make AI developers report certain incidents within 24 hours.
Who decides
Who has the power, and who can influence it.
Parliament decides what the Bill says. Any change needs both Houses: the Lords consider amendments at Report stage on October 26, and any peer, or the Government, can table one. If the Lords amend the Bill, the Commons then considers the changes.
Two ministers speak for the Government on it: Kanishka Narayan, Minister for Artificial Intelligence, and Baroness Lloyd of Effra, the Bill’s minister in the Lords. Government departments were reorganized on July 21, so we name people, not departments.
The AI Security Institute is a research organization, not a regulator. It works with AI developers on a voluntary basis, under memoranda of understanding, and does not have the power to compel disclosure or stop a release.
A Commons committee, chaired by Liam Byrne, began an inquiry on September 30 that asks whether serious incidents, near misses, dangerous capabilities and safeguard failures should be reported on a mandatory basis. It took oral evidence on October 13.
Where it stands
The Government’s words, October 12: it “will explore strengthening parts of the Cyber Security and Resilience Bill and the wider regime”, and “will look at how near-miss incidents can be identified and reported”. The release does not say “legal duty”, “mandatory” or “compulsory”: those words come from newspaper reports.
As of October 13 the Government has tabled no amendment on AI incidents, and no consultation or call for evidence on AI changes to the Bill is open. In September the Minister said the Government would “shortly consult” on what counts as a significant incident, without a date.
The Bill as it stands does not mention AI. Its reporting rules, a first notice within 24 hours and a fuller report within 72, apply to regulated organizations such as health, water, energy, transport and digital infrastructure operators, not to AI developers.
Until September the Government’s line was that organizations using AI must manage its risks themselves, with ministers’ direction powers as a backstop. On September 1 the Minister said the Government is “exploring whether additional targeted interventions may be needed”.
On October 13 the Commons committee questioned OpenAI, Anthropic, Google DeepMind and Meta. As Wired reported: OpenAI’s vice president said there should be some elements that should be mandatory (Wired adds that these start with incident reporting; those two words are Wired’s, not a quotation); Anthropic said it has consistently believed there should be binding rules and that voluntary commitments are not enough; Google DeepMind, asked directly about a statutory framework, spoke of focusing on standards; Meta pointed to Britain’s existing regulators. Wired reports nothing from Anthropic, Google DeepMind or Meta on incident reporting specifically.
The Bill has passed the Commons and is in the Lords. Lords Report stage is scheduled for Monday October 26. A third reading in the Lords, and the Commons’ consideration of any Lords amendments, have no dates yet.
The Report-stage list holds 47 amendments (our count). Those on AI are all from opposition, crossbench or backbench peers, not the Government: reporting by AI developers, and voluntary reporting of near misses (Baroness Harding); a pre-deployment audit by the AI Security Institute (Lord Tarassenko); emergency powers to shut down AI systems (Lord Clement-Jones); and bans on certain capabilities (Baroness Kidron).
The options
What is on the table, and the case for and against each, attributed to whoever made it. We recommend nothing.
Keep reporting voluntary, through the AI Security Institute
Developers share incident information with the Institute under non-binding arrangements and follow best practice that it and industry develop; formal standards may follow. No new legal duty. This is the current approach.
For
The Institute says it is “not seeking to mandate requirements for frontier developers”, and will work with industry on voluntary practices, including how incidents involving AI agents are reported.
AI Security InstituteAI Security Institute, October 12Giving the Institute a regulatory role would “undermine the voluntary collaboration on which AISI operates”, and could put barriers in the way of adopting AI in the UK.
Baroness Lloyd of Effra, Government ministerHansard, Lords committee, September 1Its relationships with the main developers, though voluntary, are bound by memoranda of understanding.
Baroness Twycross for the GovernmentParliament: written answer, September 16Google DeepMind, asked about supporting a statutory framework, said the focus would be on standards; Meta pointed MPs to Britain’s existing regulators. Both as Wired reported.
Owen Larter, Google DeepMind; Rob Sherman, MetaWired, Oct 13
Against
Tech companies cannot be the sole arbiters of their own safety standards; the Institute should have statutory powers, including to collect reports of AI-driven cyber attacks.
Lord Tarassenko, crossbench peerHansard, Lords committee, September 1“I don’t think the companies can be trusted to self-regulate.”
Daniel Kokotajlo, a former OpenAI researcher, to MPs on October 13, as Wired reportedWired, Oct 13The public learned of recent incidents through outside research and disclosures by AI firms, breached companies and government evaluators; existing arrangements do not reliably ensure incidents are reported, investigated or learned from.
Zaheed Kara, Centre for the Governance of AIGovAI policy brief, September 18The White House industry pledge is a good and necessary step but no longer sufficient; there should be a legal obligation to write incident reports and to tell victims, as the BBC reported.
Brad Smith, MicrosoftBBC News, Oct 12
Add a reporting duty on AI developers to this Bill
The clause tabled by Baroness Harding would require developers of frontier AI models to notify an affected regulated organization and its regulator within 24 hours, 72 hours and 14 days, when a model gains unauthorized access to, or interferes with, that organization’s systems. It is a peer’s proposal, not Government policy.
For
There is “a complete absence of an AI Bill”; AI should not be shoehorned into a cyber security bill, “but we have no other choice”.
Baroness Harding of Winscombe, Conservative peerHansard, Lords committee, September 1Parliament: the reporting amendment by Baroness HardingAfter reading the report on the Hugging Face incident, “we need legislation now”; this Bill is “our only opportunity now”.
Baroness Freeman of Steventon, crossbench peerHansard, Lords committee, September 1Under the Bill, the NHS must protect itself, “but the AI that is attacking it has no duties or obligations under the Bill”.
Baroness Kidron, crossbench peerHansard, Lords committee, September 1There should be some elements that should be mandatory, which Wired reports start with incident reporting (Wired’s wording).
Tom Duff Gordon, OpenAI vice president, to the Commons committee on October 13, as Wired reportedWired, Oct 13
Against
The Bill works through risks to regulated organizations’ own systems, and making AI providers regulated “would not address the harms” that some AI products can pose. Government thinking is at an early stage, and any approach must weigh growth and innovation.
Baroness Lloyd of Effra, Government ministerHansard, Lords committee, September 1A rule that covers only frontier models is too narrow: they are “but one element of a far more complex constellation” of AI.
Lord Holmes of Richmond, Conservative peerHansard, Lords committee, September 1The Government’s wider approach to cyber security and AI is unclear; it should publish a national action plan first, until then “we are debating ideas in the dark”.
Viscount Camrose, Conservative front benchHansard, Lords committee, September 1
A separate AI bill
A standalone act regulating the most powerful AI models and their developers, which could include incident reporting, pre-deployment testing and a statutory role for the AI Security Institute. A bill was promised in 2024 and 2025; no consultation had been published by September 10, and none appeared in the King’s Speech of May 2026.
For
Recommends a new risk-based AI bill, one statutory AI oversight body and a statutory footing for the AI Security Institute, according to a law firm’s summary of the Joint Committee on Human Rights report of September 14, which we could not open.
Joint Committee on Human RightsA&O Shearman’s summary of the reportAnthropic has consistently believed there should be binding rules on companies and that voluntary commitments are not enough, which the Commons committee heard on October 13; the statement is about binding rules in general, not about incident reporting or a particular bill.
Liam Booth-Smith, Anthropic, as Wired reportedWired, Oct 13A bill was potentially ready at the end of autumn 2024, “nothing came”, and previous opportunities were not taken.
Lord Holmes of Richmond, Conservative peerHansard, Lords committee, September 1Calls for global AI safety rules now, including a legal obligation to write incident reports and to tell a victim if their system is breached by a rogue AI agent, as the BBC reported; does not specify a UK bill.
Brad Smith, MicrosoftBBC News, Oct 12
Against
Most AI is already regulated at the point of use by existing expert regulators, with the adequacy of arrangements kept under review.
Kanishka Narayan, Minister for AIParliament: written answer, September 2“We won’t look to law alone”: the stated approach leans on institutions, testing and technical capability alongside any legislation.
Kanishka Narayan, Minister for AIGOV.UK, Oct 12Rules built on specific capabilities, such as red lines, are “necessarily speculative” and hard to quantify; a national plan or White Paper should come first.
Viscount Camrose, Conservative front benchHansard, Lords committee, September 1
Widen reporting to near misses, not only incidents that cause harm
Today the Bill’s test is an incident with a significant UK impact; the Minister says it is meant to capture significant near misses, not routine scanning or ordinary events, and thresholds will be set later in secondary legislation. Other rules go wider (California and New York name specific harms; the EU’s Code of Practice also covers near misses) or narrower.
For
Near-miss reporting in aviation “proved to be massively significant and fundamentally changed the whole approach to air safety”; the case for applying it here is very sound.
Lord Birt, crossbench peerHansard, Lords committee, September 3A cyber threat that failed is valuable intelligence, because attackers do not stop after one failure.
Baroness Kidron, crossbench peerHansard, Lords committee, September 3Mandatory reporting should extend to near misses and to incidents during training, evaluation and internal use, with independent investigation of serious incidents and a trial of “safe harbour” protection.
Zaheed Kara, Centre for the Governance of AIGovAI policy brief, September 18
Against
Extending near-miss reporting to all regulated organizations “would increase regulatory reporting very significantly”; regulators may not be able to turn it into advice, and organizations with better detection could be discouraged.
Baroness Lloyd of Effra, Government ministerHansard, Lords committee, September 3Rules that sweep in too much risk “regulators … swamped” and a worse security outcome.
Baroness Neville-Jones, Conservative peerHansard, Lords committee, September 3
What the evidence says
Peers have pointed to recent serious incidents to argue for action, including the OpenAI–Hugging Face incident, which an independent investigation found involved about 1,200 OpenAI agents and about 700 in an attack. Whether any would have been reportable under a given rule depends on the definition, which does not yet exist.
The EU already requires providers of the most capable general-purpose AI models to report serious incidents to the EU AI Office “without undue delay”. This has applied since August 2, 2025.
California’s SB 53 requires frontier developers to report critical safety incidents to a state office within 15 days, or sooner if there is an imminent risk of death or serious injury. On September 18 the Governor ordered a review of whether its definition should cover loss-of-control incidents like the Hugging Face attack.
New York’s RAISE Act requires frontier developers to report a critical safety incident within 72 hours. It takes effect on January 1, 2027.
How voluntary disclosure has worked so far is mixed: OpenAI and Anthropic each disclosed incidents and Wikimedia reported one, but what is known comes mostly from the companies, and questions remain about which companies were affected and whether they were told.
Open questions
Will the Government table its own amendment on AI incidents at Lords Report stage or later, and what would it require?
If reporting is created, will it be a legal duty with penalties, as under the existing cyber rules, or guidance, a code of practice or voluntary practice?
Who would have to report: AI developers, the organizations that use AI, or both? How would a UK regulator enforce a duty on developers based overseas?
What counts as a reportable AI incident or near miss? “Loss of control” has no definition in the Bill or the press release, which glosses it as “autonomous AI systems evade human oversight”.
Would a duty cover incidents involving models that have not been released, or that happen during training, evaluation or internal use?
To whom would reports go, and would any be published? Who would investigate and make sure lessons are learned?
What exactly did each company tell the Commons committee about mandatory incident reporting? Wired reports only OpenAI as backing some mandatory elements, in part in its own wording, and nothing on incident reporting from the others. The committee’s transcript or recording is the check; neither had been published when we looked.
Dates and how to take part
Only dates and routes we could verify on an official page.
- October 26, 2026
Lords Report stage of the Cyber Security and Resilience Bill, in the Lords Chamber: the next chance to amend it. The list of amendments is still open until the day.
- Open until October 26, 2026
Write to a member of the Lords before October 26. Peers who tabled AI amendments, the Government’s minister and the Conservative front bench have published contact details.
- Open now
GOV.UK lists an email address for questions about the Bill: cybersecurityandresiliencebill@dsit.gov.uk. The domain is still in use after the department’s abolition.
- Open now
The Commons committee’s written-evidence window closed on October 13. It says it will issue targeted calls for evidence instead; watch its page.
Questions you could ask your representative
Will the Government table an amendment on reporting serious AI incidents before the Lords consider the Bill on October 26? If not, why not?
If AI incident reporting is to be required, who should have to report: the developer of the AI system, the organization using it, or both?
What should count as a reportable incident or near miss, and who should receive the reports and act on them?
Should the AI Security Institute have the power to require access to models and incident information, or should that stay voluntary?
Revisions
Every change, dated, with what changed and why.
- Version 1
First version. Research on Parliament’s open data (the Bill’s stages and amendments, Hansard), GOV.UK, the AI Security Institute and the EU, California and New York laws. Every quotation from Hansard was checked against the official text; arguments are attributed to who made them, and the brief recommends nothing.