Connecting Your Data to LLMs: Identity, Functions and Agents are all you Need - BRKETI-2411#

Guillaume De Saint Marc (Cisco)

• Why: Agentic identity is one of the PM's explicit interests and almost absent from vendor programs — this is the closest hit: per-request authorization deciding which data an agent may fetch and serve.
• What: Architectures and tools for connecting enterprise data (including on-prem) to LLMs without data migration, including real-time prompt inspection to identify the data required by a request, determine whether the user has rightful access, and serve only authorized data (from abstract only).
• How: Prompt-time authorization — mapping an incoming prompt to data requirements and checking entitlements before data is served to the model.
• Where applicable: Enterprise GenAI deployments; Cisco brings product positioning, but the underlying pattern — entitlement-aware data serving for agent requests — is broadly relevant to anyone designing agentic identity.