SECOPS
Scheduled control-screenshot evidence capture to S3 and Notion
On a recurring audit cadence, logs into each control dashboard, captures timestamped screenshots, archives them in S3, and records a dated evidence row in a Notion audit log.
How it runs
The automated pipeline, trigger to output.
- TriggerAudit cadence schedule fires
- ActionCapture control dashboard screenshotBrowserbase
- ActionUpload screenshot to versioned S3 keyAWS S3
- ActionAppend dated evidence row to Notion logNotion
- OutputPost capture summary to SlackSlack
What it does
Runs on your audit cadence (monthly or quarterly), opens each control system's dashboard in a headless browser, captures a full-page screenshot, uploads the image to a versioned S3 bucket with a date-stamped key, and appends a row to a Notion evidence database recording the control ID, capture time, and the S3 link.
When to use it
When you maintain a SOC 2, ISO 27001, or HIPAA control set and an auditor expects periodic proof that controls (MFA settings, backup config, logging dashboards) were in place at known points in time. It replaces the manual quarterly screenshot scramble.
How it works
- 1A schedule fires on the first of the audit period.
- 2For each control in the list, Browserbase opens the dashboard URL and captures a full-page screenshot.
- 3The image is uploaded to S3 under `evidence/<control-id>/<date>.png`.
- 4A new row is written to the Notion evidence database with control ID, timestamp, and the S3 object URL.
- 5A Slack message summarizes how many controls were captured and links the Notion log.
Set it up
What you configure once, before turning it on.
- 1Connect BrowserbaseHeadless browsers, sessions, replays.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.