SECOPS
Correlate WAF Blocks with Datadog App Errors to Find Noise
Cross-references Cloudflare WAF blocks against Datadog application logs to separate real attacks from blocked-but-benign requests, surfacing rules that are hurting healthy users.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule triggers the correlation run
- ActionFetch Cloudflare WAF block eventsCloudflare
- ActionQuery Datadog for matching traces and session logsDatadog
- LogicClassify each block as benign or hostile from joined evidence
- OutputPost ranked noisy rules to Slack with correlation detailSlack
What it does
Pulls recent Cloudflare WAF blocks and joins them against Datadog APM and log data for the same requests. Blocks tied to authenticated sessions, successful prior calls, or normal user journeys are flagged as probable false positives; blocks matching error storms or scanner patterns are confirmed as legitimate. The output is a ranked list of rules generating benign noise.
When to use it
Use it when you can't tell from Cloudflare alone whether a blocked request was a real customer or an attacker. Datadog's view of what the app actually did gives the missing context to tune confidently.
How it works
- 1A schedule triggers the correlation run periodically.
- 2The workflow fetches Cloudflare WAF block events for the window.
- 3For each block it queries Datadog for matching traces, sessions, and surrounding log activity.
- 4Logic classifies each block as benign or hostile from the joined evidence.
- 5Rules driving benign blocks are ranked and posted to Slack with correlation details for the team to action.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect DatadogMetrics, traces, log search.
- 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.