SECOPS
File and track verified push secret leaks as Linear issues with audit log
Detects live secrets in pushes, files one Linear issue per leak with severity and owner, and appends every confirmed exposure to a Postgres audit table for compliance reporting.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub push event receivedGitHub
- ActionRetrieve commit diffsGitHub
- LogicScan, verify, assign severity and owner
- ActionOpen Linear triage issue per leakLinear
- ActionInsert audit row in PostgresPostgres
- OutputLink Linear issue as GitHub commit statusGitHub
What it does
This workflow turns verified secret exposures into trackable remediation work. On each push it scans the diff, confirms which secrets are live, creates a Linear issue per leak with severity, the owning team, and rotation checklist, and records the event in a Postgres audit table so you have a defensible history of every exposure and its resolution.
When to use it
Use it when leaked-secret response needs an owner, a deadline, and an audit trail, not just a transient alert. Ideal for teams under SOC 2 or similar regimes that must prove each exposure was tracked to closure.
How it works
- 1A GitHub push event triggers the workflow.
- 2An action retrieves the commit diffs.
- 3A logic step scans and verifies liveness, attaching severity and the likely owning team based on file path.
- 4A Linear action opens a triage issue per verified leak with the rotation checklist.
- 5A Postgres action inserts an audit row with repo, SHA, severity, and issue link.
- 6The output sets a GitHub commit status linking the Linear issue.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.
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.
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.