Shadow AI: The Risks, and How to Govern It Without Blocking AI
Data you can't see is data you can't protect. When staff feed company information into unsanctioned AI tools, it can be stored, logged, or trained on far beyond your control.
Shadow AI is the use of AI tools at work that the security team hasn’t approved or doesn’t even know about. An employee pastes a customer list into a free chatbot. A team wires an unsanctioned copilot into company data. A browser extension quietly ships documents to an outside AI service. It’s the AI version of shadow IT, and it spreads fast because AI tools are free, genuinely useful, and one click away.
The core problem is simple: data you can’t see is data you can’t protect. When staff feed company information into outside AI tools, that data can be stored, logged, or used to train models far beyond your control. On episode 98, Or Eshed, co-founder and CEO of LayerX Security, captured the human side with a blunt line: a lot of AI risk is “natural stupidity to artificial intelligence” — ordinary people making ordinary mistakes with very powerful tools.
Shadow AI examples you’re probably missing
Shadow AI is rarely one obvious app. It hides inside daily work:
- Pasting sensitive data — customer records, source code, contracts — into public chatbots to summarize or rewrite.
- Unsanctioned copilots and plugins connected to email, code repos, or cloud drives, often on personal accounts.
- AI browser extensions that read the contents of a page and send it to a third party.
- Bring-your-own-AI on personal devices, where nothing touches a company log.
- Meeting bots that silently join calls and send transcripts to an outside service.
The copilot and plugin cases are the riskiest, because they act with a user’s access — the same least-privilege problem behind agentic AI security. An AI tool inherits whatever the employee can reach.
Why it’s a real security risk
The numbers are no longer theoretical. IBM’s 2025 Cost of a Data Breach Report found 20% of breached organizations were compromised through shadow AI, and those breaches cost about $670,000 more than average. Only 17% of organizations have technical controls that can stop employees from uploading confidential data to public AI tools. The other 83% rely on training, warning emails, or nothing.
Four risks stack up fast: data leakage the moment information enters an outside model; compliance exposure when regulated data lands in an ungoverned tool; identity and credential risk as connected tools widen the blast radius of a phished account, the same pattern behind why passwords still get stolen; and no audit trail, because an invisible tool leaves nothing to prove what went where. You also can’t protect data if you don’t know what’s going into the model — the case for tracking an AI data bill of materials.
Shadow AI vs. shadow IT
| Shadow IT | Shadow AI | |
|---|---|---|
| What it is | Unapproved apps and services | Unapproved AI tools and AI features |
| Main risk | Ungoverned access and data sprawl | Company data fed into models you don’t control |
| Why it’s harder | Usually a separate app to discover | Often hidden inside approved apps and the browser |
The key difference: with shadow IT, your data usually stays in a database you could in theory reach. With shadow AI, data pasted into a model may be gone for good.
How to detect and govern it
You can’t govern what you can’t see, and most shadow AI happens in the browser, not in network logs. A workable order of operations:
- Get visibility where AI is actually used — the browser session, where employees type into prompts.
- Inventory the tools in play and the data flowing to them.
- Apply controls at the point of use: warn or block when someone pastes regulated data into an AI prompt.
- Tie AI use to identity, so every action maps to a person and a role.
Network tools sit too far from the action to see a paste into a chatbot. The browser sits right on top of it.
A policy that doesn’t block productivity
A flat ban backfires. Tell people they can’t use AI and they’ll use it on their phones, off your network, with zero oversight — more shadow AI, not less. The better path is safe enablement, the same posture behind why security leaders should enable AI instead of blocking it. A policy that holds up usually does four things: it offers sanctioned tools good enough that staff don’t need to sneak; it states clearly what data can go into which tools, in plain language; it enforces the rules with guardrails at the point of use, not just a document nobody reads; and it gets reviewed often, because new AI tools appear every week.
The goal is not zero AI. It’s AI you can see. Govern the doorway, and you can say yes to the tools your teams want without losing track of your data.