What Feeds Defend
Defend merges events from two sources into one list:
When the same request appears in both sources, Defend shows it once.
The DLP summary reads only from Targets of type
dlp. A dlp Target receives its events
from a Dome proxy. It runs no scans, and no Collector
reports into it. The Console creates scanner Targets only. To create a dlp Target, use
the discover_deployment_create MCP tool with type set to dlp. See
Create and Manage Targets.
With no dlp Target, the DLP summary stays empty. The event cards still show Console Dome
events.
Read the DLP Summary
The DLP target selector scopes this section only: All targets, or a singledlp
Target. The event cards below always cover every source.
An errored event means the Guardrail failed to reach a verdict, so the traffic passed
unchecked. Watch this counter.
Unattributed flagged counts detections that Dome failed to tie to a registered Agent.
Any number above zero means traffic is routing through the proxy from a source your
Agent Registry is missing.
Inspect an Event
Click a row to open the details panel beside the cards. The panel shows:- Fields: Group (the Agent), User, Detector or policy, Direction, whether the decision was Enforced, and Time.
- Content: the prompt or model response that triggered the event.
- View the whole turn: for a Console event, opens the trace in the Agent’s Monitor tab. For a Discover event, the panel lists the other steps of the same turn.
- More from this user: filters the page to the same user ID.
Read the Posture Section
Below the cards, Open violations and Alerts list what Discover is tracking for your estate, each with a severity badge.When a Source Is Missing
If one source fails, Defend still shows the other and explains the gap with a banner:Next Steps
Configure Guardrails
Change what Dome enforces for an Agent.
Observability
Per-Agent Guard execution logs and telemetry.