SECOPS
Cloudflare Off-Hours Config Change Detector
Polls the Cloudflare audit log on a schedule, flags configuration changes made outside business hours, and opens a Linear ticket for secops to review each suspicious change.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes, pull new Cloudflare audit-log entriesCloudflare
- LogicKeep only configuration-mutation actions
- LogicDrop changes inside business hours
- ActionOpen a Linear ticket for each off-hours changeLinear
- OutputReturn filed ticket IDs
What it does
Watches your Cloudflare account audit log for configuration changes (WAF rules, zone settings, page rules, access policies) that happen outside your defined business hours. Any off-hours change is treated as anomalous and gets a Linear ticket assigned to the secops review queue, complete with the actor, the action, and the timestamp.
When to use it
Use this when most legitimate Cloudflare changes happen during the workday and you want a fast, low-noise way to catch the ones that don't — whether that's an attacker with stolen credentials, a contractor working unusual hours, or an automated script nobody approved.
How it works
- 1A schedule fires every 15 minutes and pulls new audit-log entries from Cloudflare since the last run.
- 2A filter keeps only entries whose action type is a configuration mutation (create/update/delete on settings).
- 3A logic step checks each entry's timestamp against your business-hours window (e.g. Mon-Fri 8am-7pm in your timezone) and discards in-hours changes.
- 4For each remaining off-hours change, the workflow creates a Linear issue in the secops project with the actor email, resource, and a deep link back to the audit entry.
- 5The new ticket IDs are emitted as the run output so you can confirm what was filed.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect LinearIssues, projects, cycles, triage.
- 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.