SECOPS
Daily WAF bypass audit against Honeycomb origin hits
Once a day, reconciles Cloudflare WAF allow decisions on sensitive paths against Honeycomb origin traces to find requests that should have been blocked but reached the backend.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionPull Cloudflare WAF decisions for sensitive pathsCloudflare
- ActionPull Honeycomb origin traces for those pathsHoneycomb
- LogicFind bad-signature requests that reached origin
- OutputOpen or update GitHub issue with bypass listGitHub
What it does
Each day it audits whether the WAF is actually catching what it should. It pulls Cloudflare events for sensitive paths and compares them against Honeycomb origin traces to find requests matching known-bad signatures that were allowed through. The mismatches are likely rule gaps or misconfigured exceptions, and they get filed for the team to fix.
When to use it
Use it as a recurring assurance check on your WAF ruleset rather than a real-time alert. It answers "is anything getting past us that shouldn't be?" on a steady cadence.
How it works
- 1A daily schedule fires.
- 2An action step pulls Cloudflare WAF decisions for the configured sensitive paths over the past day.
- 3An action step pulls Honeycomb origin traces for those same paths.
- 4A logic step finds requests that matched bad signatures yet reached origin, the suspected bypasses.
- 5The output step opens or updates a GitHub issue listing each suspected bypass with the trace link and suggested rule fix.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect HoneycombDistributed traces and queries.
- 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.