SECOPS
Cloudflare DNS Edit Real-Time PagerDuty Escalation
Receives Cloudflare audit-log events via webhook, detects DNS record edits to sensitive domains.
How it runs
The automated pipeline, trigger to output.
- TriggerReceive Cloudflare audit event via webhookHTTP webhook
- LogicKeep only DNS-record actions
- LogicMatch sensitive zone and check actor allowlist
- ActionTrigger PagerDuty incident for on-callPagerDuty
- OutputReturn incident dedupe key
What it does
Listens for Cloudflare audit events in real time and zeroes in on DNS record changes — adds, edits, and deletes. When a DNS edit touches a sensitive zone (your apex domains, MX records, or anything on your protected list) and the actor isn't on the approved DNS-admin allowlist, it triggers a PagerDuty incident so on-call can respond before a hijack or phishing redirect takes hold.
When to use it
DNS changes are high-blast-radius: a single edit can reroute email or hijack your domain. Use this when you need sub-minute alerting on DNS mutations rather than waiting for a periodic batch scan.
How it works
- 1A webhook trigger receives a Cloudflare audit event (delivered via Logpush or your forwarder) as soon as it occurs.
- 2A filter keeps only DNS-record actions and drops everything else.
- 3A logic step matches the affected zone against your sensitive-domain list and checks whether the actor is on the DNS-admin allowlist.
- 4If the zone is sensitive AND the actor is not approved, the workflow opens a PagerDuty incident with severity, actor, record, and old/new values.
- 5The incident key is returned so downstream automations can dedupe.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.