ModelRefs / Shadow AI — AI Glossary
Shadow AI — AI Glossary
Unauthorized use of AI tools by employees outside of official IT governance, procurement, and security review processes.
Overview
Shadow AI mirrors shadow IT: employees using ChatGPT, Claude, or Copilot on personal accounts for work tasks, bypassing corporate data governance. Risks: sensitive data sent to third-party LLM APIs, no visibility into data retention, no corporate SSO or audit trail. Addressed by deploying sanctioned AI tools with monitoring and acceptable-use policies.
Reference details
| Topic | safety |
|---|---|
| Last reviewed | 2026-06-24 |
Related terms
How it works
- The pattern begins with a capability gap: employees have work a model would help with and no sanctioned tool that does it, so they use a personal account.
- Because the account is personal, the organisation has no visibility into what was sent, no record of what came back, and no contractual position on retention or training use.
- Data governance is bypassed rather than violated. The controls exist and the traffic simply does not pass through them, which is why audit logs show nothing rather than showing a problem.
- Identity and access controls are absent too: no single sign-on, no offboarding, so access persists after someone leaves and is attributable to no one.
- Detection is possible from the network and endpoint side — traffic to known endpoints, browser extensions, clipboard volume — and detection alone does not address the underlying gap.
- The durable remedy is substitution rather than prohibition: a sanctioned tool that is at least as useful, with logging and a contractual data position, removes the reason the personal account was used.
Example: Why the exposure count grows faster than the policy violation count
Assume an organisation of 2,000 employees and that 40% use an unsanctioned tool for work — a figure to measure rather than accept, but useful for the shape. That is 2,000 x 0.4 = 800 people. If each pastes one work document a week, the annual exposure is 800 x 52 = 41,600 documents sent to third-party services with no record of what they contained. The number of policy violations is 800; the number of exposures is 41,600, and only the second is the risk. That ratio is why enforcement framed around violations understates the problem by a factor of 52 — and why a single incident investigation cannot establish scope, since there is no log to query. The substitution arithmetic is the more useful comparison: a sanctioned deployment costing, say, 20 units per user per month is 2,000 x 20 x 12 = 480,000 units a year for full coverage with logging and a contractual data position. Whether that is worth paying is a question about the value of 41,600 documents' worth of exposure, which is at least now a comparison between two numbers rather than between a number and an anxiety.
Commonly confused with
Shadow AI is a governance gap, not a security breach, and treating it as the latter produces the wrong response. Nothing was compromised and no control was defeated: employees used a legitimate service outside a process, usually to do their jobs. So the effective interventions are provisioning and policy rather than incident response, and a blocking-only approach reliably moves the activity to personal devices where even network-side detection stops working. The related distinction is from sanctioned use with weak governance, which is a configuration problem with a known owner rather than an invisible one.
When to use it
Reach for it when:
- As the framing when planning AI provisioning, where the question is what employees are already doing rather than what they should do.
- In risk assessment, where unlogged exposure to third-party services is the actual quantity at issue.
- Alongside a measurement of actual usage, since the prevalence figure is what makes the exposure arithmetic real.
- As the argument for sanctioned tooling, where substitution rather than prohibition is what changes behaviour.
Reach for something else when:
- Addressed by blocking alone, which moves the activity to personal devices and removes the remaining visibility.
- Treated as a security incident, where the response machinery does not fit a provisioning problem.
- Quantified from assumed prevalence rather than measured, since the exposure arithmetic is only as good as that input.
- As a reason to delay AI provisioning, which is the condition that produced it.
Continue your research
Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to Shadow AI — AI Glossary.
Frequently asked questions
What is Shadow AI?
Unauthorized use of AI tools by employees outside of official IT governance, procurement, and security review processes.
What concepts are related to Shadow AI?
Closely related concepts include ai audit, data privacy, responsible ai.