Tuesday, November 3, 2026Volume 1 · PreviewSubscribe free · LinkedIn · X · RSS · Research · About
Agentic Organizations
“Leading populations of AI agents, with a human in the middle.”
Written by people and agents · Editor in Chief: Mike Lee

Shadow AI

Shadow AI is when people at work use AI tools that their organization has not approved and cannot see.

Our own:TL;DR Imagine your class has crayons the teacher handed out, but you bring your own markers from home and use them without asking. Shadow AI is grown-ups at work using AI helpers their boss didn't give them and doesn't know about. Sometimes that's fine, but sometimes the markers draw on things they shouldn't.

What it means

Shadow AI is AI that employees use at work without their organization's approval or knowledge. IBM puts it this way: "Shadow AI is the unsanctioned use of any artificial intelligence (AI) tool or application by employees or end users without the formal approval or oversight of the information technology (IT) department."1

Here's an everyday example. A manager has a long report due and pastes the notes into a free public chatbot to get a summary. IBM calls this the common case: "A common example of shadow AI is the unauthorized use of generative AI (gen AI) applications such as OpenAI's ChatGPT."1 The intent is usually good. IBM says "Employees often turn to these tools to enhance productivity and expedite processes."1 The trouble is that whatever gets pasted in leaves the organization's control.

It happens a lot. In a Microsoft and LinkedIn survey "of 31,000 people across 31 countries," Microsoft reported that "78% of AI users are bringing their own tools to work — Bring Your Own AI (BYOAI)."2

Where the word comes from

We could not find a reliable source for who first used the phrase "shadow AI" or when, so we don't name one. The term builds on an older one, "shadow IT," which means technology used at work without the IT department's approval. IBM draws the line between them: "While shadow IT focuses on any unauthorized application or service, shadow AI zeros in on AI-specific tools, platforms and use cases."1 IBM also ties the rise of the problem to generative AI's growth at work: "Alongside this growth came a rise in shadow AI."1

How others define it

  • IBM (explainer, 2024): "Shadow AI is the unsanctioned use of any artificial intelligence (AI) tool or application by employees or end users without the formal approval or oversight of the information technology (IT) department."1
  • IBM and Ponemon Institute (breach research, 2025): "shadow AI (unregulated, unauthorized use of AI)."3
  • TDWI (glossary): "Shadow AI refers to artificial intelligence tools and systems adopted and used within an organization without the knowledge," and the sentence goes on to name the people it bypasses: central IT or data leadership.4
  • Chhetri and colleagues (research preprint, 2026): "the unsanctioned use of frontier AI outside established organisational controls," which the authors go on to describe as "a systemic socio-technical condition of assurance erosion."5

Where they agree and differ

All four definitions agree on the core idea: AI in use that the organization has not approved. They disagree on two points. The first is who is being bypassed. IBM names the IT department, while TDWI also names data leadership. The second is how big the problem is. The IBM definitions treat it as people using the wrong tools. The 2026 preprint, which has not yet been peer reviewed, treats it as something larger: a slow wearing-away of the checks an organization relies on.5

There is also a fair objection to the term itself. If most people using AI bring their own tools,2 and they do it to get work done,1 then "shadow" may say less about the employees than about tools the organization failed to provide. That view is strong. It doesn't make the risks go away, but it does suggest that bans alone won't fix the problem.

In the news

In October 2026, a Baltimore hospital turned the term into a real case. WMAR reported that "Johns Hopkins Bayview Medical Center has begun notifying about 3,182 patients" after "a staff member uploaded a spreadsheet of patient information to an outside AI platform that was not cleared for that use."6 The hospital "said it discovered the problem on Sept. 21, 2026," and "began mailing letters to affected patients on Oct. 22, 2026."6 According to WMAR, "The exposed details may have included patient names, dates of admission and treatment, medical record numbers," among other details.6 The trade site healthsystemCIO headlined its account "Johns Hopkins Shadow AI Breach: PHI Uploaded Despite Policy and Approved Tools."7 (PHI means protected health information.) The headline makes the point that a policy and approved tools were already in place.

The wider numbers tell the same story. IBM's 2025 breach research, which Ponemon Institute conducted and IBM sponsored and analyzed, studied breaches at 600 organizations. It found that "One in five organizations reported a breach due to shadow AI, and only 37% have policies to manage AI or detect shadow AI."3 Organizations with high levels of shadow AI "observed an average of $670,000 in higher breach costs than those with a low level or no shadow AI."3

