How to manage shadow AI without blocking it.
Blocking AI tools moves shadow AI out of sight. Approve fast, follow the spend, keep the inventory current. A practical guide for security and IT.
- Topic
- Shadow AI
- Product
- Novie Control
- Format
- Answer
- Reading time
- 3 min
- Published
- 2 October 2026
- Updated
- 21 October 2026
To manage shadow AI without blocking it, make the approved path faster than the unapproved one. Publish a list of approved AI tools, answer requests for new ones in days, watch spend and identity for AI you did not approve, and keep an inventory of every AI system and agent with an owner. Blocking moves shadow AI to personal devices and accounts, where it is harder to see and impossible to govern.
What shadow AI is.
Shadow AI is the use of AI tools without approval or oversight. It includes a personal chatbot account used for work, a browser extension, an AI feature switched on inside a licensed product, and an agent a team built and runs on its own credentials. It is shadow IT with a difference. A shadow tool stores data outside control. A shadow agent acts outside control.
TakeawayShadow AI is any AI used without approval or oversight, and a shadow agent acts outside control rather than only storing data outside it.
Why it matters.
IBM's Cost of a Data Breach Report 2026, drawn from breaches at 602 organisations, found that security incidents involving shadow AI 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.
Closer to home, use has outrun the rules. The EMA's survey of more than 300 of its member businesses, published in July 2026, found 83 percent use AI and 13 percent have an AI policy. In 18 percent, AI is used without a clear owner.
TakeawayShadow AI incidents reached 43 percent of breached organisations in 2026, and among EMA members 83 percent use AI while 13 percent have a policy.
Why blocking backfires.
People use unapproved AI because it helps them do their work. Block it on the corporate network and the work moves to a phone, a personal laptop or a home account. The organisation loses the one signal it had, the traffic, and keeps the risk. A blocked tool that someone needs becomes a tool used out of sight.
Blocking has a place: a tool with known data handling problems, or a class of data that must never leave a system. As a general policy it treats a demand signal as a threat.
TakeawayBlocking moves the work out of sight and keeps the risk, so it belongs only where a tool or a class of data clearly warrants it.
Six steps that work.
- Publish the approved list. The AI tools the business supports, the data each may handle, and who to ask about anything else.
- Answer requests fast. A request for a new tool answered in days removes most of the reason to go around the list.
- Follow the money. Card statements, expense claims and software renewals show AI tools and features nobody listed. Spend is often the first place shadow AI is visible.
- Follow identity. Service accounts and API keys with no human owner, and OAuth grants to AI tools, show what is running on the organisation's behalf.
- Keep the inventory. Every AI system and agent, with an owner, its data and its approval. Shadow AI is an inventory problem before it is a policy problem.
- Bring it in. When you find an unapproved tool that people rely on, approve it with a scope or replace it with one that is approved. Treat each find as a request that arrived late.
TakeawayMake the approved path faster than the unapproved one, then follow spend and identity to find what is already running.
Agents need more than a policy.
A policy tells people what not to do. An agent built last month by a team on its own credentials is already doing something, and keeps doing it whether or not anyone reads the policy. For agents, the controls are an owner, an approved scope with a review date, a budget cap and a record of what the agent did. Those sit in the path the agent's calls take, rather than in a document.
TakeawayAn agent keeps acting whether or not anyone reads the policy, so its controls have to sit in the path its calls take.
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)
- EMA, AI adoption surges among SMEs, but businesses risk falling behind on workforce readiness (9 July 2026)