SECOPS
Escalate likely secret leaks in GitLab MR diffs to PagerDuty
Scans new merge request diffs for credential and key patterns, and when a likely secret is found it auto-labels the MR, blocks merge, and pages the on-call security engineer…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened or commits pushedGitLab
- ActionFetch added lines from MR diffGitLab
- LogicMatch diff against secret patterns
- ActionLabel MR and post failing commit statusGitLab
- ActionOpen PagerDuty incident for on-callPagerDuty
- OutputPost heads-up to security channelSlack
What it does
Inspects every newly opened or updated merge request diff for high-risk patterns: private keys, cloud access tokens, connection strings, and hardcoded passwords. On a hit it applies a `security::secret-leak` label, posts a failing commit status, and triggers a PagerDuty incident so it gets handled immediately rather than queued.
When to use it
Use it as a fast tripwire alongside your full secret scanner when a leaked credential in a diff is an urgent, page-worthy event. It shortens time-to-response for the worst-case leak from hours to seconds.
How it works
- 1A GitLab webhook fires when an MR is opened or its commits change.
- 2The flow fetches the diff and runs the added lines against the secret pattern set.
- 3A filter stops the flow when no candidate secret is found.
- 4On a match it labels the MR and posts a failing `security/no-secrets` commit status to block merge.
- 5It opens a PagerDuty incident with the MR link, file, and matched pattern type, then drops a heads-up in Slack for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.