SECOPS
Leaked Cloudflare API Token Revoke and Reissue
On detection of an exposed Cloudflare API token, this workflow immediately revokes the live token, issues a scoped replacement, stores it securely.
How it runs
The automated pipeline, trigger to output.
- TriggerExposure report received via webhookHTTP webhook
- LogicVerify token is active and ours
- ActionRevoke compromised tokenCloudflare
- ActionIssue scoped replacement tokenCloudflare
- ActionRecord rotation in audit logPostgres
- OutputNotify service owner with new token refSlack
What it does
Contains the blast radius of a leaked Cloudflare API token by revoking it the moment exposure is confirmed, minting a fresh token with the same scopes, and handing the replacement to the owning service so the rotation closes the same hour.
When to use it
Use it when a Cloudflare token is found in logs, a public repo, or a paste, and you need automatic containment rather than a manual revoke-and-rebuild that leaves a window open. Best for orgs managing many edge tokens.
How it works
- 1An HTTP webhook receives the exposure report with the token ID and the source that flagged it.
- 2The flow checks the token is still active and confirms it belongs to your Cloudflare account before acting.
- 3It revokes the compromised token via the Cloudflare API to immediately cut access.
- 4It creates a replacement token carrying the original's permission scopes.
- 5It writes the new token to the secrets store and records the rotation in Postgres for audit.
- 6It DMs the service owner in Slack with the new token reference and the revoked token's old ID.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Scheduled AWS Access-Key Age Sweep and Forced Rotation
Runs daily to find IAM access keys older than your policy threshold, deactivates the stale key, issues a fresh pair, and notifies the key owner with their replacement instructions.
Correlate Datadog WAF anomaly alert with Cloudflare evidence
When Datadog fires a WAF block-rate anomaly monitor, it pulls the matching Cloudflare firewall events, builds an evidence pack of top rules and ASNs.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
Non-Rotatable Leaked Secret to PagerDuty Escalation
Catches secret-scan hits for credentials that cannot be auto-rotated, gathers blast-radius context, and pages the on-call engineer with a step-by-step manual rotation runbook.
GitHub Secret-Scan Hit to Auto-Revoke and Rotate
When GitHub secret scanning flags a leaked credential in a repo, it auto-classifies the secret type, revokes the live key at the provider, mints a replacement.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.