Skip to main content
TrustGuard ships a fixed catalog of detectors. You don’t build a detector from scratch — you pick one from the catalog, configure its settings, then reference the detector you created from a policy. This page is the index of what’s available; each catalog detector’s full settings live on its category page (linked below). The console’s Detectors → Catalog (Agent Runtime) lists the catalog grouped by category, with a configuration form for each detector’s settings. Sensitivity is aligned across detectors to three levels: Permissive, Balanced (recommended), and Strict.

​
Categories

​
The catalog

Each catalog detector is identified by a stable slug. Sides = which directions it supports. Mutable detectors can rewrite the payload (so they support the Transform action).

​
Data loss prevention

​
Content security

​
How the catalog, detectors, and policies fit together

  • A catalog detector is a fixed capability — you can’t change its code, only its settings.
  • A detector is a named, reusable instance you create from a catalog detector plus its settings. It is detection‑only.
  • A policy references detectors in rules that set the action (Monitor / Block / Transform) and the evaluation phase (Input / Output).
  • Only data_loss_prevention is mutable — the only catalog detector where Transform is valid and the only one that can populate transformed_payload.