AI Governance4 min read

What Is Shadow AI, and How Do You Find It Before Your Auditor Does?

The Core Reality: Shadow AI is any AI tool, model, or AI feature that employees or teams use for work without the security, legal, or risk team knowing about it. It is hard to see because AI arrives as a browser tab, a plug-in, or a feature switched on inside software you already own. You find it by combining three sources: what employees report, what your identity provider shows, and what your spreadsheets and procurement records list. Then every finding goes into one AI register.
Finding shadow AIThree sources, one register
Employee reports

No-blame form: tool, data, purpose

Identity provider

Apps people sign in to with work accounts

Spreadsheets and records

Procurement, renewals, expense lists

AI register

Triage, owner, then governance

Where Teams Get Stuck

Most organizations have no single list of their AI systems. Each team knows its own tools, nobody owns the whole picture, and a ban on unapproved tools simply pushes use out of sight. Auditors and customers increasingly ask for an inventory, and an incomplete one is worse than a known gap because it looks like you did not look.

How RAMP Handles It

RAMP builds the AI register from three intake paths: employee self-reports, imports from your identity provider, and spreadsheet uploads. Each item is triaged into the register as an AI system, a non-AI tool, or a duplicate, and every approved system moves on to a requirements document and two-stage approval. The register becomes the starting list for your risk assessment and your audit package.

October 21, 2026Try the RAMP demo ↗
In-Depth Guide
The Situation

A customer sends a security questionnaire that asks which AI systems touch their data. The team answers from memory and lists two. A later review of single sign-on logs, expense reports, and browser extensions turns up many more: a meeting summarizer, a coding assistant, an AI feature inside the support desk, and a model a data scientist called from a personal account.

Where Teams Get Stuck

Most organizations have no single list of their AI systems. Each team knows its own tools, nobody owns the whole picture, and a ban on unapproved tools simply pushes use out of sight. Auditors and customers increasingly ask for an inventory, and an incomplete one is worse than a known gap because it looks like you did not look.

How RAMP Handles It

RAMP builds the AI register from three intake paths: employee self-reports, imports from your identity provider, and spreadsheet uploads. Each item is triaged into the register as an AI system, a non-AI tool, or a duplicate, and every approved system moves on to a requirements document and two-stage approval. The register becomes the starting list for your risk assessment and your audit package.

What counts as shadow AI

Four patterns cover most of it. Standalone chat and writing tools that staff sign up for themselves. AI features added to approved software by an update, often switched on by default. Browser extensions and plug-ins that read page content. Models and APIs that engineers call from code or notebooks. The common thread is that the business is using it and the governance process has not seen it.
The Bottom Line

Shadow AI is mostly not malicious. It is people trying to work faster with tools nobody told them how to request.

Three places to look

Employee reports: a short, no-blame form that asks what tool, what data, and what for. Identity provider data: the list of applications people sign in to with company accounts, and the permissions they granted. Existing records: expense reports, procurement and renewal lists, and any spreadsheet a team already keeps. None of these is complete alone; together they usually surface most of what is in use.

What to do with what you find

Triage each item: is it an AI system, what data does it touch, who owns it, and is it already approved. Record it in one register even if the answer is that it must stop. Systems that stay get a governance requirements document, then the approval gates described in our guide to governing AI in your company. Keep the register current, because a one-time sweep is out of date within a quarter.

Frequently asked questions

What is shadow AI?
Shadow AI is AI that people use for work without the security, legal, or risk teams knowing about it or having approved it. It includes standalone tools, AI features inside approved software, browser extensions, and models called from code.
Why is shadow AI a risk?
Unreviewed AI can receive confidential, personal, or customer data, produce output nobody validates, and create obligations under contracts and regulations that the organization does not know it has. It also leaves gaps when a customer or auditor asks for an AI inventory.
How do you find shadow AI in a company?
Combine employee self-reports, identity provider application data, and procurement or spreadsheet records, then triage everything into a single AI register with an owner for each system.
Leadership Action Item

Do not start with a ban. Start with an inventory: collect from the three sources, triage into one register, and give every system an owner. You cannot govern, price the risk of, or evidence what you have not listed.