Topic starter
09/07/2026 12:37 pm
TL;DR: Glean combines LLMs, semantic search, and permission-aware retrieval to reduce enterprise search friction, but Knostic argues that oversharing persists because static access models cannot reliably enforce need-to-know boundaries when AI synthesises context from multiple systems. The real governance problem is not search accuracy, but whether AI can expose permissible yet operationally inappropriate information.
Editorial analysis by NHI Mgmt Group, based on content published by Knostic: “Glean Secures LLM Search. Who Stops Oversharing?”.
Key questions
Q: What fails when AI search uses static permissions alone?
A: Static permissions control access to source objects, but they do not fully control how an AI system recombines approved fragments into a new answer.
Q: Why can enterprise AI search overshare even when ACLs are in place?
A: ACLs can block direct access to specific source content, but they do not always govern synthesis across multiple permitted sources.
Q: What do security teams get wrong about AI search oversharing?
A: They often assume encryption, tenant isolation, and source permissions solve the disclosure problem.
Practitioner guidance
- Define response-time disclosure policy Set explicit rules for which combinations of source documents, chats, tickets, and metadata may be synthesised into one answer for each role.
- Instrument prompt and response logging Capture the user prompt, retrieval path, cited sources, and final answer so security teams can review why a given synthesis was produced.
- Test for contextual oversharing Run red-team queries that combine individually permitted fragments from multiple systems to see whether the model reveals strategy, timelines, or sensitive operational context.
Bottom line: AI search changes the access-control problem from retrieving documents to governing what the generated answer is allowed to disclose.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
09/07/2026 12:43 pm
Need-to-know is the broken assumption: Static permissions were designed for object access, not for AI synthesis across multiple permissible sources. That assumption fails when the actor is a language model that can assemble contextually inappropriate answers from fragments the user was never meant to see together. The implication is that enterprise search governance has to measure disclosure risk at response time, not only entitlement status at source.
A few things that frame the scale:
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: What should organisations govern when AI search sits on top of enterprise data?
A: They should govern the disclosure rules for generated answers, not only the entitlements on the underlying repositories. That means deciding which roles may receive synthesised context, which source combinations are allowed, and which topics require review before the AI response is shown.
👉 Read our full editorial: Glean AI search increases oversharing risk beyond static permissions