SECOPS
Impossible-Travel Login Detection with PagerDuty Escalation
Streams authentication events from Axiom, computes geo-velocity between consecutive logins per user.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled pull of recent login eventsAxiom
- LogicPair consecutive logins per user and compute distance + elapsed time
- LogicFilter to events exceeding ~900 km/h implied speed
- ActionOpen PagerDuty incident with coordinates and speedPagerDuty
- OutputMirror the incident to the secops Slack channelSlack
What it does
This workflow watches your authentication log stream and catches "impossible travel" — the same user account signing in from two locations so far apart, so quickly, that no real human could have traveled between them. When detected, it raises a PagerDuty incident with the account, both geo-coordinates, and the computed travel speed so on-call can act in minutes.
When to use it
Run this when you need always-on detection of credential compromise across a distributed workforce. It is ideal for teams that already ship auth logs to Axiom and want a deterministic, low-false-positive trigger that wakes someone up only for genuinely anomalous sessions.
How it works
- 1A scheduled Axiom query pulls the last window of successful login events, ordered by user and timestamp.
- 2The pipeline pairs each login with the prior login for the same user and computes the great-circle distance and elapsed time between them.
- 3A logic step divides distance by time to get implied speed; events under ~900 km/h pass and are dropped.
- 4For events that exceed the threshold, a PagerDuty incident is opened with severity tied to the speed.
- 5A Slack message is posted to the secops channel mirroring the incident for visibility.
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.