SECOPS
Block GitLab merge requests that introduce secrets, with inline review
On every GitLab merge request, scans the changes for embedded credentials and, if any are found, fails the pipeline status and leaves an inline review comment pinpointing each…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab merge request eventGitLab
- ActionPull MR diff and scan changed hunksGitLab
- LogicBranch: clean vs leak detected
- ActionSet failing commit status to block mergeGitLab
- OutputPost inline review comments on flagged linesGitLab
What it does
Intercepts GitLab merge requests and scans the proposed changes for hardcoded secrets before they can merge. When it finds one, it sets a failing commit status to block the merge and posts an inline comment on the exact offending lines so the author can fix it without guessing.
When to use it
Use it to enforce a no-secrets-in-main policy as a required merge gate. It is the right fit when you want prevention at review time rather than alerting after the fact, and when you want developers to get precise, actionable feedback inside the MR they are already looking at.
How it works
- 1A GitLab merge request event triggers the flow.
- 2The flow pulls the MR diff and runs credential and entropy detection across the changed hunks.
- 3A logic branch decides clean versus leak-detected.
- 4On a clean result it sets a passing status. On a leak it sets a failing commit status to block the merge.
- 5It posts an inline review comment on each flagged line describing the credential type and how to remediate.
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.