SECOPS
On-Demand Script Forensic Snapshot
Triggered manually during an incident, captures a full inventory of every script, its source, body hash, and SRI on the affected pages, archives it to S3.
How it runs
The automated pipeline, trigger to output.
- TriggerManual trigger with target URLs
- ActionCapture full script inventory, bodies, hashes, SRIBrowserbase
- ActionArchive snapshot to S3 with timestamped keyAWS S3
- OutputFile Linear incident ticket linking the evidenceLinear
What it does
When you suspect a compromised or rogue third-party script, this workflow captures court-quality evidence fast. It renders the affected production pages, enumerates every loaded script with its full src, response body, SHA-256 of the body, declared SRI, and load chain, then writes the immutable snapshot to S3 with a timestamped key. It opens a Linear incident ticket linking the archived artifact so responders have a frozen point-in-time record before anything changes.
When to use it
Fire it the moment a supply-chain incident is suspected, after a drift alert, an abuse report, or a customer complaint about unexpected behavior. Capturing the snapshot early preserves the malicious payload before the attacker or a vendor rotates it away.
How it works
- 1An operator triggers the run manually with the target URLs.
- 2Browserbase loads each page and captures every script src, body, SHA-256, and SRI plus the load chain.
- 3The assembled snapshot is archived to S3 under a timestamped, immutable key.
- 4A Linear ticket is created in the security project with the page list and a link to the S3 evidence bundle.
Set it up
What you configure once, before turning it on.
- 1Connect BrowserbaseHeadless browsers, sessions, replays.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
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.