SECOPS
Cloudflare Login-Endpoint Credential-Stuffing Detector
Watches login and auth endpoints in Cloudflare logs for sudden failed-attempt spikes, throttles the attacking IPs via rate-limit rule.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 5 minutes
- ActionQuery failed-auth events by IPAxiom
- LogicConfirm credential-stuffing spike
- ActionApply Cloudflare rate-limit ruleCloudflare
- ActionPage on-call via PagerDutyPagerDuty
- OutputOpen Slack incident threadSlack
What it does
This workflow narrows the anomaly hunt to your authentication surface. It watches Cloudflare logs for the specific signature of credential stuffing: a burst of POSTs to login or token endpoints with an elevated 401/403 ratio from a concentrated set of IPs. When that pattern crosses threshold, it applies a tightened Cloudflare rate-limit rule to the source range, pages the on-call security engineer, and spins up a Slack thread to coordinate response.
When to use it
Use this when account takeover is the threat you care about most and a delayed response is unacceptable. It is tuned for auth endpoints specifically, so it reacts faster and with fewer false positives than a generic traffic monitor.
How it works
- 1A 5-minute schedule triggers the check.
- 2Axiom queries failed-auth event counts grouped by IP over the last 15 minutes.
- 3A logic step confirms the spike exceeds the credential-stuffing threshold for one or more sources.
- 4Cloudflare applies a strict rate-limit rule to the offending IP ranges.
- 5PagerDuty pages the on-call engineer with the incident summary.
- 6A Slack thread is opened with the attacking IPs and counts for live coordination.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
GitLab Push Secret Detection to Block and History Purge
On a GitLab push that contains a detected secret, it revokes the exposed credential, opens a tracking issue with git-history purge instructions.
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.