SECOPS
Route Risky GitLab MRs to the Right Security Reviewer Queue
When a GitLab merge request is opened or updated, scans the diff for security-sensitive paths and assigns a risk label.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened or updatedGitLab
- ActionFetch MR changed-file listGitLab
- LogicMatch paths to risk ruleset, pick severity label
- ActionApply label + assign reviewer groupGitLab
- OutputPost routed MR card to reviewer Slack channelSlack
What it does
Classifies every incoming merge request by the security risk of its changed files and hands it to the reviewer queue that owns that risk class, so auth, crypto, and infra changes never sit in a generic backlog.
When to use it
Run this when your security review is a bottleneck and MRs touching sensitive code (auth middleware, IAM policy, dependency manifests) need a specialist rather than whoever grabs the queue first.
How it works
- 1A GitLab webhook fires on merge request `open` and `update` events.
- 2The flow pulls the MR's changed-file list and matches paths against a risk ruleset (e.g. `**/auth/**`, `*.tf`, `package*.json`).
- 3A branch picks the highest-severity match and selects a label: `sec/critical`, `sec/high`, or `sec/standard`.
- 4It applies the label and assigns the corresponding reviewer group to the MR via the GitLab API.
- 5It posts a summary card to that group's Slack channel with the MR link, matched paths, and assigned reviewer.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.