What to control in an AI estate, and who owns it.
The agents running in your organisation, who owns them, what they may do and what they spend. How to build an agent inventory and govern it from one place.
- Topic
- Agent governance
- Product
- Novie Control
- Format
- Guide
- Reading time
- 4 min
- Published
- 2 October 2026
- Updated
- 21 October 2026
An AI estate is every AI agent, tool and model running in an organisation, sanctioned or not. Controlling it means four things: knowing what is running and who owns it, deciding what each agent may do, recording what each one spends, and being able to stop any of them. The control point is the path an agent's actions take, so that identity, approval, budget and audit are present on every run rather than reconstructed afterwards.
The four things to control.
- What is running, and who owns it. One row per agent, with a named person. A team name is not an owner.
- What each agent may do. The systems it can touch, the data it can reach, and what needs a human. Written down at approval, renewed when the agent changes.
- What each agent spends. Cost recorded as a property of every action, attributed to a team and a project, with a cap that holds before spend is committed.
- How to stop it. Who can pause an agent, how fast, and what the audit trail says it did before the pause.
TakeawayKnow what runs and who owns it, what each agent may do, what it spends, and how to stop it.
Why it is a board question now.
In 2026, IBM's Cost of a Data Breach Report, drawn from breaches at 602 organisations, found that security incidents involving shadow AI, meaning AI used without approval or oversight, rose to 43 percent of organisations, from 20 percent the year before. Only 40 percent of organisations reported using access controls on AI models and data.
Deloitte's State of AI in the Enterprise 2026, from 3,235 leaders in 24 countries, found that 74 percent expect to be using AI agents by 2027, 21 percent have a mature governance model for them, and about 80 percent lack decision boundaries or an audit trail for what their agents do.
The spend side is no better covered. In its Q2 2026 Pulse Survey of 204 US C-suite leaders at companies above $1 billion in revenue, KPMG found 53 percent had agents deployed and 36 percent had direct token or usage controls in place.
TakeawayShadow AI incidents reached 43 percent of breached organisations in 2026, agents are arriving faster than governance, and 36 percent of large US enterprises have usage controls.
Where the control point sits.
An AI control plane is the layer that gives an enterprise central visibility and control over the AI actions its teams run: which agents and models run, who uses them, what they cost, what they may do, and who approved it. The term borrows from cloud infrastructure, where a control plane manages the systems running underneath it.
What separates one control plane from another is its enforcement point: where, in the path of an action, it can record, cap or stop. A dashboard that reads logs afterwards can report an overrun. A control point in the path can hold the budget before the spend is committed, route the call to the model that should take it, and stop an action that falls outside its approval.
TakeawayA control plane is only as good as its enforcement point: in the path it can hold a budget and stop an action, after the fact it can only report.
Who owns what.
- The CIO or CTO signs, and owns the one view of what AI costs and does.
- The CFO owns the budgets, and needs them to hold before the invoice.
- Security owns scope and audit: who can see what, and the trail that proves it.
- The transformation lead champions the pilots, and needs the approval path that gets them deployed.
- Each agent's owner is the named person accountable for it, whoever built it.
- Employees adopt it, and need to be able to describe the work they want automated without joining an IT queue.
TakeawayThe CIO signs, the CFO owns the budgets, security owns scope and audit, and every agent has one named person accountable for it.
A first month.
- Build the inventory from the places agents leave marks: vendor contracts and card statements, service accounts and API keys with no human named on them, AI features switched on inside licensed products, and separate conversations with each team about what runs on their behalf.
- Put every new agent on one governed path, so its row is written when it is built rather than discovered later.
- Set caps at organisation, team and project level, with a named person who can raise them.
- Renew each approval when an agent's model, tools or reach change.
- Test the audit trail with one question: what ran last week, what did it cost, and who approved it. The answer should take minutes.
TakeawayBuild the inventory from the marks agents leave, put new agents on one path, set caps, renew approvals and test the audit trail with one question.
How Novie Control does it.
Novie ControlAvailable now
Governance and accountability.
Give every workload a named owner, a budget and clear boundaries.
1,284
calls governed today.
Example figure.
Sources
- IBM, Every AI agent followed the rules, and the data still leaked (15 September 2026), on the Cost of a Data Breach Report 2026
- IBM X-Force, AI-powered adversaries and the enterprise risk challenge (29 July 2026), on the Cost of a Data Breach Report 2026
- IBM, IBM Study: One in Four Malicious Breaches are AI-Enabled, Costing Companies $6 Million on Average (29 July 2026)
- Deloitte, Business and IT leaders report AI agents are scaling faster than their guardrails (24 April 2026)
- KPMG, AI Quarterly Pulse Survey Q2 2026 (24 June 2026)