SECOPS
Geo-Distributed Login Burst Correlation
Correlates failed-then-successful login bursts arriving from many distinct geographies against one account within a short window, signaling distributed brute-force.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled rolling-window aggregation of login attemptsAxiom
- LogicFlag accounts crossing distinct-geo + failed-to-success thresholds
- ActionOpen PagerDuty incident for the campaignPagerDuty
- ActionFile Linear tracking issue with attempt timelineLinear
- OutputPost Slack summary linking incident and issueSlack
What it does
This workflow looks for the signature of a distributed attack: a single account hit by many login attempts from a scatter of countries in a tight time window, ending in a success. That pattern usually means a credential-stuffing or brute-force campaign behind a proxy network rather than a traveling user.
When to use it
Use it when single-event geo-velocity rules miss slow, distributed attacks. It aggregates across many low-signal events to surface the campaign as a whole, then both pages on-call and files a tracked follow-up.
How it works
- 1A scheduled Axiom query buckets login attempts per account over a rolling window, counting distinct source countries and failure/success transitions.
- 2A logic step flags accounts crossing both a distinct-geography threshold and a failed-to-successful transition.
- 3For flagged accounts, a PagerDuty incident is opened for immediate response.
- 4A Linear issue is created in the security project with the attempt timeline attached for post-incident tracking.
- 5A Slack summary links both the incident and the issue for the responding analyst.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.