SECOPS
Nightly git history scan with batched secret rotation
Runs a scheduled deep scan of repository history for committed secrets, rotates each confirmed finding in Cloudflare.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionRun git-history secret scan via shellShell
- LogicFilter out allowlisted and already-rotated hits
- ActionRotate each confirmed secret in CloudflareCloudflare
- ActionOpen consolidated PagerDuty incidentPagerDuty
- OutputPost nightly summary to SlackSlack
What it does
On a nightly schedule, deep-scans the full commit history of your repositories for secrets that earlier push-time checks missed, rotates every confirmed credential in Cloudflare, and rolls all findings into a single consolidated incident so responders see the whole night's exposure in one place.
When to use it
Use this as a backstop for secrets that predate your scanning, were force-pushed, or hid in old branches. Running it on a schedule catches historical leaks that event triggers never see, and batching avoids alert storms.
How it works
- 1A nightly schedule triggers the scan job.
- 2A shell step runs a history scanner across all branches and emits a findings list.
- 3A filter drops already-rotated and allowlisted findings to leave only live exposures.
- 4For each remaining finding, Cloudflare rotates the corresponding secret value.
- 5A single PagerDuty incident is created summarizing every rotation with commit references.
- 6The same summary is posted to Slack for the security team's morning review.
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 CloudflareWorkers, Pages, R2, KV — the edge stack.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Scheduled AWS Access-Key Age Sweep and Forced Rotation
Runs daily to find IAM access keys older than your policy threshold, deactivates the stale key, issues a fresh pair, and notifies the key owner with their replacement instructions.
Correlate Datadog WAF anomaly alert with Cloudflare evidence
When Datadog fires a WAF block-rate anomaly monitor, it pulls the matching Cloudflare firewall events, builds an evidence pack of top rules and ASNs.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
Non-Rotatable Leaked Secret to PagerDuty Escalation
Catches secret-scan hits for credentials that cannot be auto-rotated, gathers blast-radius context, and pages the on-call engineer with a step-by-step manual rotation runbook.
GitHub Secret-Scan Hit to Auto-Revoke and Rotate
When GitHub secret scanning flags a leaked credential in a repo, it auto-classifies the secret type, revokes the live key at the provider, mints a replacement.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.