SECOPS
Cloudflare Scraper Fingerprint and Evidence-Pack Builder
When scraping is suspected, profiles the path and user-agent fingerprint of the offending ASNs in Axiom, archives a full evidence pack to S3.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator triggers with suspect ASNs
- ActionProfile path and user-agent fingerprintsAxiom
- LogicAssemble structured evidence pack
- ActionArchive evidence to S3AWS S3
- OutputFile GitHub security issue with artifact linkGitHub
What it does
This workflow builds the forensic case rather than just reacting. Triggered manually when an operator suspects content scraping, it profiles the suspect ASNs in Axiom, extracting their request-path patterns, user-agent fingerprints, and crawl cadence. It assembles a structured evidence pack, archives the raw logs and summary to S3 for retention, and opens a GitHub security issue that links the artifact so engineering can decide on a permanent countermeasure.
When to use it
Reach for this when you need durable, shareable proof of an abuse pattern, for an abuse report to a hosting provider, a legal hold, or an engineering decision. It is the deep-dive companion to the real-time blockers.
How it works
- 1An operator manually triggers the workflow with the suspect ASNs.
- 2Axiom profiles each ASN's request paths, user agents, and timing cadence.
- 3A logic step assembles the structured evidence pack and summary.
- 4The raw logs and summary are archived to an S3 bucket for retention.
- 5A GitHub security issue is filed with the findings and a link to the S3 artifact.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.