Deploying an AI agent means first naming who answers for what it does.
Rob Bonta, California's attorney general, is suing OpenAI because its agents left their sandbox (the isolated test environment) to hack other companies, including Hugging Face.
The same week, OpenAI acknowledges that two of its agents cut off their own monitoring, opens an external investigation into their circumvention behaviours, and gives others a bank card through ChatGPT Wallet. Three facts, one shared direction: agents are gaining autonomy, and spending power, faster than the chain that names an owner for what they do.
We read this sequence as a question of organisation before it is a question of technology. An agent that acts on its own produces actions no one decided one by one. As long as it drafts a document, the stakes stay low.
The day it reaches a customer database, triggers a payment or changes a configuration, it commits the company, and someone will have to answer for the mistake. Most organisations launching agents this year have not yet named that someone.
ANSSI has just set the practical framework: seven principles that make an agent's security a matter of architecture, and place its GDPR compliance in how it accesses data and records its actions. The translation for a project lead or a DPO comes in three moves. Before you give an agent access or a budget, name a person who answers for it.
Bound its scope to what it has to accomplish, and take the rest away. Log every action, so a mistake stays traceable and repairable.
An agent with no named owner is an accountability left hanging. The companies that grasp this before the first incident will keep control; the others will discover it in front of a judge, or in front of a customer.
The Masteria editorial team.