Review data flows

Data Flows summarizes relationships that send data between agents, models, tools and endpoints. Use it to identify destinations that need an owner, an authorization review or additional evidence.

Investigate a destination

Select the relevant source or flow in the chart, then inspect the underlying rows. The table and chart use the same dataset. Follow the linked asset or evidence to understand why the destination appears.

Check whether a flow is configured, inferred or observed. Runtime data can report outbound destinations, but missing telemetry does not establish that no outbound data exists. A configured remote server URL does not prove that sensitive information was sent there.

A practical review

For each important destination, record:

• The agent, tool or identity associated with it.
• The evidence state and collection time.
• Whether your organization expects this destination.
• The source control or runtime control that authorizes it.
• Any open findings, gaps or follow-up checks.

Use Runtime to inspect individual reported events. A heuristic about a new destination is a lead for investigation, not proof of data exfiltration.

What is not shown

ModelFence does not capture prompt or completion bodies. It does not currently produce the classification, retention or geographic fields needed to make a complete data residency assessment. Confirm those requirements through your own systems and provider agreements.