Elastic high stable kql
Anthropic Compliance API Key Created
Compliance-scoped API keys read organization audit activity and compliance data. Once an attacker has administrative access, creating one gives them programmatic read of chats, files, and membership without an interactive session. This is separate from admin API key creation, which covers organization administration rather than compliance read scopes.
Detection Logic
from logs-anthropic.audit-* metadata _id, _version, _index
| where
data_stream.dataset == "anthropic.audit" and
event.action == "api_key_created" and
event.outcome == "success" and
anthropic.audit.scopes is not null and
(
mv_contains(anthropic.audit.scopes, "read:compliance_activities") or
mv_contains(anthropic.audit.scopes, "read:compliance_org_data")
)
| keep _id, _version, _index, @timestamp, event.*, organization.*, user.*, source.*, user_agent.*, anthropic.audit.*, data_stream.* False Positives
- ⚠ Platform and security teams create compliance-scoped API keys when onboarding the Anthropic Fleet integration or setting up SIEM ingestion. Verify the actor and confirm the key is in the approved credentials inventory.
Field Validations
Loading…
Comments (0)
Loading comments...