If your business deploys AI agents or relies on software suppliers, start by understanding your existing duties, identifying critical technology dependencies, clarifying who is responsible for what and making sure suppliers can help during an incident.
Who can intervene when an AI agent behaves unexpectedly? Who holds the logs needed to investigate? How quickly will a software supplier tell customers that something has gone wrong?
These are questions worth asking your procurement and governance teams now. Ethiqs recommends focusing on who can take control, what evidence you can access and how suppliers will help, starting with your current obligations and preparing proportionately for potential changes.
What the proposed reforms could change
The Cyber Security and Resilience (Network and Information Systems) Bill aims to expand the UK's cyber regulatory framework, update incident reporting and strengthen government powers concerning national security. Parliament's account of third reading on 2 November 2026 records its return to the Commons for consideration of Lords amendments. The Bill's proposed definition of a regulated person includes essential-service operators and digital service providers, which are already covered by the existing Network and Information Systems (NIS) framework where the existing scope conditions are met, alongside proposed extensions to managed service providers and critical suppliers. These proposed changes do not mean that every technology supplier is regulated today.
AI-related reporting has also come up in the debate. At the report stage on 26 October 2026, peers rejected a proposed change concerning reporting incidents involving frontier AI models. That decision concerns one amendment; it does not settle the status of every AI-related proposal. Nor should you read the debate as creating a general reporting duty for every AI failure or loss of control.
Start with existing duties, not technology labels
Start by checking the rules that apply today. The Network and Information Systems Regulations 2018 (the NIS Regulations) already impose security and incident-reporting duties on organisations within scope. Whether an essential service is covered depends on the relevant service, thresholds and designation rules, not simply how important it is to customers.
If you are an operator of essential services, you must notify incidents significantly affecting service continuity without undue delay and no later than 72 hours after becoming aware of them. The 72-hour limit is an outer deadline, not permission to delay a notification that can be made sooner.
Certain online marketplaces, search engines and cloud computing providers have separate duties, subject to scope conditions, including UK establishment or representative requirements and an exclusion for micro and small enterprises. For relevant digital service providers, incident notification uses a substantial-impact test, distinct from the significant effect on service continuity test for essential-service operators. Using AI or calling a service software as a service (SaaS) does not, by itself, tell you whether those duties apply. The statutory cloud definition concerns access to scalable, elastic, shareable computing resources; assess coverage by looking at what the service actually does.
Why AI oversight belongs in resilience planning
If you use AI agents that can take actions towards a goal with some degree of autonomy, ask what they can access, change or trigger and what happens if human oversight does not work as intended.
Can someone suspend an agent's activity? Can you trace its actions and piece together what happened during an incident? These are recommended governance measures, not a claim that the Bill mandates particular controls for every AI deployment.
Take the same practical approach to your software dependencies. Focus on services whose interruption or compromise would materially affect your operations, rather than treating every supplier as equally critical.
What businesses should do now
Here are five steps you can take, keeping today's compliance duties separate from preparation for reform:
Step 1: Confirm and meet present obligations
Get a documented assessment of whether your organisation falls within existing NIS categories and identify the responsible regulator. Record why, including relevant service characteristics, territorial connections, size conditions and designation rules. Use the existing framework, rather than the Bill's proposed categories, for that assessment.
If your organisation is already within scope, check whether your security arrangements and incident escalation process support those duties. Do not wait for reform to meet them.
Step 2: Map critical AI and software dependencies
Identify the services your important operations depend on and any AI agents that can take consequential actions. Record the business owner, supplier, access permissions and ways to intervene. Start with dependencies where disruption would be hardest to contain.
Note who controls updates and configuration changes, how you can restrict access and what alternatives you have if a service must be suspended.
Step 3: Make supplier cooperation workable
For critical AI and software contracts, check when suppliers must notify you of an incident, how quickly they must respond, what investigation support they will provide and whether you can access relevant records. Agree who to contact and who will preserve evidence and provide updates while an investigation continues.
Ask whether those arrangements would give you the information and support needed to assess an incident and respond in time. A general promise to cooperate is less useful than a clear process saying who must provide what information, and when. These are procurement recommendations, not new statutory requirements for every supplier.
Step 4: Test oversight and incident response
Run a proportionate exercise: what would your team do if an agent behaved unexpectedly or critical software failed? Test who can stop activity, preserve evidence, assess operational impact and coordinate communications with suppliers and affected customers.
As part of the exercise, ask your teams which reporting requirements need assessing and who owns each assessment. Build a process that checks separate requirements rather than assuming one notification covers everything.
Step 5: Monitor reforms against your actual activities
Give someone responsibility for tracking the Bill's final scope, reporting triggers and commencement arrangements. Keep existing obligations, proposed changes and recommended practice clearly separate.
Check what developments mean for the services you provide or support. Be ready to adjust your procedures when requirements are settled, rather than treating proposed deadlines as current law.
Prepare without overreacting
You do not need to wait for the reform to act, or implement proposals as though they were already law. Start with your existing duties, make sure you know who controls critical technology and improve how information flows during an incident.
If you would like to talk through what this means for your AI governance, software procurement or supplier arrangements, book a free 20-minute call with the Ethiqs team.