Skip to main content
TrustGuard is NeuralTrust’s runtime security engine for generative-AI and agentic traffic. It inspects prompts, model output, documents, URLs, and agent/tool activity in flight and returns a structured security verdict for each request. TrustGuard is deliberately decision-only: it tells you what it found and what it would do, but it never blocks or drops traffic itself. The component that calls TrustGuard (the collector) decides whether to allow, mask, or block based on the verdict. This keeps TrustGuard safe to deploy inline anywhere — a failure or timeout can never take your application down.
TrustGuard is one of four NeuralTrust products. It pairs naturally with TrustGate (the AI gateway, the most common collector), TrustLens (AI security posture), and TrustTest (red teaming).

​
What it does

Prompt & content security

Jailbreak and prompt-injection detection, topic moderation, toxicity scoring, and document/URL analysis on both input and output.

Data loss prevention

Detect and mask 43 PII entities and secrets (API keys, tokens, JWTs) in flight, returning a transformed payload.

URL & document analysis

Fetch and screen URLs, and extract text from uploaded documents (including OCR) for jailbreaks and PII before they reach the model.

Secrets in flight

Catch leaked credentials and sensitive tokens in prompts and model outputs alongside PII masking.

​
The model in one minute

TrustGuard has four building blocks. You compose them once, then send traffic.
A request names no detectors: TrustGuard resolves the collector’s policy and runs its gates and the detector rules that match the request’s direction and conditions. See How it works.

​
What makes it safe to run inline

Traffic with no matching policy is unguarded: TrustGuard returns status: "allow" with no inspection. Attach a default (or per-consumer) policy on the collector after setup.
  • Never drops traffic. A detection is always HTTP 200 with the finding in the response body. Non-2xx is reserved for auth (401), bad requests (400), and system failures (500).
  • Fail-open or fail-closed — your choice. If a detector errors (e.g. an upstream model API is down), TrustGuard either drops that detector’s result and continues (fail-open) or returns 500 so you can hold traffic (fail-closed). The mode is configured per deployment (ask NeuralTrust if unsure). A structured block decision always applies.
  • Enforcement is the caller’s choice. The response status (allow / report / transform / block) is advisory. Your collector decides what to do with it.

​
Get started

  1. Create a collector (TrustGate, SDK/REST, or another collector).
  2. Create detectors from the catalog.
  3. Create a policy with Input and Output detectors chained and configure rules if needed.
  4. Attach the policy to the collector created (default and/or per-consumer).
  5. Test in playground.
  6. Verify traffic in Activity.

​
Where to go next

How it works

The guard pipeline, gates, and the findings model.

Core concepts

Detectors, policies, and collectors.

Policies

Gates, detector rules, and the Report / Enforce switch.

Detector catalog

Every built-in detection and its settings.

Evaluate API

The POST /v1/evaluate request and response contract.

Telemetry Alerts

Turn guard findings into prioritized alerts — prompt-injection spikes, leaked PII/secrets, toxicity bursts.