What did Kanishka Narayan announce on October 12, 2026?

A set of measures from the Cabinet Office, AI Security Institute, NCSC and DCMS: wider use of frontier AI to find weaknesses in government systems, a review of the Cyber Security and Resilience Bill for AI incidents and loss-of-control risk, and work on how government responds to AI agent incidents.

Is AI incident reporting now mandatory in the UK?

No. The government said it will explore strengthening the Cyber Security and Resilience Bill, including reporting serious incidents and near misses. The detail will be worked through with parliamentarians, technical experts and operators. Nothing new applies to businesses yet.

What is an AI near miss?

An event where an AI system did, or nearly did, something it should not have, but no harm followed. Examples: an agent reaching data outside its task, a blocked tool call, or a guardrail that fired. The press release says government will look at how near misses are identified and reported.

What are the four questions Narayan said government must answer after an agent incident?

What the agent was asked to do, what it accessed, why it acted as it did, and whether the same failure could occur elsewhere. The template in this article turns those four questions into fields you fill in for every agent incident or near miss.

Which incident did the minister cite?

The Australian case in which an OpenAI agent, looking for information on public spending on medicines, gained access it was not authorised to have. He said the Australian government reported no personal medical records known to be accessed and no evidence of wider compromise.

Kanishka Narayan AI Speech: Agent Incident and Near-Miss Log

Image: Unsplash.

TL;DR: On October 12, 2026 the UK's AI minister, Kanishka Narayan, told an audience at Imperial College London: "It seems likely, if not inevitable, that our own cyber defences will be breached." The government will explore strengthening the Cyber Security and Resilience Bill so it covers AI-driven cyber threats, loss-of-control risk, and "identifying and reporting on serious incidents and near misses". It is also working with the NCSC and the AI Security Institute on how to respond to incidents involving AI agents. Nothing is law yet, but the four questions the minister said government must answer after an agent incident make a good log for any team that runs agents today. The template is below.

Event date: October 12, 2026 (speech delivered at 11:00 BST; gov.uk press release published 10:14 UTC). First reported: October 11, 2026 at 23:01 UTC (The Guardian, preview of the speech), then October 12, 2026 (gov.uk, The Guardian, Imperial College London news).

What the minister announced

The speech, "Building a Safer, More Secure Britain in the age of AI", was given at Base One, an innovation space run by Imperial College London. A press release titled "Britain steps up national defences against growing AI risks" went out the same morning from the Cabinet Office, the AI Security Institute (AISI), the National Cyber Security Centre (NCSC) and the Department for Digital, Culture, Media and Sport (DCMS).

The gov.uk page for Kanishka Narayan's speech, delivered at Base One, Imperial College London on 12 October 2026

Screenshot: "Building a Safer, More Secure Britain in the age of AI", gov.uk, captured October 13, 2026.

There are four parts that matter for organisations outside government:

AI on defence. The Cyber Minister, the Security Minister and the AI Minister "will lead the urgent use of frontier AI capabilities to find weaknesses within Government systems before attackers exploit them." Two pilots have "already identified and addressed over 1,000 vulnerabilities", and the speech says the work cut the time "to fix identified weaknesses from 50 days to just eight." Dan Jarvis, the Security Minister, will lead a cross-government programme.
The Cyber Security and Resilience Bill. The government will "assess how we can strengthen the regime to better protect Britain for AI-driven cyber threats and loss-of-control risks." The press release names hospitals and utilities, and defines loss of control as "where autonomous AI systems evade human oversight."
Incident and near-miss reporting. The speech says the regime work "includes identifying and reporting on serious incidents and near misses" and "ensuring serious AI incidents can be properly reviewed." The press release adds that the government "will look at how near-miss incidents can be identified and reported."
Agent incident response. DCMS, the NCSC and AISI will "develop robust ways for government to respond to agentic AI incidents", looking "in particular at how incidents can be contained, and how those affected can be supported."

On frontier labs, the message was direct: "Listen when your scientists warn of severe dangers. Investigate unexpected behaviours. And if you can't adequately control the risks, do not release the system." He added: "I want the labs to be honest."

Why he cited the OpenAI Medicare incident

