Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

Glossary. Shadow AI.

What is shadow AI, and what should you check first?

Shadow AI is AI used at work without approval. What decides the risk is the data each tool can reach, so the register starts there for approved tools as well.

By Dipal Panchal, co-founder and CEO · Updated November 8, 2026

The tool matters less than its reach

Shadow AI is the use of AI tools, assistants or agents at work without the organization’s approval or knowledge, with company data pasted, uploaded or connected to them. Unlike shadow IT in general, the risk sits in the data a tool can reach more than in the tool itself. The first check on any AI tool, approved or not, is what it can read.

The usual forms are a public chatbot used from a browser, a browser extension granted access to email, and an AI feature a vendor switched on inside an approved application.

An AI-tool register, six rows

Tools in one company, reviewed on November 7, 2026. The Role or group column records approval and who uses each tool.

Records
IdentityRole or groupObjectPrivilegeLast usedDecision
Enterprise AI assistantApproved; licensed to all staffEvery Microsoft 365 file the user can openReads with each user’s own permissionsDailyKeep; fix overshared HR and finance libraries before wider use
Public chatbot, free tierNot approved; finance team, UKWhatever staff paste or upload: spreadsheets, PDFsUploads by usersNovember 4, 2026Block on the corporate network; point users to the approved assistant
Meeting-notes browser extensionNot approved; sales team, IndiaCalendars and email bodiesOAuth consent granted by each userNovember 6, 2026Revoke the consents; require admin approval for new apps
Coding assistantApproved; engineeringSource repositories, including config filesApp installed on the code hostDailyKeep; remove the keys found in config files first
support-bot, an in-house agentApproved pilot; supportEvery CRM table, through a service accountDatabase SELECT on the whole crm schemaNovember 7, 2026Narrow the account to the three columns the bot uses
AI feature in the HR systemNot assessed; switched on by the vendorEmployee records already in the HR systemBuilt into an approved applicationNot measuredExcluded from the block list; assess under the vendor contract first

Where unapproved tools show up

Unapproved tools leave records in places security already holds. OAuth app consents in your identity provider show extensions like row 3. Proxy or DNS logs show traffic to AI services like row 2, and expense reports show the subscriptions nobody filed with IT.

Rows 1, 5 and 6 show why the register covers approved tools too. Each has approval, and each reaches more data than its job needs until someone narrows the access.

The rules that ask for a register

None of these uses the term shadow AI. Each asks for something an AI-tool register provides.

The rules that ask for a register
RuleProvisionWhat it asks
NIST AI Risk Management Framework 1.0GOVERN 1.6Mechanisms to inventory AI systems, resourced according to organizational risk priorities
EU AI ActArticle 4, as replaced by Regulation (EU) 2026/1744, Art. 1(5), in force from July 27, 2026Providers and deployers take measures to support AI literacy among staff and others using AI systems on their behalf
GDPR and UK GDPRArticle 28A processor handling personal data for you works under a contract with set terms

Check the data before the model

Dipal Panchal, Sylox’s co-founder and CEO, made the point on the FutureGPT panel in June 2026: “The model is rarely the risk. The risk is the data feeding it and the access around it.” Row 5 is that case: an approved bot with a read grant on every CRM table.

On an advisory call in 2026 he called the upload route the common one. A company licenses an AI assistant for every employee, and staff upload spreadsheets and PDFs that hold company data the company does not know about. So for every tool in the register, record what data it can reach, and narrow that before you decide whether to approve it.

What a register can’t see

A register lists the tools you found. A personal phone used with a personal account, outside the corporate network and identity provider, leaves none of the records above.

It also can’t recall data already uploaded. Once a spreadsheet is pasted into a public tool, the vendor’s terms decide what happens to it, which is why row 2 is blocked outright.

With IRIS

IRIS maps who can reach sensitive data in supported sources, and an agent’s service account is one more identity in that map. Capabilities vary by edition.

What an agent’s database or Microsoft 365 account can reach: IRIS produces part of this, for supported sources that expose permission data.

Sensitive data in the files an assistant can open: IRIS produces part of this, in the sources you connect.

Which public AI tools staff use (your web proxy or CASB logs show the traffic): Not produced by IRIS.

Blocking uploads or revoking app consents: Not produced by IRIS.

Explore AI governance

Pull the latest app consents

Export the OAuth app consents from your identity provider for the past month and mark every AI tool among them approved, not approved or not assessed. The first register is done when each tool has a row with the data it can reach and a decision.

Before an approved assistant goes wide, review oversharing in the libraries it will read, then work through the checklist for AI assistant oversharing.

Official sources

  1. NIST AI Risk Management Framework (AI RMF 1.0), GOVERN 1.6, NIST. Opened November 8, 2026.
  2. Digital Omnibus on AI, Regulation (EU) 2026/1744: Article 1(5) and amended Article 113, European Parliament and Council. Opened November 8, 2026.
FAQ

What security teams ask about shadow AI

Protect your brand. Start with your data.

Bring the service accounts your AI agents use. We’ll show what sensitive data they can reach, in supported sources.