Notifications
Clear all
Topic starter
16/08/2026 4:59 pm
TL;DR: AI agent deployments fail most often when retrievers overexpose internal knowledge rather than when models take unapproved actions, according to Visiq Labs. The article argues that retrieval governance must operate before context injection, because once restricted material enters the context window, output filtering cannot undo the exposure or its downstream effects.
NHIMG editorial — based on content published by Visiq Labs: Sensitive Knowledge and Retrieval Governance
By the numbers:
- 64% of valid secrets leaked in 2022 are still valid and exploitable today, proving that detection alone is not enough without automated revocation.
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers.
Questions worth separating out
Q: How should security teams handle AI agent visibility?
A: Security teams must conduct an exhaustive discovery process to identify all deployed AI agents, both sanctioned and unsanctioned, across the organization.
Q: Why do AI agents create a different access problem from human developers?
A: AI agents create a different access problem because they can parallelise work, retrieve context on demand, and initiate actions without the pauses that human workflows naturally create.
Q: What breaks when retrieval is governed only by output filters?
A: Output filters can hide text after generation, but they cannot undo prior exposure.
Practitioner guidance
- Map retrievers as access points Inventory every vector store, search tool, memory lookup, and document-returning API that can feed an agent.
- Apply need-to-know at document level Build policy so each returned document is evaluated before injection, with allow, redact, or deny as the only outcomes.
- Record every retrieval decision Preserve signed evidence for the matched policy, the document identity, the outcome, and any masked fields.
What's in the full article
Visiq Labs' full whitepaper covers the operational detail this post intentionally leaves for the source:
- A worked policy example showing how document metadata, trust tier, and function combine into per-document decisions.
- The four-phase rollout model for moving from observation mode to enforced redaction and denial.
- Specific scenario breakdowns for finance, HR, support, and engineering assistants.
- The evidence model for signed retrieval decisions, including what auditors can verify later.
👉 Read Visiq Labs' whitepaper on sensitive knowledge and retrieval governance →
AI agent context windows: what retrieval governance needs to change?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
16/08/2026 5:00 pm
Retrieval governance is the missing authorization layer in AI agent architectures. Most enterprises still think about model output as the primary risk surface, but the real boundary failure happens earlier, at document admission. Once sensitive material enters context, the agent has already been authorised to see more than its task requires, even if no prohibited action follows. The implication is that identity governance for AI agents must control exposure, not just execution.
A few things that frame the scale:
- 64% of valid secrets leaked in 2022 are still valid and exploitable today, according to The State of Secrets Sprawl 2026.
- The same research found that AI-related credential leaks surged 81.5% year-over-year in 2025, with surrounding AI infrastructure leaking 5x faster than core LLM providers.
A question worth separating out:
Q: Who should approve exceptional access to restricted documents in agent workflows?
A: A designated human approver should handle exceptional access when the request is genuinely outside normal need-to-know boundaries. The approval should be recorded with the document identity, policy outcome, and reason for access. That gives audit, security, and governance teams a verifiable trail instead of an untracked exception.
👉 Read our full editorial: Sensitive knowledge retrieval governance for AI agent context windows
