SECOPS
Escalate critical-severity GitLab MRs to on-call AppSec
When a merge request gets a critical security label, page the on-call AppSec engineer via PagerDuty and open a high-priority Linear issue so a human responds within minutes.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR labeledGitLab
- LogicFilter for critical severity only
- ActionPage on-call AppSec via PagerDutyPagerDuty
- ActionOpen urgent Linear security-incident issueLinear
- ActionPost incident links to war-room SlackSlack
- OutputApply review::blocking label on MRGitLab
What it does
Detects merge requests tagged with a critical security severity (`security::critical` or `severity::p0`) and treats them as incidents. It pages the on-call AppSec rotation through PagerDuty, opens an urgent Linear issue, and drops a thread in the security war-room channel.
When to use it
Use it for the small set of MRs that touch auth, secrets handling, or payment paths where a slow review is a real risk. Routine security labels should use the standard reviewer-pod routing instead.
How it works
- 1A GitLab webhook fires on merge request label changes.
- 2A filter keeps only critical-severity security labels and discards the rest.
- 3The flow triggers a PagerDuty incident on the AppSec escalation policy with the MR title and author.
- 4It opens an urgent Linear issue tagged `security-incident` and links the MR.
- 5It posts to the security war-room Slack channel with the PagerDuty incident and Linear links.
- 6It labels the MR `review::blocking` in GitLab so it cannot merge until acknowledged.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.