SECOPS
Secret-Rotation Audit Ledger to Warehouse
When an owner closes a secret-rotation issue, it captures who rotated what and how fast, writes the record to a warehouse table for compliance.
How it runs
The automated pipeline, trigger to output.
- TriggerSecret-rotation issue closed in GitHubGitHub
- ActionRead issue timeline for owner + timestampsGitHub
- LogicCompute time-to-rotate vs SLA
- ActionAppend audit row to warehouseBigQuery
- OutputPost rotation metric and breaches to SlackSlack
What it does
Builds the audit trail auditors actually ask for. Every completed rotation becomes a durable, queryable record linking the original exposure to the owner who fixed it and the elapsed time, so you can prove SLA performance on demand.
When to use it
Use it when compliance or security leadership needs evidence that exposed secrets get rotated within policy, and you want time-to-rotate trends rather than scattered closed tickets.
How it works
- 1A trigger fires when a GitHub issue labeled `secret-rotation` is closed.
- 2The flow reads the issue timeline to extract the open timestamp, acknowledging owner, and close time.
- 3A logic step computes time-to-acknowledge and time-to-rotate against the policy SLA and flags breaches.
- 4It appends a structured row to the rotation-audit table in the data warehouse via BigQuery.
- 5It posts the per-rotation metric to the secops channel, calling out any SLA breach.
- 6The accumulated table backs compliance reporting and trend dashboards.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 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.