Views:

Integrate with the Anthropic Compliance API by deploying the Claude Compliance Collector, a customer-deployed collector that automatically retrieves Claude Enterprise conversation data and scans it for policy violations using AI Guard.

The Claude Compliance Collector runs on a schedule in your own environment, pulling conversation content directly from the Anthropic Compliance API and scanning it for policy violations using AI Guard. You can review and investigate detections in the AI Application Security dashboard, giving you the visibility and audit trail that compliance programs require.
Your Anthropic Compliance Access Key never leaves your infrastructure. Conversation content is forwarded to AI Guard for scanning — either your self-hosted deployment or TrendAI-hosted AI Guard.
You can deploy the collector as an AWS CloudFormation stack or as a Helm chart on Kubernetes. Both deployment methods run the same collection and scanning logic and report to the same AI Application Security dashboard — choose whichever fits your environment.

How It Works

After deployment, the collector runs automatically on a configurable schedule (every four hours by default) and completes the following steps:
  1. Scans the Anthropic Compliance API Activity Feed to discover active Claude chat IDs within the configured time window, automatically excluding deleted chats.
  2. Retrieves conversation content for each discovered chat, including prompts, model responses, and any text content sent alongside uploaded files.
  3. Chunks large transcripts and forwards them to AI Guard for policy violation detection.
  4. AI Guard detections appear in the TrendAI Vision One™ AI Application Security dashboard, where you can filter results by the collector's application name and investigate flagged interactions. For more information about AI Guard, see AI Application Security.

Deployment Resources

The resources created depend on which deployment method you choose.
AWS CloudFormation provisions:
  • Lambda functions
  • SQS queue
  • EventBridge schedule
  • Secrets Manager secrets (stores API keys encrypted at rest)
  • IAM roles
  • CloudWatch Log Groups
Kubernetes (Helm) provisions:
  • A CronJob that runs the collector on schedule
  • A namespace-scoped ServiceAccount
  • Optionally, a NetworkPolicy restricting egress
For a Kubernetes deployment, you create the Secret holding your API keys yourself before installing — the chart never creates or populates Secret material.

Requirements

Before deploying the collector, verify that your environment meets the prerequisites. See Claude Compliance Collector prerequisites.
Related information