SECOPS
Daily Chaser for Unrotated Exposed Secrets
Runs each morning to find open secret-rotation issues that owners have not acknowledged or closed, nudges the owners in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled weekday-morning sweep
- ActionQuery open secret-rotation issuesGitHub
- LogicBucket issues by age vs SLA
- ActionNudge owners on overdue acksSlack
- ActionPage on-call for past-deadline issuesPagerDuty
- OutputPost backlog rollup to secops channelSlack
What it does
Keeps the rotation backlog from rotting. It sweeps every still-open exposed-secret issue daily, ranks them by age against your rotation SLA, and applies graduated pressure so nothing sits exposed indefinitely.
When to use it
Use it alongside an intake workflow when rotation tickets pile up and owners go quiet. This is the recurring enforcement layer that turns SLAs into action.
How it works
- 1A scheduled trigger runs every weekday morning.
- 2The flow queries GitHub for all open issues labeled `secret-rotation` across the tracked repos.
- 3A logic step buckets each issue: fresh, overdue for an ack nudge, or past the hard rotation deadline.
- 4For overdue-but-not-critical issues it posts a per-owner Slack reminder threaded to the original alert.
- 5For issues past the hard deadline it raises a PagerDuty incident naming the owner and issue age.
- 6It posts a single rollup to the secops channel summarizing counts by bucket so leadership sees the trend.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.