SECOPS
Production Script-Tag Drift Monitor
On a schedule, renders your production pages in a real browser, fingerprints every external <script> src and SRI hash.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: every 15 minutes
- ActionRender pages and scrape script srcs + SRI hashesBrowserbase
- ActionFetch approved baseline from Cloudflare KVCloudflare
- LogicDiff current fingerprint vs baseline
- OutputPost script-drift diff to Slack security channelSlack
What it does
Every run, this workflow loads a list of your production URLs in a headless browser, extracts the full set of third-party `<script src=...>` tags plus their `integrity` (SRI) hashes, and compares that fingerprint against the last approved baseline stored in Cloudflare KV. Any added domain, changed src, or mutated SRI hash is flagged as drift and pushed to your security channel before it can ship a compromised payload to users.
When to use it
Run it when you depend on third-party tags (analytics, tag managers, A/B tools, payment widgets) and want early warning of a Magecart-style injection or a silently updated vendor bundle. Ideal for teams without a full CSP rollout who still need supply-chain visibility.
How it works
- 1A schedule fires (e.g. every 15 minutes).
- 2Browserbase renders each monitored URL and scrapes all external script srcs and SRI attributes.
- 3The current fingerprint is compared against the baseline held in Cloudflare KV.
- 4A logic step decides: identical means no-op; any new, removed, or altered entry means drift.
- 5On drift, Slack receives a diff message listing exactly which scripts changed.
Set it up
What you configure once, before turning it on.
- 1Connect BrowserbaseHeadless browsers, sessions, replays.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 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.