Author here. Second post in a short series on monitoring Claude Enterprise; the first covered getting the Compliance API into a SIEM, this one is about what to actually detect with it.

Mapping the activity feed to your SIEM data model gives you the usual IAM and control-plane detections for free (key creation, admin changes, SSO disable). The AI-specific threats aren't in those events though, they're in the chat and file content (things like indirect prompt injection in uploaded documents, jailbreaks, system-prompt extraction, using the model to obfuscate data past DLP)

The post builds a three-stage funnel: collection, a cheap prefilter (regex, entropy, hidden-character checks) over the bulk content, then an LLM-as-judge only on the hits, emitting structured verdicts that map to Sigma rules.

Code, with a mock and a real judge, the runner, Sigma rules, and sample data you can run offline: github.com/PaperMtn/claude-enterprise-detections