SECOPS
Daily Org-Wide Secret Sweep with Slack Digest
Each morning it sweeps every public repo in your GitHub org for exposed secrets and posts a single ranked Slack digest of new findings with file links and severity.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionList all public org reposGitHub
- ActionScan repo history for secretsGitHub
- LogicDedupe and score new findings
- OutputPost ranked digest to SlackSlack
What it does
This workflow runs a scheduled, org-wide audit of all your public repositories, finds newly exposed secrets since the last run, ranks them by severity, and delivers one consolidated Slack digest instead of a flood of per-commit alerts.
When to use it
Use it when you want daily situational awareness of leak exposure across many repos without paging anyone. It complements real-time rotation by catching secrets in older history, forks, and repos that real-time hooks miss.
How it works
- 1A daily schedule fires the sweep.
- 2An action lists every public repo in the GitHub org.
- 3Each repo's recent history is scanned for credential patterns.
- 4A logic step deduplicates against findings already reported and scores each new hit by credential type and blast radius.
- 5If there are no new findings the run ends quietly.
- 6Otherwise an output posts a ranked Slack digest with repo, file, line, and severity for triage.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.