Standardized logging replaces per-team event submission

Cloudflare has entered beta on Automatic Audit Logs, a system that unifies audit logging across its products. Under the previous model, individual product teams were responsible for generating and maintaining their own audit logs, which produced coverage gaps and a fragmented experience. The new approach emits a log automatically in a standardized format whenever an action is performed, removing that per-team dependency.

An audit log records who performed an action, what it was, when and where it occurred, and how it was executed. That record supports vulnerability identification, regulatory compliance and operational troubleshooting.

What changed in the beta

  • Coverage: the product count rises from 62 to 111, moving overall coverage from 75% to 95%. Actions from the /accounts, /zones and /organizations APIs are now captured.
  • Consistent format: uniformly formatted entries can be filtered by action, user, method and resource, which speeds up investigations.
  • More context: each entry carries the authentication method used, whether the action came through the API or the Dashboard, and mappings to Cloudflare Ray IDs.
  • Broader capture: alongside create, edit and delete operations, the system records GET requests and failed attempts.

The beta is available only through the API. Cloudflare frames the work as supporting its pledge to CISA's Cybersecurity Commitment by improving customers' ability to gather evidence of intrusions.

How a log entry is produced

Logs are generated for all user requests made through the public API or the Dashboard. GraphQL requests and static assets are among the few exceptions. Each action is routed into the audit logging pipeline close to its source.

Gateway to redaction

The API Gateway handles every user-initiated action and forwards the request and its response data to a Worker called the Audit Log Redactor. To keep latency low, the Gateway streams requests to that Worker over RPC using service bindings, so traffic never traverses a publicly accessible URL.

Field-level sanitization

The redactor Worker looks up the matching API definition in Cloudflare's OpenAPI Schema, which uses JSON Schema to describe the underlying data. Only fields explicitly marked as auditable survive; everything else is redacted. Product teams define their APIs in the schema and choose which fields carry that marking, so the logs show how a resource's value changed without exposing sensitive data. For JSON REST APIs, sanitized request bodies are logged, while GET requests record only the action and the resource accessed.

From the redactor, sanitized data moves through Cloudflare's data pipeline, including Logfwdr, Logreceiver and Buftee buffers. The Ingestor service consumes from those buffers and converts individual requests into audit log records using a fixed schema. Because the API Gateway handles tens of thousands of requests per second, the Ingestor processes requests concurrently.

BLOG-2635 image2

Enrichment, storage and retention

Logs are enriched with user details and authentication information taken from custom response headers. Other context, such as the account name, comes from internal service calls behind a read-through cache: the system checks the cache first and fetches and caches on a miss. Finished records are written to the database in batches; the beta retains 30 days, and retention will extend to 18 months at General Availability.

curl -X PUT https://api.cloudflare.com/client/v4/accounts/<account_id>/alerting/v3/policies/<policy_id> --data-raw '{...'}

General availability roadmap

For GA, planned in the second half of 2025, Cloudflare intends to build a new Dashboard interface, extract additional auditable fields, and enable export through Logpush. Those new fields cover system-initiated actions and user-level actions such as login events. Longer term, the roadmap lists dashboards, trend analysis and alerting.

Accessing the beta

Audit logs can be retrieved with the following endpoint:

/accounts/<account_id>/logs/audit?since=<date>&before=<date>

The beta does not change the Audit Logs UI in the Dashboard. The existing UI and API remain available until GA.