SECOPS
Escalate GitLab MRs awaiting security acknowledgment past SLA
On a schedule, finds security-labeled merge requests still waiting on reviewer acknowledgment beyond the SLA window and escalates them to the reviewer's manager pool in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule during business hours
- ActionQuery GitLab for pending security MRsGitLab
- LogicBucket MRs by time-in-queue vs SLA
- ActionSlack reminder to reviewer and manager poolSlack
- ActionPage AppSec on-call for critical breachesPagerDuty
- OutputPost SLA breach summary to SlackSlack
What it does
Acknowledgment gates only work if stalled MRs surface. This sweep runs on a timer, finds security MRs that have been pending reviewer ack longer than the SLA, and escalates by age tier — gentle nudge, manager ping, or on-call page.
When to use it
Use it alongside an acknowledgment gate when you need to guarantee no security review silently rots in the queue and you have tiered SLAs for review turnaround.
How it works
- 1A schedule trigger runs every hour during business hours.
- 2An action queries GitLab for open MRs with a `security::*` label and a `needs-secreview` status.
- 3A logic step computes time-in-queue and buckets each MR into within-SLA, overdue, or critical.
- 4Overdue MRs get a Slack reminder to the assigned reviewer and their manager pool.
- 5Critical MRs trigger a PagerDuty incident for the AppSec on-call.
- 6A summary of all breaches posts 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.
- 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.