SECOPS
Block GitLab merge requests that introduce live secrets
Scans the diff of each GitLab merge request, verifies any detected secret is active.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab merge request eventGitLab
- ActionFetch MR added lines from GitLab APIGitLab
- LogicDetect candidate secrets in additions
- LogicVerify liveness and decide pass or fail
- ActionComment inline and set pipeline status failedGitLab
- OutputBlock merge until recheck passesGitLab
What it does
This workflow runs as a gate on GitLab merge requests. It scans only the MR's changed lines for credentials, verifies whether each detection is a live secret, and if so fails the merge check and posts an inline comment pinpointing the file and line. Clean MRs pass untouched.
When to use it
Use it as a hard preventive control: stop leaked secrets at the merge boundary instead of cleaning them up after they land. Best for teams that enforce required status checks and want a blocking gate rather than an after-the-fact alert.
How it works
- 1A GitLab merge request event triggers the workflow.
- 2An action fetches the MR changes (added lines only) from the GitLab API.
- 3A scan step detects candidate secrets in the additions.
- 4A logic branch verifies liveness and decides pass or fail.
- 5On a verified leak, an action posts an inline MR comment at the offending line and sets the pipeline status to failed.
- 6The output blocks merge until the secret is removed and the recheck passes.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.