Skip to main content

Data Flow Overview

Beacon collects supported agent harness activity on the endpoint, normalizes it locally, and writes one JSON object per line to a local runtime log. Security teams can inspect that file locally, view it through the loopback dashboard, or forward it through customer-controlled security pipelines.

Data Flow

Threat Model

Current Boundaries

Beacon focuses on supported agent harness telemetry and local endpoint configuration context. It does not provide kernel or process monitoring, shell history collection, cloud audit ingestion, browser or SaaS telemetry, credential-use attribution, Datadog API export from Beacon, Sumo Logic API export from Beacon, Rapid7 API export from Beacon, or automatic mutation of Factory Droid shell profiles. Provider-managed cloud agents use a separate ephemeral boundary from the local endpoint. Their hook adapter writes sandbox-local JSONL and can send compressed snapshots directly to customer-managed object storage. Upload failures are fail-open so telemetry delivery cannot block the agent task; verify the remote object rather than treating a successful agent run as proof of delivery.

Open Source Architecture

Follow the collection, normalization, storage, and forwarding architecture.

Agent harness integrations

Review supported runtimes, destinations, MDM support, and current boundaries.