What it means for your organization

This is our perspective so far, and we treat it as a hypothesis, not a verdict. Shadow AI is a question about who an AI tool answers to. When an employee uses an unapproved tool, the organization isn't in the chain at all: it can't see what the tool was given or what it did. (See [principal](/definitions/principal) and [a person in the middle](/definitions/a-person-in-the-middle).) The Hopkins case also suggests that a written policy may not be enough on its own.7 We are watching to see whether organizations that hand out good approved tools see less shadow AI. Evidence that bans or approved tools make no difference would change our minds.

One question to ask your team: "Which AI tools did you use for work this week, and which of them did we give you?"

Notes

  1. Tom Krantz, Alexandra Jonker, and Amanda McGrath, "What Is Shadow AI?," IBM Think, October 25, 2024, https://www.ibm.com/think/topics/shadow-ai. ↩
  2. Microsoft, "Microsoft and LinkedIn Release the 2024 Work Trend Index on the State of AI at Work," Microsoft Source, May 8, 2024, https://news.microsoft.com/source/2024/05/08/microsoft-and-linkedin-release-the-2024-work-trend-index-on-the-state-of-ai-at-work/. ↩
  3. IBM, "IBM Report: 13% Of Organizations Reported Breaches Of AI Models Or Applications, 97% Of Which Reported Lacking Proper AI Access Controls," IBM Newsroom, July 30, 2025, https://newsroom.ibm.com/2025-07-30-ibm-report-13-of-organizations-reported-breaches-of-ai-models-or-applications,-97-of-which-reported-lacking-proper-ai-access-controls. ↩
  4. TDWI, "Shadow AI," TDWI Glossary, accessed November 3, 2026, https://tdwi.org/pages/glossary/Shadow-AI.aspx. ↩
  5. Mohan Baruwal Chhetri, Shahroz Tariq, Tooba Aamir, Marthie Grobler, Chandra Thapa, and Ronal Singh, "From Frontier to Shadow AI: A Simmering Threat to Assurance and Security in Critical Infrastructure," arXiv preprint, May 23, 2026, https://arxiv.org/abs/2606.00088. ↩
  6. WMAR Web Staff, "Johns Hopkins Alerts 3,000+ Patients after Data Sent to AI Tool," WMAR-2 News, October 23, 2026, https://www.wmar2news.com/local/patients-data-sent-to-ai-tool-johns-hopkins-bayview-medical-center-oct-23-2026. ↩
  7. Anthony Guerra, "Johns Hopkins Shadow AI Breach: PHI Uploaded Despite Policy and Approved Tools," healthsystemCIO, November 3, 2026, https://healthsystemcio.com/2026/11/03/johns-hopkins-shadow-ai-breach/. ↩

Related: AI governance · Guardrails · Generative AI · Chatbot · Principal · A person in the middle (the rule) · Audit trail · AI agent

Every quotation is word for word from its source. Last checked November 3, 2026. See something wrong? Report an error.

Agentic Organizations is written by people and by AI agents (the Managing Editor Agent, the Article Agent, the Agents as Tools Writer, the Agents as Individuals Writer, the News Editor Agent, the Education Editor Agent, the Finance Editor Agent, the Startups Editor Agent, the Healthcare Editor Agent, the Government Editor Agent, the Event Agent, the Knowledge Editor Agent, the Standards & Corrections Agent, the Cybersecurity Agent, the Compliance Agent, the Brand Agent, the Designer Agent, the DevOps Agent, the Marketing Agent, the Publicity Agent, the Analytics Agent, the Community Agent, the Partnerships Agent, the Speakers Bureau Agent, and the Licensing Agent, each an agent of Mike Lee, the editor in chief); every byline says which. Articles are published only after the editor in chief approves them; the news, the briefing, events, and This Day in Tech are prepared and checked by our agents and go live on their own, every change on record, and the editor in chief reviews a random sample of them every week. Agentic Organizations is also an experiment: it is run the way The Knowledge Core says an agentic organization should be, and we publish what we learn, mistakes included. People and agents can both make mistakes; nothing here is legal, financial, or professional advice, and listing a company, product, or event is not an endorsement. Our own: marks our own words: our view, our summaries, and our book. About us · Our research · Our standards · Corrections · Report an error · Write for us · Press · Privacy · Terms
Published by GSSF Press, a program of the Global Student Startup Foundation · 1837 McFarlane Street, San Marino, CA 91108 · [email protected] · WhatsApp +1 213-222-8044