SECOPS
Daily sweep for stale GitLab security reviews past SLA
Each morning, scan open security-labeled merge requests, flag any past their review SLA, and nudge the assigned reviewer pod in Slack with an aging report.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionList open security-labeled MRsGitLab
- LogicCompute age and SLA status per MR
- ActionBump priority on breached Linear issuesLinear
- OutputPost per-pod aging digest to SlackSlack
What it does
Runs a scheduled sweep over all open merge requests carrying a `security::*` label, measures how long each has waited since the label was applied, and surfaces the ones past their pod's SLA. It posts a per-pod aging digest to Slack and re-prioritizes the matching Linear issues so nothing rots silently.
When to use it
Use it when security reviews are landing in the right place but sometimes stall. This catches the slow leak that real-time routing misses, before a stale review becomes a release blocker.
How it works
- 1A daily schedule triggers the sweep each morning.
- 2The flow lists open merge requests with any `security::*` label via the GitLab API.
- 3A logic step computes age per MR and tags each as on-track, due-soon, or breached against the pod SLA.
- 4Breached and due-soon items are grouped by reviewer pod.
- 5It bumps the priority of the linked Linear issues for breached MRs.
- 6It posts a per-pod aging digest to Slack so each lead sees only their queue.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.