SECOPS
Brute-Force and Credential-Stuffing Burst Pager
Scans Axiom auth logs every few minutes for failed-login bursts against single accounts or single source IPs, classifies the pattern as brute-force or credential stuffing.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: query Axiom every few minutesAxiom
- ActionAggregate failed logins by account and by IP
- LogicClassify burst and test against thresholds
- ActionBuild attacker summary for crossings
- OutputPage on-call via PagerDutyPagerDuty
- OutputMirror heads-up to SlackSlack
What it does
Identifies password-guessing campaigns in near real time. It distinguishes a vertical attack (many passwords against one account) from a horizontal one (one IP spraying many accounts) and escalates only the genuinely abusive bursts so on-call isn't drowned in noise.
When to use it
Use when login endpoints are exposed to the internet and you want automated paging for active guessing, not a daily report. Ideal if you already centralize auth failures in Axiom.
How it works
- 1A schedule fires every few minutes and queries Axiom for failed-login events in the trailing window.
- 2The flow aggregates failures two ways: by target account and by source IP/subnet.
- 3A logic step classifies each cluster — brute-force vs. credential stuffing — and checks failure count and velocity against tunable thresholds.
- 4Bursts below threshold are logged and dropped; only crossings continue.
- 5For a qualifying cluster it builds a summary: attacker IPs, targeted accounts, success/failure ratio, and time-to-lockout estimate.
- 6It triggers a PagerDuty incident with that summary and severity, and mirrors a heads-up to Slack for situational awareness.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.