SECOPS
Nightly Repo Secret Sweep with Severity Triage to PagerDuty
Runs a scheduled deep secret scan across your GitHub org each night, classifies findings by how dangerous the credential is, and pages on-call via PagerDuty only for live.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly cron schedule fires
- ActionClone org repos and run secret scannerShell
- LogicTriage findings by severity and liveness
- ActionOpen PagerDuty incident for high-severity live secretsPagerDuty
- OutputAppend all findings to Postgres audit tablePostgres
What it does
Proactively hunts for committed secrets instead of waiting for a provider alert. A nightly scan walks the org's repos, and every finding is triaged by severity: a live production database URL pages on-call immediately, while a low-risk or already-revoked match is filed for review. This keeps the signal-to-noise ratio sane so PagerDuty stays trustworthy.
When to use it
Use it when you have many repos and want a daily safety net beyond GitHub's native scanning, with strict control over what actually wakes someone up at 3am.
How it works
- 1A nightly cron schedule starts the sweep.
- 2A shell step runs the secret scanner against the org's checked-out repos and emits findings as JSON.
- 3A logic step scores each finding by credential type and whether it validates as live.
- 4High-severity live secrets trigger a PagerDuty incident with the repo, file, and line.
- 5All findings, regardless of severity, are appended to a Postgres audit table for the morning review queue.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.