SECOPS
Vendor Privilege Drift Detector
Compares the current quarter's vendor access snapshot in Postgres against last quarter's attested baseline, isolates every added or escalated grant.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled drift check fires
- ActionRead current access state and attested baseline from PostgresPostgres
- LogicDiff snapshots and filter to additions and escalations
- ActionOpen a GitHub issue per drift item with before/after detailGitHub
- OutputPost consolidated drift summary to SlackSlack
What it does
Detects privilege drift between attestation cycles. It diffs the live vendor access inventory against the previously signed-off baseline and surfaces only the deltas — new accounts, widened scopes, and role escalations that appeared without an approved change.
When to use it
Run it mid-cycle or just before sign-off to catch access that crept in since the last attestation. It lets reviewers focus on what changed instead of re-reading the entire grant list, and creates a tracked record for each anomaly.
How it works
- 1A schedule (e.g. monthly) triggers the drift check.
- 2Reads the current vendor access state and the last attested baseline from Postgres.
- 3Computes the diff and filters to additions and privilege escalations only, discarding unchanged grants.
- 4For each drift item, opens a GitHub issue in the security backlog with the before/after detail and an owner.
- 5Posts a consolidated drift summary to the security channel in Slack so the team triages the new exposure immediately.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.