SECOPS
Scan GitLab MR diffs for leaked secrets and page on a hit
Runs a secret-detection scan against each GitLab MR diff; on a verified hit it labels the MR as blocked, comments the offending lines.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened or updatedGitLab
- ActionFetch MR diff (added lines)GitLab
- LogicRun secret detection + verifier; exit if clean
- ActionLabel MR sec::secret-leak + comment locationGitLab
- OutputOpen PagerDuty incident for rotationPagerDuty
What it does
This workflow treats every merge request as a potential secret-leak surface. When an MR opens or updates, it runs a secret-scanning pass over the added lines of the diff. If a credential pattern is found and passes the verifier (entropy plus known-format checks), it labels the MR `sec::secret-leak`, comments the exact file and line, and pages on-call so the secret can be rotated immediately.
When to use it
Use it as a last-line defense when pre-commit hooks are optional or inconsistently installed, and you need server-side enforcement plus a real-time page for confirmed leaks rather than a daily report.
How it works
- 1A GitLab MR webhook fires on open or update.
- 2The flow fetches the MR diff (added lines only).
- 3A scan step runs detection rules and a verifier to drop false positives.
- 4If no verified secret is found, it exits.
- 5On a hit it applies the `sec::secret-leak` label and comments the offending location on the MR.
- 6It triggers a PagerDuty incident tagged with the repo and MR for rotation.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.