SECOPS
Sweep stalled security MR reviews and escalate SLA breaches
Runs on a schedule to find open security-labeled merge requests that have waited past their review SLA, nudges the assigned reviewer pool.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled SLA sweep
- ActionList open security-labeled MRs and agesGitLab
- LogicBucket MRs by SLA tier
- ActionNudge reviewers on soft breachesSlack
- ActionLabel hard-breach MRs in GitLabGitLab
- OutputPage security lead on hard breachesPagerDuty
What it does
Scans all open security-labeled merge requests on a timer and grades each against a tiered SLA: a soft nudge after the first window and a hard escalation past the deadline. Reviewers get reminded in Slack; true breaches page the security lead via PagerDuty so nothing sensitive sits unreviewed for days.
When to use it
Use it when security MRs reliably get opened and labeled but then stall waiting on busy specialists. It replaces manual queue-watching with an automatic SLA enforcer that distinguishes a gentle reminder from a real breach.
How it works
- 1A schedule triggers the sweep every few hours.
- 2The flow lists open MRs carrying a security label and computes how long each has waited since assignment.
- 3A branch buckets each MR into within-SLA, soft-breach, or hard-breach.
- 4Soft-breach MRs get a threaded Slack reminder tagging the assigned reviewer pool.
- 5Hard-breach MRs open a PagerDuty incident for the security lead and get a `sla-breach` label applied in GitLab for reporting.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.