SECOPS
Route GitLab MR security labels to the right reviewer pool
When a merge request gains a security label, this looks up the matching reviewer group and assigns those reviewers to the MR.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR updated with a security:: labelGitLab
- LogicMap label to reviewer pool
- ActionAssign pool reviewers and add needs-secreview labelGitLab
- OutputPost assignment to Slack triage channelSlack
What it does
GitLab merge requests get tagged with labels like `security::crypto`, `security::authz`, or `security::data-handling`, but assigning the right specialist reviewer is usually manual and slow. This workflow watches for security labels and instantly routes the MR to the correct reviewer pool, then announces it in Slack.
When to use it
Use it when your AppSec team owns several distinct review domains and you want labels — not tribal knowledge — to decide who looks at a change. Ideal for teams running a `security::*` scoped label taxonomy in GitLab.
How it works
- 1A GitLab webhook fires when an MR is updated and a `security::*` label is present.
- 2A logic step maps the specific label to a reviewer pool (a lookup table of label to GitLab usernames).
- 3An action assigns those reviewers to the MR via the GitLab API and adds a `needs-secreview` label.
- 4A Slack message posts the MR title, author, label, and assigned pool to the security triage channel.
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.