SECOPS
Nightly Git History Credential Sweep
Each night this workflow scans tracked repositories for high-entropy strings and known key patterns.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionRun entropy + pattern scan over reposShell
- LogicDedupe against known fingerprints
- ActionFile Linear issue per new findingLinear
- OutputSend severity-ranked digest to SlackSlack
What it does
Proactively hunts for secrets already sitting in git history — the ones that never tripped a real-time scanner. It runs a deterministic sweep across your repos and turns each confirmed hit into trackable remediation work.
When to use it
Use it after onboarding new repos, post-migration, or as a standing hygiene job when you suspect older commits contain keys that predate push protection. Good for teams that want a daily backlog of leak debt rather than ad-hoc panic.
How it works
- 1A scheduled trigger kicks off the sweep every night.
- 2A shell action runs a pattern + entropy scanner across the cloned repositories and emits structured findings.
- 3A logic step deduplicates against previously-seen fingerprints so the same old leak isn't refiled nightly.
- 4For each new finding, an action creates a Linear issue with the file path, commit, and suggested rotation steps.
- 5The workflow outputs a severity-ranked digest to Slack so the team sees the night's net-new exposure at a glance.
Set it up
What you configure once, before turning it on.
- 1Connect ShellRun sandboxed commands inside the workspace.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.