SECOPS
Third-Party Vendor Allowlist Reconciliation
Weekly, crawls production pages for every distinct script-loading domain and reconciles the live set against an approved-vendor registry in Airtable.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: weekly
- ActionCrawl pages, collect all script-loading originsBrowserbase
- ActionRead approved-vendor registryAirtable
- LogicReconcile live origins vs registry, find gaps
- OutputPost unapproved and stale vendor lists to SlackSlack
What it does
This workflow keeps your approved third-party vendor list honest. It renders production pages, collects every distinct origin that loads JavaScript (including nested loads chained by tag managers), and compares that live inventory against an Airtable registry of approved vendors. It surfaces two gaps: domains observed live but not in the registry (shadow vendors), and registry entries no longer seen on any page (stale approvals to retire).
When to use it
Use it for periodic supply-chain governance and audit evidence, especially under PCI DSS 6.4.3 / 11.6.1 which require an inventory of page scripts and a justification for each. It produces a clean approved-versus-actual reconciliation you can hand to auditors.
How it works
- 1A weekly schedule fires.
- 2Browserbase renders each monitored page and captures every script-loading origin, including dynamically injected ones.
- 3The approved-vendor registry is read from Airtable.
- 4A logic step computes the set differences: unapproved live domains and stale registry rows.
- 5A summary of both gap lists is posted to Slack for the security owner to act on.
Set it up
What you configure once, before turning it on.
- 1Connect BrowserbaseHeadless browsers, sessions, replays.
- 2Connect AirtableBases, tables, views, automations.
- 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.