Skip to Content
DeploymentAnthropicOverview

Anthropic

Arrakis governs Anthropic products through two complementary planes — endpoint-side telemetry for Claude Code (native OpenTelemetry emitted by the CLI) and org-side inventory and audit for Claude Cowork (Anthropic Admin API plus SSO/SCIM). Coverage across the four pillars (configuration, runtime, reasoning, preventive) is scored on the Connectors page.

Primary data planes

  • Claude Code — native OpenTelemetry. Claude Code ships an OTLP exporter (logs, metrics, and beta traces). Arrakis-recommended pattern is MDM-managed settings that pin the OTLP endpoint, header secret, and content-control flags so policy is fail-closed. → Claude Code
  • Claude Cowork — Admin API + SSO. Web-only Cowork sessions are governed entirely server-side via the Anthropic Console. Where Cowork ships the Claude Code desktop footprint, the same managed-settings payload applies. → Claude Cowork

Where telemetry lands

All coding-telemetry paths on this page terminate at the Arrakis coding-telemetry ingest, which runs the shared detection rules (typosquatting, secret exposure, template injection, tool collision, and others). Whether telemetry arrives as native OTLP, a hook-emitted event, or an admin-API pull, it is normalized into the same event registry.

Pages in this section

  • Claude Code — Anthropic Console (Enterprise) walkthrough, Bedrock variant, MDM payloads for Jamf/Intune/Iru.
  • Claude Cowork — Admin API issuance and rotation; managed-settings reuse where Cowork ships the Claude Code footprint.

Cross-references

Last updated on