SECOPS
Vendor Offboarding Deprovision Attestation
When a vendor offboarding event arrives via webhook, opens a tracked revocation checklist, verifies access is actually removed in Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerVendor offboarding webhook receivedHTTP webhook
- ActionQuery all active accounts and grants for the vendor in PostgresPostgres
- LogicBranch: residual access still active vs. fully revoked
- ActionNotify security owner of status in SlackSlack
- OutputFile timestamped deprovisioning closure evidence to ConfluenceConfluence
What it does
Turns a vendor termination signal into a verified, evidence-backed deprovisioning record. It opens a revocation checklist, confirms the vendor's accounts are genuinely disabled in the access inventory, and stores proof of removal for the attestation file.
When to use it
Use it whenever a third-party contract ends or a vendor is offboarded and you must prove that access was revoked within your SLA window. Closes the common audit gap where access lingers after a relationship ends.
How it works
- 1An offboarding webhook (from your contract or vendor-management system) triggers the workflow with the vendor identifier.
- 2Queries Postgres for every active account, token, and grant tied to that vendor.
- 3Branches: if any access is still active, it escalates; if all access is confirmed disabled, it proceeds to closure.
- 4Notifies the security owner in Slack with the remaining-access list or a clean-confirmation.
- 5Writes a timestamped deprovisioning closure record with the before/after access state to Confluence as attestation evidence.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect ConfluenceSpaces, pages, blueprints.
- 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
Scheduled AWS Access-Key Age Sweep and Forced Rotation
Runs daily to find IAM access keys older than your policy threshold, deactivates the stale key, issues a fresh pair, and notifies the key owner with their replacement instructions.
Correlate Datadog WAF anomaly alert with Cloudflare evidence
When Datadog fires a WAF block-rate anomaly monitor, it pulls the matching Cloudflare firewall events, builds an evidence pack of top rules and ASNs.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
Non-Rotatable Leaked Secret to PagerDuty Escalation
Catches secret-scan hits for credentials that cannot be auto-rotated, gathers blast-radius context, and pages the on-call engineer with a step-by-step manual rotation runbook.
GitHub Secret-Scan Hit to Auto-Revoke and Rotate
When GitHub secret scanning flags a leaked credential in a repo, it auto-classifies the secret type, revokes the live key at the provider, mints a replacement.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.