SecureLLM.ai

Home › Could it leak information between departments?

Could it leak?

AI didn't create the leak, it found it

Updated November 2026 · About 5 minutes to read

The short answer

In most companies, plenty of files are shared far more widely than anyone intended. Until now, nobody stumbled on them, because nobody knew where to look.

An AI assistant that searches everything a person is allowed to open finds those files in seconds. It isn't breaking any rule; the rule was already broken. That's why the clean-up has to come before the rollout, not after.

Think of an office full of unlocked drawers

For years, some drawers were left unlocked. It didn't matter much: nobody had time to open every drawer in the building.

Now hire an assistant who opens every unlocked drawer in a second and tells anyone who asks what's inside. The drawers haven't changed. What changed is that someone finally looks.

Where the picture stops working: the assistant doesn't just find a file, it reads it and repeats what's in it, so a salary sheet can turn up as one line inside an ordinary answer.

Why the assistant finds what people never did

Assistants built into your office software follow the permissions you already have. Microsoft, for example, says its Copilot "only surfaces organizational data to which individual users have at least view permissions", and that getting those permissions right is up to you (Microsoft Learn).

That's the right design. But it means every over-generous setting now matters. Two common ones:

  • "Anyone with the link." Anyone who has the link can open the file without signing in. Microsoft notes you "can't track who has access to shared items or who has accessed shared items" (Microsoft Learn).
  • "Everyone except external users." A built-in group that "automatically includes all internal users". A file shared with it is open to every employee (Microsoft Learn).

Files shared like this years ago, for one project, are still shared like this today.

Step through it

How an old setting turns into today's answer

Salary sheetshared with everyone, years ago
The assistantreads what the person may open
A sales rep asks"What do people in my role earn?"
The answerquotes the salary sheet
  1. Years ago, a salary sheet was shared with everyone in the company, for one project, and never narrowed again.
  2. The assistant follows your permissions, so it can read anything the person asking may open, including this sheet.
  3. A sales rep asks an ordinary question about pay.
  4. The answer quotes the salary sheet. The assistant broke no rule: the sharing was already wrong.
  5. Narrow the sharing before launch, and the same question turns up nothing private.

How a well-run rollout handles it

  • Find the wide-open places first. Microsoft offers reports that list sites shared with all employees, to help "identify broad internal exposure that could lead to unintended data access" (Microsoft Learn). Other platforms have similar reports.
  • Ask the people who own the content. Microsoft's guidance: "Site owners are best positioned to review and address oversharing issues for their own sites" (Microsoft Learn). IT can't judge whether a folder should be open; the department can.
  • Keep sensitive areas out of the assistant while you clean up. Microsoft's Restricted Content Discovery hides chosen sites from company-wide search and Copilot. It's meant as a temporary measure and "doesn't change existing permissions" (Microsoft Learn).
  • Start early. On the same page, Microsoft notes that for very large sites a change "could take more than a week" to take effect.
  • Then fix the permissions themselves. Hiding a site from the assistant doesn't stop people opening it directly. The lasting fix is narrower sharing. How the assistant knows who may see each document.

What goes wrong when the clean-up comes later

  • The first person to find it isn't IT. It's someone who asked an innocent question and got a colleague's salary or a draft layoff plan in the answer.
  • It looks like the AI's fault. The assistant gets switched off, and the real problem, the sharing, stays.

99%

of organizations have sensitive data that an AI assistant could easily surface, according to a review of 1,000 company IT environments.

Varonis, 2025. Varonis sells tools for this problem.

Many companies are waiting

In a survey of 279 IT and security decision-makers, 66% said their organization had delayed or cancelled Microsoft Copilot over fears it could expose confidential SharePoint data (CoreView, 2026; reported by IT Brief). CoreView sells Microsoft 365 management tools.

Questions to ask your IT team or vendor

  1. Before we switch it on, how many files and sites are shared with everyone, or by "anyone" links?
  2. Who will review them: IT, or the people who own the content?
  3. Can we keep the most sensitive areas out of the assistant until that review is done?
  4. After launch, how will we spot new over-sharing as it happens?
  5. Can we see a test: an ordinary employee asking about salaries, layoffs or a pending deal, and getting nothing they shouldn't?

Other names you may hear

Oversharing
Files or sites shared more widely than they should be.
Permission sprawl, access creep
Access that builds up over the years and is never taken away.
Anyone link, anonymous link
A link that works for whoever has it, without signing in.
EEEU
"Everyone except external users": a group that includes every employee.
Data access governance, access review
Regularly checking who can open what, and narrowing it.
Restricted Content Discovery, Restricted SharePoint Search
Microsoft settings that keep chosen sites out of search and Copilot.