SECOPS
CSP Script-Violation Report Pager
Ingests Content-Security-Policy violation reports via webhook, filters for unexpected script-src blocks.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives CSP violation reportsHTTP webhook
- LogicFilter to script-src violations, drop known noise
- LogicGroup by blocked URI and affected page
- OutputPage on-call via PagerDuty with violation detailPagerDuty
What it does
This workflow turns your browsers into a distributed supply-chain sensor. It receives `report-to`/`report-uri` CSP violation payloads at a webhook, isolates `script-src` and `script-src-elem` violations, and drops known-noise sources (browser extensions, localhost). A genuine block, meaning a real production page tried to load a script your policy does not allow, indicates either a misconfigured deploy or an active injection, so it pages on-call immediately.
When to use it
Use it once you have a CSP deployed in enforce or report-only mode and want to catch the moment an unexpected third-party script appears in the wild, reported by actual visitor browsers rather than a periodic crawl.
How it works
- 1An HTTP webhook receives batched CSP violation reports.
- 2A logic step filters to script-related directives and discards extension and noise origins.
- 3Remaining violations are grouped by blocked URI and effective page.
- 4If any qualifying script violation remains, PagerDuty is triggered with the blocked URI, page, and report count for on-call triage.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.