SECOPS
GitHub Vendor Collaborator Attestation Reviewer
Audits external collaborators and outside contractors across GitHub org repos, cross-checks them against an approved-vendor list in Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerReviewer starts the access-review run
- ActionList outside collaborators and permissions from GitHub orgGitHub
- ActionMatch collaborators against approved-vendor table in PostgresPostgres
- LogicBranch sanctioned vs. unrecognized or over-privileged grants
- OutputSend repo owners keep/revoke decisions in SlackSlack
What it does
Reviews every external collaborator and outside-contributor with access to your GitHub organization's repositories, then verifies each one against the approved third-party vendor register. It produces a per-reviewer decision request so access either gets re-attested or revoked, leaving a clean trail.
When to use it
Use it during the access-review window when source-code access by vendors must be justified line by line. Ideal when contractors rotate frequently and stale collaborator grants accumulate between audits.
How it works
- 1A manual run kicks off the review for the current cycle.
- 2Pulls all outside collaborators and their repo permission levels from the GitHub org.
- 3Looks up each collaborator in the approved-vendor table in Postgres to determine whether the grant is sanctioned.
- 4Branches: sanctioned grants are logged as attested; unrecognized or over-privileged grants are marked for action.
- 5Sends each repo owner a Slack message listing their flagged collaborators with keep/revoke buttons, capturing the decision back to the audit log.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.