> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usetrident.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Agent Security: Trace, Test, and Protect in Production

> An overview of Trident's agent security capabilities: distributed tracing, automated red-teaming, runtime firewall, and findings management.

Trident gives you end-to-end security coverage for AI agents — from the first prompt your agent receives to the findings that land in your inbox. This section covers the four pillars of agent security in Trident: distributed tracing to capture every LLM call and tool invocation, automated red-teaming to discover vulnerabilities before attackers do, a runtime firewall to block prompt injection and jailbreaks in production, and a findings inbox to triage, replay, and resolve issues.

<CardGroup cols={2}>
  <Card title="Tracing" icon="chart-network" href="/agents/tracing">
    Automatically capture every prompt, tool call, and LLM response your agent makes — with zero-config PII redaction built in.
  </Card>

  <Card title="Red-Teaming" icon="sword" href="/agents/red-teaming">
    Run 200+ adversarial attack vectors against your agents covering the full OWASP Agentic Top-10.
  </Card>

  <Card title="Firewall" icon="shield-halved" href="/agents/firewall">
    Scan every prompt and output for injection attacks, jailbreaks, and data exfiltration attempts in real time.
  </Card>

  <Card title="Findings" icon="circle-exclamation" href="/agents/findings">
    Review, replay, and resolve security issues from red-team runs, the firewall, static analysis, monitors, and agent self-reports.
  </Card>
</CardGroup>

## End-to-end workflow

Trident's agent security features are designed to work together across the full development and production lifecycle.

<Steps>
  <Step title="Instrument">
    Install the Trident SDK and call `trident.init()` (TypeScript) or `vouch_sdk.init()` (Python) once at startup. The SDK wraps OpenLLMetry and auto-traces every LLM call in the process — no additional code required.
  </Step>

  <Step title="Red-team">
    Before you ship, run a red-team campaign from the dashboard or via the API. Trident fires 200+ attack vectors at your agent and scores every result against the OWASP Agentic Top-10 and AIVSS severity scale.
  </Step>

  <Step title="Firewall">
    In production, route prompts through the Trident gateway proxy or call `trident.scan()` directly before each LLM call. Every prompt passes through a two-stage firewall: your project's custom deny rules fire first, then the LLM Guard ensemble.
  </Step>

  <Step title="Review findings">
    All issues — from red-team campaigns, the runtime firewall, static analysis, monitors, and agent self-reports — land in the Findings inbox. Confirm a finding to automatically push a new firewall rule. Replay it at any time to verify your fix.
  </Step>
</Steps>

## Supported frameworks

Trident's tracing and firewall integrations work with every major LLM framework and provider. Install the SDK and your existing code is instrumented automatically — no framework-specific plugins required.

**LLM providers:** OpenAI, Anthropic, Amazon Bedrock, Google Vertex AI, Cohere

**Agent frameworks:** LangChain, CrewAI, LlamaIndex

**Protocols:** Model Context Protocol (MCP)

## PII redaction

Trident redacts sensitive data **in your process** before any trace data leaves your infrastructure. The following patterns are scrubbed from span attributes automatically:

* Email addresses
* Credit card numbers (validated with Luhn checksum)
* US Social Security Numbers (SSNs)
* AWS access key IDs
* JSON Web Tokens (JWTs)
* API keys (OpenAI, Anthropic, and similar `sk-` prefixed secrets)
* IBANs
* IPv4 addresses
* Phone numbers

You can supply your own redaction rules or disable redaction entirely by passing options to `trident.init()`. See the [Tracing](/agents/tracing) page for details.