Matched call
The identity and call line up.
Review the recorded decision.
Compare available AI traffic logs with Fabriq records. Investigate what doesn’t match.
Get a free assessmentUpload network logs for a snapshot, or stream them for ongoing discovery. Fabriq matches incoming activity against known agents and recorded calls.
ZscalerProxy, firewall, and SIEM logs.
Discovery depends on the signals you provide.
Connect the signal to the agent.The source points to forecast-worker, but no corresponding Fabriq call was found. Inspect the route to understand the gap.
Each classification keeps the evidence separate from the conclusion. A missing match is a reason to investigate, not proof of misuse.
The identity and call line up.
Review the recorded decision.
A known caller. A missing record.
Check how this connection reached the service.
A connection without a clear owner.
Use source, time, and available user or IP details.
Consumer AI chat activity is counted separately. A visit to an AI chat service does not, by itself, identify an agent.
Fabriq checks incoming logs against known agent activity, 24/7. New or unmatched signals stay visible for review.
Coverage and freshness depend on connected logs. Discovery identifies activity; policy enforcement requires a configured Fabriq access path.
Talk with our team about your available log sources and where to begin investigating AI activity.
Request your assessment