Extensions
Every extension across the fleet, with a permission score and a
behavioural verdict — remote code loading, obfuscation,
observed exfiltration paths, publisher reputation change.
- Inventory with install counts and first-seen dates
- Version drift and silent auto-updates that changed permissions
- Store watch for impersonators and ownership transfers
Primary action: set verdict — allow, warn, block, force-remove.
Data movement
Paste, upload, download, form fill and copy — each with its
destination, data class and outcome. Grouped by receiving site,
this is the view that changes the conversation.
- Destinations ranked by volume and sensitivity mix
- Classes: source code, credentials, PII, financial, health
- Where policy actually intervened, and what the user did next
Primary action: create a policy straight from an event.
Shadow AI and SaaS
Unsanctioned LLM and agent tools discovered from real sessions —
not from a static catalogue — with the users, the frequency and
the data classes actually submitted.
- A sanctioning queue, oldest first, so the list never rots
- Adoption trend per tool, and displacement after a block
- Non-AI SaaS discovery in the same shape
Primary action: sanction or restrict.
Devices and coverage
Enrolled devices, browser and extension versions, sidecar
status — plus the number nobody else shows you: identities
active in your IdP with no protected browser at all.
- Coverage gaps — the honest denominator
- BYOD, with what is enforced there and what is not
- Sidecar health: model version, latency, fallback-to-rules rate
Primary action: send an enrolment link.
Policies
Live rules ordered by precedence with hit counts, templates by
regulation and use case, and a full change history with diffs.
- Simulation against the last 30 days before anything goes live
- Who changed what, when, and exactly what changed
- Starting points for GDPR, HIPAA, PCI DSS and DORA
Primary action: new policy.
The egress panel
Every screen in this module carries one persistent line:
analysis ran on device or in your VPC, and only the finding
record crossed the boundary.
- Local-analysis attestation attached to each event
- Redacted context — enough to triage, never the raw payload
- Exportable to an auditor without a second data-flow review
Why it lives here: it is the differentiator, so it belongs in the product, not the deck.