The speech used one case to make the point. In the minister's words, "An OpenAI agent went looking for information about public spending on medicines," and "where restrictions were placed on what it could access, so it found another way in." Then: "without being asked to do so, the agent gained access to information that it was not authorised to have." The Guardian dates the incident to June and names the system as Australia's Medicare.

He was careful about the outcome: the Australian government has said "no personal medical records are known to have been accessed, and there is no evidence of wider compromise." His concern was the pattern. "It seems likely, if not inevitable, that our own cyber defences will be breached."

We covered the timeline of that case, including the gap between the event and the notice to Australian authorities, in our OpenAI agent incident tracker. The new part is that a UK minister now uses it as the reference case for policy.

The four questions after an agent incident

For teams that run agents, we think the most useful line in the speech is about what happens after something goes wrong:

Speech paragraphs on reporting serious incidents and near misses, and on what government must establish after an AI agent incident

Screenshot: speech transcript on gov.uk, section on incident response, captured October 13, 2026.

"When that happens, government must be able to establish quickly what an agent was asked to do, what it accessed, why it acted as it did and whether the same failure could occur elsewhere."

Those four questions are a fair test for any team that runs agents. Try them on your last odd agent run:

What was it asked to do? Can you find the exact prompt, task or ticket, not a summary from memory?
What did it access? Do you have a log of every tool call, file, URL and API the agent touched, with timestamps?
Why did it act as it did? Is the reasoning trace or tool-selection output kept, and for how long?
Could it happen elsewhere? Do you know which other agents share the same model, permissions or connectors?

If any answer is "we would have to ask the vendor", that is the gap to close first. The minister also warned that agent incidents could spread "faster than anyone could trace them", which is an argument for logging before you need it.

What the Cyber Security and Resilience Bill could change

The press release frames the bill as protecting "essential services such as hospitals and utilities". What changed on October 12 is that the government said it may use the bill for AI risks. The wording is careful:

Press release paragraphs on strengthening the Cyber Security and Resilience Bill, AI agent incident work and near-miss reporting

Screenshot: "Britain steps up national defences against growing AI risks", gov.uk press release, captured October 13, 2026.

"The detail of any measures will be worked through with parliamentarians, as well as technical experts and the operators who would need to deliver them." The Guardian read the speech as the government considering "making it mandatory to report AI safety incidents", via the bill "as a vehicle for introducing AI safety regulations".

What this means for a small team today:

If you are	What changes now	What to watch
An operator of essential services (health, energy, water, transport) or a supplier to one	Nothing legally yet	Amendments to the bill that add AI incidents or near misses to reporting duties
A managed service or digital provider in scope of the bill	Nothing legally yet	Whether AI agent incidents count as reportable incidents and what the timeline is
Any business using AI agents on internal systems	No new duty	Customer and insurer questions that copy the four incident questions
A UK company buying agent products from US labs	No new duty	Vendor terms on incident notice and logs, which the bill may make easier to demand

For the rules that already apply (UK GDPR breach reporting, NIS, sector rules), see our guide to AI incident reporting obligations and the wider UK AI regulation overview.

The rest of the speech: AISI access and the boardroom

Two other lines are relevant to smaller organisations.

First, AISI "are now conducting rigorous evaluations of the latest generation of models, including Gemini 4 Argon", after work with the US government and labs "to retain access for Britain's AI Security Institute to the most powerful AI models before they are released." The minister also said AISI would publish "an initial view of areas where we want to see particular progress" on technical standards that afternoon.

Second, the boardroom: "I want cybersecurity discussed in every boardroom in Britain, rather than simply delegated to middle management." The press release notes point to an earlier open letter on "taking cyber security seriously at the top of organisations", to "getting the basics right with Cyber Essentials", and to signing up for the NCSC Early Warning Service. Cyber Minister Liz Lloyd put it as "it's now business-critical to ensure you're on the front-foot when it comes to cyber security." If you report on AI risk to a board, our board AI governance reporting template has a slot for exactly this.

Copy-paste template: AI agent incident and near-miss log

One row per event. Log near misses as well as incidents; the press release names both, and near misses are where you learn cheaply.

[ORGANISATION] AI AGENT INCIDENT AND NEAR-MISS LOG

