SECOPS
Quarterly Vendor Access Evidence Pack Builder
On a quarterly schedule, pulls every third-party service account from Postgres, joins it to last-login and grant data.
How it runs
The automated pipeline, trigger to output.
- TriggerQuarterly schedule fires
- ActionQuery vendor accounts, owners, and last-login from PostgresPostgres
- LogicFlag dormant or unowned accounts as high-risk
- ActionPublish dated evidence pack to ConfluenceConfluence
- OutputPost sign-off link to security channel in SlackSlack
What it does
Builds the audit-ready evidence package security teams need every quarter to prove who has third-party vendor access and whether it is still warranted. It snapshots the current state of all vendor service accounts and publishes a single, dated Confluence page that an approver can review and sign.
When to use it
Run it at the start of each attestation cycle (e.g. first business day of the quarter) when you need a defensible, point-in-time record for SOC 2, ISO 27001, or internal review. Replaces the manual spreadsheet scramble of screenshotting consoles.
How it works
- 1A quarterly schedule fires the workflow.
- 2Queries the access-inventory Postgres tables for all vendor accounts, their owners, grant dates, and last-login timestamps.
- 3Flags accounts that are dormant (no login in 90+ days) or missing an owner so reviewers see risk first.
- 4Formats the joined dataset into an evidence table with a sign-off block.
- 5Publishes a dated, versioned page to the attestation space in Confluence and posts the link to the security channel in Slack for the approver to action.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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.