Anthropic Compliance API Logging Disabled
Description
Compliance API logging feeds the anthropic.audit dataset that Anthropic audit detections run on. An attacker with administrative access can disable it so later role grants, API key creation, exports, and authentication changes stop reaching this data source. This rule detects the disable action itself. Activity that happens after logging stops may not appear in logs-anthropic.audit-*.
Query · esql
from logs-anthropic.audit-* metadata _id, _version, _index
| where
data_stream.dataset == "anthropic.audit" and
mv_contains(event.category, "configuration") and
event.action == "org_compliance_api_settings_updated" and
anthropic.audit.compliance_api_logging_enabled == false
| keep _id, _version, _index, @timestamp, event.*, organization.*, user.*, source.*, user_agent.*, anthropic.audit.*, data_stream.*
Investigation fields
Pivot points the source recommends for triage.
@timestampevent.actionevent.idorganization.idanthropic.audit.compliance_api_logging_enabledanthropic.audit.compliance_api_enabledanthropic.audit.actor.typeanthropic.audit.actor.admin_api_key_iduser.emailuser.idsource.ipuser_agent.original
Known false positives
- Platform or security administrators disable compliance logging during onboarding, integration testing, or log pipeline migrations. Verify the actor, source IP, and whether logging was re-enabled promptly. Planned changes can be exempted from this rule.
Analyst notes
Investigating Anthropic Compliance API Logging Disabled
Compliance API logging feeds logs-anthropic.audit-*. Disabling it creates a blind window: later admin actions
may not appear in this data source even if other logging remains. Do not assume the timeline after disable is complete.
Unauthorized = no platform/security ticket for Fleet/integration work, and logging was not re-enabled promptly — or disable is paired with role grants, key creation, exports, or SSO changes.
Possible investigation steps
- Confirm
anthropic.audit.compliance_api_logging_enabled == false. Do not confuse withcompliance_api_enabled(whether the Compliance API itself is on). - Branch actor:
admin_api_key_actor→ which key (anthropic.audit.actor.admin_api_key_id);user_actor→ email/IP/UA vs known admins. - Pivot the same
organization.idfor admin grants, key creation, exports, or SSO changes before the disable (still visible) and note the blind window start time. - Gate re-enable: treat the case as open until logging is back on and fresh events appear in
logs-anthropic.audit-*.
False positive analysis
- Integration testing / pipeline migrations can disable logging briefly — require a ticket and verify re-enable.
Response and remediation
- Re-enable compliance API logging first and confirm ingestion resumes. Then reconstruct the blind window via any prior exports, Anthropic support, or other data sources, and review configuration changes around the disable.