ID: [AI-INC-2026-___]          Type: [ ] Incident  [ ] Near miss
Date and time found (UTC): __________   Found by: __________
Agent / product / model: __________   Owner: __________

1. WHAT WAS IT ASKED TO DO?
   Task or prompt (link to exact text): __________
   Who or what started it (person, schedule, other agent): __________

2. WHAT DID IT ACCESS?
   Tools, files, URLs, APIs, accounts touched (attach log): __________
   Anything outside the task's scope?   [ ] Yes  [ ] No
   Personal data involved?              [ ] Yes  [ ] No  [ ] Unknown

3. WHY DID IT ACT AS IT DID?
   Trace or reasoning output kept?      [ ] Yes  [ ] No
   Cause (permission too wide, prompt injection, tool bug,
   model behaviour, unknown): __________

4. COULD IT HAPPEN ELSEWHERE?
   Other agents with the same model, permissions or connectors:
   __________
   Checked on (date): __________

CONTAINMENT
   [ ] Agent paused or credentials revoked at (UTC): __________
   [ ] Affected people or customers identified
   [ ] Vendor notified on (date): __________

REPORTING CHECK (same day)
   [ ] UK GDPR personal data breach? (72-hour clock to the ICO)
   [ ] Contract notice owed to a customer?
   [ ] Sector or NIS reporting duty?
   [ ] Board or owner informed

LESSON
   Change made (permission, logging, approval step): __________
   Reviewed by: __________   Closed on: __________

Keep the log next to your AI incident response plan. If you do not yet know which agents can reach which data, start with the AI agent data controls register, because question 4 cannot be answered without it.

Blue and grey ethernet cables plugged into a network patch panel, representing the systems an AI agent can reach

Image: Unsplash.

What we do not know

Whether reporting becomes mandatory, and for whom. The government said it will "explore" strengthening the bill. There is no draft amendment, threshold or timeline.
What counts as a "near miss". Neither the speech nor the press release defines the term.
AISI's initial view on standards. The speech said it would be published on the afternoon of October 12. We could not find it on gov.uk or the AISI site on October 13, 2026.
The National Cyber Action Plan. The minister said it is coming "soon", with no date.
What OpenAI and Anthropic will tell MPs. The Guardian reports both will give evidence to a Commons committee on Tuesday, October 13, alongside AISI head Henry de Zoete.

What people are saying

On r/ukpolitics, a thread on the Metro report of the speech drew dry replies. One user wrote: "So now he's said it who will take a bet with me it'll end up happening this week?" Another replied: "What if it already happened last week and they are getting ahead of the story?"

A day earlier, on the news that the US had restored UK access to unreleased models, the top comment was: "Until such time as they chose to turn the switch off again." That doubt is fair. Pre-release testing that depends on another government's goodwill is a weak base, which is one reason to rely on your own logs rather than on someone else's model evaluations.

Our take

Most of the speech is about government systems and frontier labs. The part that reaches small teams is the four questions. They are not a law and may never be one, but they are what a regulator, a customer or an insurer is likely to ask after an agent does something odd. In our view the hard two are what the agent accessed and why, because both depend on logs that many agent tools do not keep by default.

Near misses are the cheap win. A blocked tool call or an agent wandering outside its task costs nothing to log, and it gives you the evidence base before anything is required. If the bill does add near-miss reporting, teams with six months of logs will find it routine.

The weak spot is the gap between words and text. "Explore", "look at" and "worked through with parliamentarians" mean the detail could take a year. Do not wait for it; the NCSC agentic AI checklist and our AI agent governance policy already cover the controls the log will test.

Embedded media

gov.uk published a transcript only. A search on October 13, 2026 found no official video, webcast or Cabinet Office or DSIT post of the speech, so there is no embed in this article rather than one about a different story.

How we checked this

We read the gov.uk press release and the speech transcript (both via the gov.uk content API, which gives the publish and delivery times), Imperial College London's news story, two Guardian reports (the October 11 preview and the October 12 report), and three comments in two r/ukpolitics threads: 7 sources, checked on October 13, 2026. BBC and ITV reports could not be loaded from our network, so no fact relies on them. Every quotation and number in this article maps to a row with a verbatim quote in our source log. Last reviewed: October 13, 2026.