SECOPS
Route security-labeled GitLab MRs to the right reviewer pool
When a merge request gains a security label, classify the sensitivity from the diff and assign it to the matching reviewer group.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR label added or changedGitLab
- LogicKeep only security-namespace labels
- ActionFetch MR diff and changed pathsGitLab
- LogicMap label + paths to reviewer pool
- ActionAssign reviewer group and apply routed labelGitLab
- OutputPost routing decision to security channelSlack
What it does
Watches GitLab merge requests for security labels (`security`, `security::crypto`, `security::authn`, `security::pii`). When one appears, it reads the diff, decides which specialist pool should own the review, assigns those reviewers on the MR, and announces the routing in Slack.
When to use it
Use it when your repos carry mixed-sensitivity changes and a single review queue keeps misrouting crypto, auth, or data-handling diffs to generalists. It guarantees the right eyes land on the right code path without a human triaging every MR.
How it works
- 1A GitLab webhook fires on merge request label changes.
- 2A filter passes only MRs whose labels match a security namespace.
- 3The flow pulls the MR changes and maps touched paths and label to a reviewer group (crypto, identity, or data).
- 4It calls GitLab to assign that group as reviewers and apply a `routed` label.
- 5It posts the MR link, chosen pool, and matched files to the security Slack channel so the on-call lead can see coverage.
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.