Skip to content

Cloudflare

Identity & SaaS audit logs. Account audit-log events from your Cloudflare dashboard.

Status: available now - you connect this yourself

This source is live in the console. Create the read-only credential below, connect it on its card in Integrate -> Sources, and your dedicated instance starts collecting.

What SheerSight reads

SheerSight reads your account audit logs: API tokens created, member and 2FA-enforcement changes, firewall-rule deletions, Logpush and DNS tampering, and actor bursts.

That feed powers detections such as an API token created, an access-control change, a security control weakened, integrity tampering, and an actor activity burst.

It is read-only.

What you'll need

  • A Cloudflare user with permission to create an account-owned API token.
  • Your Account ID (shown on the dashboard overview, right-hand sidebar).
  • Your dedicated instance enrolled.

Create the read-only credential

Use a scoped API token, not the legacy Global API Key.

  1. Select the account you want to monitor in the Cloudflare dashboard.
  2. Open Manage Account -> Account API Tokens -> Create a token.
  3. Name the token SheerSight audit collector. Under Permission policies, choose Start from scratch -> Custom.
  4. Add one permission: Account Settings -> Read (shown on the review screen as Account Settings Read).
  5. Choose a Token expiration, such as 90 days. Plan to replace the credential in SheerSight before it expires.
  6. Review the token, click Create token, and copy its value directly into SheerSight.
  7. Copy this account's Account ID from the dashboard overview page.

No separate account-scope step

This account-owned token flow uses the account selected in step 1. It does not ask you to select Account Resources separately. The review screen shows the account the token belongs to. Profile-level user API tokens use a different flow and may show resource selectors.

Least privilege

Cloudflare's audit-log API documentation lists Account Settings Read as an accepted permission. This permission allows account settings reads; it is not a dedicated audit-only permission. It grants no write access. Do not choose Read all resources, Write all resources, or Full account and zone access.

Connect it in SheerSight

In the console, open Integrate -> Sources -> Cloudflare and fill in:

Field Value
Account ID The account ID from step 7.
API token The token from step 6.

Enter an authenticator code if prompted, then press Connect. Paste the token only into the encrypted API token field, never into chat or a support ticket.

Newer audit-logs API

The installed collector uses the established account audit-log API. Cloudflare also offers a version 2 API with different fields and pagination. If collection fails, share the raw error with support so we can check API compatibility.

Verify

  1. The relayed credentials entry moves from pending to applied.
  2. The Cloudflare source badge moves from not connected to live.
  3. Account audit events begin appearing, and matching detections start firing.

Troubleshooting

  • Badge stays not connected. Re-check that the token has Account Settings Read, has not expired, and belongs to the account whose ID you entered.
  • Credentials applied but source shows an error. Credential application confirms that your instance received the values. Check the source badge and raw error separately to confirm collection is working.
  • HTTP 400: Bad Request on first connection. A confirmed collector bug sends a start date of 1 January 1970, outside Cloudflare's 18-month audit retention. Support can confirm the provider's error and arrange a collector update. Creating another token or granting write access does not fix this request error.
  • Authorized but no data. Confirm the Account ID matches the account shown on the token's review screen, and consider the newer-API note above.

What SheerSight can and cannot do

SheerSight uses the read-only token to collect account audit logs. It cannot change DNS, firewall, or security settings, manage members, or take any action. It only reads audit events.