Topic starter
09/07/2026 12:35 pm
TL;DR: AI assistants can overshare even when underlying access looks correct, and research cited in the article shows that millisecond-scale enforcement is feasible while leakage remains a live risk in LLM workflows, according to Knostic. The governance gap is not latency, but whether access control is applied to generated answers rather than only to login and source systems.
Editorial analysis by NHI Mgmt Group, based on content published by Knostic: “The 5 Best Persona-Based Access Control (PBAC) Software Tools”.
Key questions
Q: What breaks when AI authorization happens only at login?
A: A login-only model assumes the session stays safe after authentication, but AI systems may make many later decisions and tool calls across multiple services.
Q: Why do AI assistants overshare even when source permissions look correct?
A: They overshare because source permissions govern retrieval, while generated answers can recombine context into disclosures that exceed the requester’s need-to-know.
Q: How can security teams tell whether PBAC is actually working for AI responses?
A: A PBAC control is working when it consistently blocks or masks content that a user could technically retrieve but should not receive as an answer.
Practitioner guidance
- Implement answer-time disclosure policies Evaluate persona, context, and purpose before the AI output is shown, and deny or mask content when the requester does not meet the need-to-know threshold.
- Test copilots for oversharing paths Run simulated prompts against enterprise search and assistant workflows to identify where generated answers expose content that source-system permissions alone would allow but the requester should not see.
- Separate retrieval access from disclosure approval Document which identities may fetch content and which identities may see it surfaced in generated responses, then map those decisions to the same policy model.
Bottom line: AI answer systems create a disclosure problem that source-system permissions alone do not solve.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
09/07/2026 12:39 pm
Answer-time authorisation is the real governance boundary for enterprise AI. PBAC matters because the security decision now has to happen when the answer is assembled, not when the user first signs in. That shifts identity governance from static access granting to disclosure governance at runtime. For practitioners, the control boundary has moved into the response layer.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between retrieval access and disclosure approval in AI systems?
A: Retrieval access decides whether a system may pull a source item into context. Disclosure approval decides whether the resulting answer may be shown to the requester. In AI governance, those are not the same control, and treating them as one leaves a gap that oversharing attacks can exploit.
👉 Read our full editorial: Persona-based access control for AI answers and oversharing risk