SECOPS
Vendor Access Owner Re-Attestation Campaign
Drives an agent-led quarterly campaign that asks each system owner to re-attest the vendors with access to their systems, chases non-responders, and rolls completed sign-offs…
How it runs
The automated pipeline, trigger to output.
- TriggerQuarterly campaign schedule fires
- ActionRead vendor-to-owner mapping from PostgresPostgres
- ActionAssign each owner their vendor re-attestation in SlackSlack
- LogicTrack responses and re-ping non-responders until deadline
- OutputCompile completed sign-offs into Confluence attestation reportConfluence
What it does
Runs the full human side of an access review as a managed campaign. An agent assigns each system owner the list of third-party vendors touching their systems, collects an explicit re-attestation decision per vendor, follows up with anyone who stalls, and consolidates the results into one report.
When to use it
Use it when attestation completion rates are the bottleneck — owners forget, replies scatter across DMs, and chasing sign-offs eats the security team's week. This automates the assignment, reminders, and rollup.
How it works
- 1A quarterly schedule launches the campaign.
- 2The agent reads the current vendor-to-owner mapping from Postgres and builds a per-owner attestation task set.
- 3It messages each owner in Slack with their vendor list and a clear approve/flag-for-removal prompt.
- 4Logic tracks responses and re-pings non-responders on a cadence until the deadline.
- 5The agent compiles every decision into a completion-tracked attestation report published to Confluence for the audit record.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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.