Collectors — overview & coverage
A collector captures AI activity from one layer of the environment and forwards it — with metadata and any local detection verdict — to the Lumen control plane. Collectors group by where the code runs:
| Group | Collectors | Runs |
|---|---|---|
| Host-local (the hard part) | Endpoint agent + Browser extension | On the managed device |
| Instrument-the-code | Application SDK, Agentic / MCP proxy, OpenTelemetry | In the built AI system |
| Network / platform | Gateways (Kong, LiteLLM, Portkey), Cloud (Bedrock + logs) | At the API boundary / in the cloud account |
Coverage matrix
| Surface | Collector(s) | Inline enforce? |
|---|---|---|
| AI use in browsers (ChatGPT, Claude, Gemini, …) | Browser extension | Yes (redact/block in-page) |
| Internal applications | Application SDK + inline API | Yes (pre/post model call) |
| Agentic / MCP traffic (client ↔ server) | MCP proxy | Yes |
| Developer AI tooling (Claude Code, SDKs, CLIs) | Endpoint agent proxy + hooks | Yes |
| API gateways (Kong, LiteLLM, Portkey) | Gateway plugin | Yes |
| Cloud platforms (AWS Bedrock) | Cloud ingestion | Log/redact (async) |
| OpenTelemetry GenAI telemetry | OTel receiver | Log (observability) |
Every collector can raise every detection class.
How an interaction flows
- Capture. A collector observes one AI interaction: the request (prompt, model, parameters) and/or the response, possibly streamed token by token.
- Enrich. Metadata is attached — user identity, device id, application or process, collector id, provider/model, tenant id.
- Evaluate. The collector's policy runs: access rules decide whether and how to process; prompt rules inspect the content. The local fast-path returns the inline verdict; deeper cloud detection runs asynchronously.
- Act. Log, Redact, or Block.
- Ship. The interaction and its verdict are spooled and drained to the Lumen cloud over outbound-only mTLS.
- Correlate. Findings power the console dashboards and export to the Wazuh Indexer.
Inline vs monitor
For Block/Redact the collector must sit in the data path and get a synchronous verdict (browser extension, SDK, MCP proxy, gateway, endpoint proxy). For Log-only it may observe out of band (cloud logs, mirrored traffic). The inline latency budget is a first-class design constraint: the verdict is local and takes single-digit milliseconds; the cloud never sits in the request path.