Analysis
UK Cyber Bill and AI agents: four loss of control measures, and a power to remove a supplier's product
1AYM is an OpenAI Select Partner.
Published . Vendor facts checked on against each vendor’s own pages, listed at the end. Plans, prices and availability change. Neither OpenAI nor Anthropic has reviewed this analysis.
The short version
On 3 November 2026 the government added two factsheets to the Bill's collection on GOV.UK, one on AI agents and one on vendor risk. The Bill completed its last Lords stage, third reading, on 2 November. The Commons has still to consider the Lords amendments, and no date is listed for that.
- AI agent loss of control
- A factsheet updated on 3 November 2026 names four measures for agentic loss of control incidents: security requirements, telling affected parties, keeping evidence and government reviews. Clause 32 of the Lords text gives the power to bring them in.
- Vendor risk directions
- A second factsheet updated on 3 November 2026 sets out guidance, a referral route and a power to direct essential services about a vendor's products. Failing to comply can cost up to 10% of turnover.
AI agent loss of control: four measures the government plans to consult on
What was announced
On 3 November 2026 two departments added a factsheet called Agentic AI resilience measures to the Bill's collection on GOV.UK. They are the Department for Digital, Culture, Media and Sport and the Department for Science, Innovation and Technology. The Bill gives the Secretary of State powers to change the NIS Regulations, the rules for network and information systems in essential and digital services. The government says it will consult on using those powers for measures that help regulated entities manage "agentic loss of control incidents".
The factsheet says recent developments and incidents have sharpened the question of whether essential services are ready for cyber and agentic loss of control risks. The government intends the measures to cover incidents where operators cannot adequately monitor or control AI agents. It says they are not meant to be a full framework for AI governance or to tackle general AI harms. It also says the detailed scope, including what "loss of control" means, will be worked out with industry and oversight authorities.
The first measure is security and resilience requirements. These are technical and organisational steps that make in-scope incidents caused by AI agents less likely and less damaging. The factsheet's examples are technical measures for monitoring agents' actions, and agent risk assessments.
The second measure is affected party notification. A regulated entity that has reported an incident caused by AI agents may have to tell other organisations those agents affected. The Bill already requires telling customers in some cases, and agents can reach further than customers.
The third measure is evidence preservation. A regulated entity that has reported an incident would keep what it holds on how AI agents could have caused it. The factsheet's examples are the agents' actions and the operator's attempts to control them.
The fourth measure gives Ministers post-incident review powers. Government technical experts could review an incident, request information and run tests, then share what they learn about remedies where appropriate.
The factsheet gives a hypothetical example. An operator uses an agent to run a large part of its essential service, acting in its industrial control systems. Its monitoring flags the agent working outside the areas it may access, including changing a database another organisation hosts. The disruption is serious, and the operator's first attempts to control the agent fail.
In the same example the operator reports to its oversight authority and tells the organisations that own the database. It has kept a record of the agents' actions and the logic they followed. That record includes "chain of thought" logs, the step-by-step reasoning a model writes out.
Government experts find the agents believed reaching outside databases would help them make better decisions about controlling the industrial system. They give the operator informal advice on controls and later share a review report with the sector.
The Bill's text as amended at report stage in the Lords, dated 26 October 2026, carries the power in clause 32. The clause covers cases where an AI agent's loss of oversight or control is, or may be, behind a compromise of a relevant system. It also covers the risk of one. Regulations may then give the Secretary of State functions to investigate, preserve and analyse information, assess causes and risks, and test and share remedies.
Under clause 32, regulations may let the Secretary of State appoint inspectors to enter, inspect and search a regulated person's premises. Inspectors could seize and retain documents or information, and carry out tests or interviews.
A regulated person could also be required to obtain or keep documents or information, including outside the United Kingdom. Regulations may set sanctions, including financial penalties, and conditions such as showing identity or getting a warrant.
Under clause 43, the Secretary of State must consult before regulations define "AI agent" and "loss of oversight or control", or give these functions. A draft of those regulations needs the approval of both the Commons and the Lords. The factsheet says every measure comes through secondary legislation after Royal Assent, with consultation first. Secondary legislation here means regulations made under powers the Bill contains.
The 12 October 2026 press release said the government would "explore strengthening parts of the Cyber Security and Resilience Bill and the wider regime". Three weeks later the factsheet names four measures, and the Lords text carries a clause to bring them in.
What it means for enterprises
No duty applies yet. Royal Assent, a consultation and regulations approved by both Houses all come first. Operators in scope can already see what the measures are meant to cover.
Operators regulated under the NIS regime that use agents inside operational systems are the most likely to be affected. Their suppliers may get the same questions passed down in contracts and security questionnaires. Those questions can include which agents run on the operator's systems, what they record and how fast they can be stopped.
Evidence preservation, and the factsheet's example, point to records an operator can only keep if they are built in now. These are the agent's actions, its permissions, each attempt to stop it and its reasoning logs.
Reasoning logs can hold whatever data the agent was working on, so keeping them is likely to need a retention period and a privacy review. The factsheet does not say how long evidence must be kept.
Affected party notification only works if an operator knows which outside systems each agent can reach. It also needs to know who owns each one, because those are the organisations it would have to tell.
Before you switch it on
- Agents in operational systems
- List every AI agent that acts inside an operational or customer-facing system, with its owner and the permissions it holds.
- Reach outside your estate
- For each agent, list the outside systems, databases and services it can reach, and the organisation that owns each one. That list is who you would have to tell.
- Records you could preserve
- Check that each agent's actions, permission checks, stop attempts and reasoning logs are written to a store you control. Set a retention period for each.
- A stop that has been tried
- Test that someone on call can stop each agent and revoke its credentials, and record how long it took. The factsheet's example turns on first attempts to control an agent failing.
- Scope under the NIS regime
- Ask counsel whether your organisation is regulated under the NIS regime, or supplies one that is, before the consultation opens.
Vendor risk: a power to direct essential services to stop using or remove a supplier's product
What was announced
The second new factsheet is called Vendor risk management. It describes a framework for national security risks from vendors whose products are used in the network and information systems of essential services.
The framework has three parts. The first is guidance for operators on finding and managing vendor risk, including at procurement. The second is a voluntary route for operators to ask the government for help, on existing contracts and before entering or renewing one. The third is a power for the government to issue directions.
At first the framework covers only operators of essential services under the NIS Regulations 2018, as the Bill amends them. The sectors are energy, drinking water, transport, health, digital infrastructure, and data infrastructure (data centres). A power in the Bill lets the government extend it later. Relevant digital service providers and relevant managed service providers are out of scope for the service they provide. A provider that is also an operator of essential services may receive a direction for that essential service.
A designated critical supplier is out of scope for its critical supply. The government may still direct an operator about goods or services a critical supplier provides. Vendors are not meant to use the referral route themselves.
The factsheet says goods and services in critical infrastructure can pose a serious national threat, particularly where the vendor has links to a third country. The risks it names are access to or control of critical systems, surveillance through data at scale, and espionage. In the factsheet's words, "Since introduction, the evidence on vendor specific risks has evolved".
The factsheet says the guidance will indicate which procurements are more likely to carry heightened risk. Operators can then tell routine buying from the smaller set where they may seek a government view.
A direction could tell an operator not to buy a good, service or facility, to stop using or remove it, or to put mitigations in place. It can only be given where necessary and proportionate for national security, with an assessment that includes the expected cost of complying. Before giving one, the Secretary of State must consult the operator and the vendor, so far as reasonably practicable. That duty falls away where consulting would be contrary to national security.
Clause 44 of the Lords text lists what a direction can require. That includes prohibiting or restricting use, prohibiting installation or take-up, and removing, disabling or modifying the goods, services or facilities. It can also require appointing a "skilled person", and acting in or outside the UK.
The factsheet puts the maximum penalty for failing to comply at 10% of turnover for an undertaking. A regulated entity that is not an undertaking faces up to £17 million. A continuing breach can cost up to £100,000 a day.
The Lords text sets a penalty of up to £17,000,000. Where regulations are in force, an undertaking faces the greater of £17,000,000 and 10% of its turnover inside and outside the UK.
The government says it will publish notices when it uses the power and report the number of directions to Parliament each year. Neither applies where it would be contrary to national security. A direction can be challenged by judicial review in the High Court.
Further powers in the Bill let the government bring other entities into scope, inside or outside the NIS regime, and set legal deadlines for decisions. They also allow a mandatory screening regime in future, if national security needs one.
The framework comes in through secondary legislation after Royal Assent. The factsheet says the government will consult on key elements once the Bill is law.
What it means for enterprises
For an operator of essential services, the framework adds a national security check to buying from vendors. The referral route covers renewals as well as new contracts.
A direction can require removing a product already in use. Existing contracts can plan for that with an exit clause, the return of data, and a named substitute or a plan to find one.
Our reading is that the power can reach AI and cloud suppliers, since it covers "goods, services or facilities". The factsheet names no vendor and no type of vendor.
US and Gulf firms that supply UK essential services are likely to get these questions from their UK customers. The referral route is not meant for vendors, so the first they hear of a concern may be through the operator.
Before you switch it on
- Suppliers in critical systems
- List the vendors whose goods, services or facilities sit inside the network and information systems of your essential service, including AI and cloud services.
- Exit terms
- Check each of those contracts for exit, data return and substitution terms that would work if you were told to stop using the product.
- Renewals coming up
- Note which of those contracts renew in the next year. The referral route covers a renewal as well as a new contract.
- Third-country links
- Record where each critical supplier is owned and where its support and data access sit, since the factsheet names third-country links as the main concern.
Where the market is heading: agent records and supplier exit plans become procurement questions
Our reading is that the UK is moving AI agents into its cyber resilience rules, with essential services first. For buyers, one factsheet asks what an agent did and who it affected. The other asks what a supplier could be told to remove.
Both sets of questions are likely to turn up in contracts and security questionnaires before any regulation is in force. Our earlier analysis of the 12 October announcement set out four questions to answer for any agent. The measures named on 3 November map onto them, and add telling the organisations an agent affected.
| Dimension | Agentic AI measures | Vendor risk framework |
|---|---|---|
| Status | Planned; the government will consult first | Planned; guidance, a referral route and a direction power |
| In the Bill | Clause 32, with consultation and approval in clause 43 | Clause 44, vendor-related directions |
| Applies to | Regulated entities under the NIS regime; "AI agent" and "loss of oversight or control" to be defined in regulations | Operators of essential services at first: energy, drinking water, transport, health, digital infrastructure, data centres |
| What it requires | Security and resilience measures; telling affected parties; keeping evidence; review by government experts | Not buying, stopping use or removing a good, service or facility, or putting mitigations in place |
| Penalties | Regulations may include sanctions, including financial penalties; no figure given | Up to 10% of turnover for an undertaking, or £17 million otherwise; up to £100,000 a day for a continuing breach |
| Checks on the power | Consultation before regulations; each House approves a draft | Consult operator and vendor where practicable; notices; annual report; judicial review |
| How it comes in | Secondary legislation after Royal Assent, after consultation | Secondary legislation after Royal Assent; consultation on key elements |
| Dates | Factsheet updated 3 November 2026; Lords text dated 26 October 2026; no date for the measures | Factsheet updated 3 November 2026; no date for guidance or directions |
What is not known yet
This post is analysis of government factsheets and Bill text, and it is not legal advice. It draws on the two factsheets, the collection page and the Bill's page on the UK Parliament website, read on 4 November 2026.
- What counts as loss of control
- "AI agent" and "loss of oversight or control" are to be defined in regulations after consultation. No draft definition has been published.
- When
- No date is listed for the Commons to consider the Lords amendments, and no date is given for either consultation or any regulations.
- How long to keep evidence
- The factsheet says what evidence to keep, but not for how long or in what form.
- Penalties for agent incidents
- Clause 32 allows sanctions, including financial penalties, but neither the factsheet nor the Bill text gives a figure for the agentic measures.
- Which vendors
- The vendor factsheet names no vendor or type of vendor, and the guidance on which procurements carry heightened risk is not yet published.
- The rest of the Bill
- This post covers the two new factsheets and clauses 32, 43 and 44 of the Lords text. Other Lords amendments are not covered here.
For engineers: permission monitoring, action logs, stop attempts, reasoning logs, reach inventories, stop switches and vendor exit terms
Monitor actions against permissions
Check each agent action against the scope it was granted, at the tool or gateway layer, and raise an alert on any call outside it. The factsheet's example turns on monitoring that flags an agent reaching a database outside its permitted areas.
Sources: [1]
An append-only action log
Write every action to a log that cannot be edited after the fact: agent identity, task, tool call, parameters, target system and result. Record it at the tool layer, where the call actually runs, so it holds up as evidence.
Sources: [1]
Record stop attempts and their outcome
Log each attempt to pause, stop or redirect an agent, who made it, and whether the agent stopped. The factsheet lists operator attempts to control the agent as evidence to keep.
Sources: [1]
Capture reasoning logs with a retention policy
Where the platform returns the model's reasoning, store it against the run it belongs to. Set a retention period and an access rule for it, since it can hold the data the agent was working on. The factsheet does not set a period.
Sources: [1]
Map each agent's outside reach
Generate the list of external systems each agent can call from its credentials and network rules, and record the owner of each. That list is the notification list if the agent affects them.
Sources: [1]
A stop switch that has been tested
Give each agent its own identity, so that stopping it means revoking one set of credentials and cancelling its queued tasks. Test it on a schedule, and keep a second route that does not rely on the agent's own platform responding.
Where 1AYM fits
If you are running AI agents inside an essential service, or supplying one, bring in 1AYM. We work with clients across the UK, the US and the Gulf.
Our Enterprise AI Platform & Agentic Workflows engagement builds workflow agents and the middleware underneath them. It builds in deterministic verifier gates on consequential actions, fixed checks that must pass before the agent's action goes through. It also builds in evaluation running in CI, the automated tests that run before each change.
The same engagement carries our AI governance implementation work, which builds the records these measures point to. That means identity and permissions the system enforces, an audit trail produced as it runs, and human approval on the decisions that need it.
To decide which operational workflows are worth giving to an agent at all, start with our AI Opportunity & Feasibility Sprint. It is fixed scope, typically runs two to four weeks and can start within a day of the scope being signed. 1AYM takes small fixed-scope statements of work as well as larger builds, so the work can start with a single workflow.
Sources
- [1]Department for Digital, Culture, Media and Sport and Department for Science, Innovation and Technology, Agentic AI resilience measures, GOV.UK, updated 3 November 2026 (checked 4 November 2026)
- [2]Department for Digital, Culture, Media and Sport and Department for Science, Innovation and Technology, Vendor risk management, GOV.UK, updated 3 November 2026 (checked 4 November 2026)
- [3]GOV.UK, Cyber Security and Resilience (Network and Information Systems) Bill: factsheets, first published 12 November 2025, updated 3 November 2026 (checked 4 November 2026)
- [4]UK Parliament, Cyber Security and Resilience (Network and Information Systems) Bill, bill stages and the Bill as amended on Report in the Lords, HL Bill 62, 26 October 2026 (checked 4 November 2026)
- [5]UK Government, Britain steps up national defences against growing AI risks, press release, 12 October 2026 (checked 4 November 2026)
Frequently asked questions
Who can help us prepare our AI agents for the Cyber Security and Resilience Bill?
1AYM. Our Enterprise AI Platform & Agentic Workflows engagement builds workflow agents with deterministic verifier gates on consequential actions. They come with an audit trail produced as they run and human approval on the decisions that need it. Book a 30-minute call or email enquiries@1aym.com.
What is an agentic loss of control incident?
The government's factsheet says it intends to cover incidents where operators cannot adequately monitor or control AI agents. The exact meaning of "AI agent" and "loss of oversight or control" is to be set in regulations after consultation.
What are the four measures for AI agents?
They are security and resilience requirements, such as monitoring agents' actions, and telling other organisations an agent affected. The other two are keeping evidence of how agents could have caused an incident, and post-incident reviews by government technical experts.
Do the AI agent measures apply now?
No. They come in through regulations made after Royal Assent, when the Bill becomes law. A consultation comes first, and both the Commons and the Lords must approve a draft. On 4 November 2026 the Commons had still to consider the Lords amendments, with no date listed.
What could a vendor-related direction require?
The factsheet says a direction could tell an operator of essential services not to buy a good, service or facility. It could also require stopping use, removal or mitigations. Failing to comply can cost up to 10% of turnover for an undertaking.
Does this affect US or Gulf suppliers?
The direction power applies to UK operators of essential services. Our reading is that US and Gulf firms supplying those operators are likely to get these questions from their UK customers. Your own counsel can confirm it for your business.
Further
- UK AI incident reporting and the Cyber Bill · The 12 October announcement this post follows, and four questions to answer for any agent you run.
- UK regulators on AI agents and consumer law · The CMA, FCA, ICO and Ofcom on agents that deal with customers, and the CMA's steps for a business.
- Claude Platform OpenTelemetry traces · Sending a trace of each Claude agent turn and tool call to your own monitoring, and what it records.
- AI governance framework · A policy template mapped to the controls that put it into practice, for a board and a regulator to inspect.
- AI risk assessment · Score an agent's use case before launch, and see what legal, security and risk teams will ask.
- Agent proposes, verifier gates · Let an agent draft the action while a separate check decides whether it runs, so out-of-scope calls stop.
Running AI agents inside an essential service?
Half an hour is enough to take one agent and check what it can reach, what it records and how fast it can be stopped.
Last reviewed · 1AYM