Configuration
Access Through Human Identity
Access Through Non-Human Identity
Autonomous Action Control
Connected Tools and Functions
Enterprise Retrieval Access
External Communication Access
Model and Build Provenance
Model Objective Alignment
Orchestrated AI System
Persistent Memory Access
Standing Instruction Stack
Vendor-Embedded AI
- ID: CF004
- Created: 26th August 2026
- Updated: 26th August 2026
- Contributors: Nimer Kees, James Weston,
Enterprise Retrieval Access
Enterprise retrieval access is the configuration of corpora, indexes, connectors, and Retrieval-Augmented Generation (RAG) pipelines that a synthetic subject can retrieve from. A corpus is a collection of documents, records, messages, files, or other source material made available for search or retrieval. RAG is a design pattern where relevant source material is retrieved before the synthetic subject generates an answer or takes action.
This configuration creates an elevated exposure condition because retrieval defines what internal information can enter the synthetic subject’s context. If retrieval spans mailboxes, documents, tickets, customer records, wikis, source code, or other enterprise stores, the synthetic subject may combine information across repositories, sensitivity levels, and access boundaries.
The primary risk is retrieval beyond entitlement. A synthetic subject may retrieve, summarize, or expose information that the human requester is not authorized to view. This may occur through shared indexes, broad connectors, cached embeddings, service identities, incomplete query-time access checks, or retrieval pipelines that do not enforce per-user permissions.
A related risk is untrusted content in retrieval context. Externally sourced documents, inbound emails, customer records, support tickets, uploaded files, or partner content may be indexed and later retrieved into the synthetic subject’s context. If that content contains malicious or misleading instructions, it may influence the synthetic subject during an otherwise legitimate request.
Investigators should review retrieval configuration, connected corpora, index membership, connector permissions, query logs, documents returned, requester identity, access-control decisions, prompt and response records, and output destinations. Particular attention should be given to cross-boundary retrieval, sensitive content in outputs, externally sourced documents, and cases where retrieved material exceeded the requester’s entitlement.
Investigative Relevance
Enterprise retrieval access is relevant because retrieval configuration determines what information a synthetic subject can see and use. Weak retrieval boundaries may turn an assistant or agent into a bridge between restricted information and an unauthorized requester.
This section is especially relevant where synthetic subjects retrieve from enterprise search indexes, RAG pipelines, mailboxes, file stores, collaboration platforms, ticketing systems, customer relationship management platforms, source repositories, or shared document corpora.