SECOPS
GitLab Blocked Secret Notify and Coach
When GitLab secret detection blocks a merge request, this workflow logs the event, emails the commit author with safe-removal steps.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab secret-detection block webhookGitLab
- LogicRecord finding and start ack timer
- ActionEmail author safe-removal stepsGmail
- LogicCheck acknowledgment after window
- OutputEscalate unresolved cases to SlackSlack
What it does
Handles the high-volume, lower-severity case: a developer almost committed a secret and GitLab caught it. It coaches the author privately first and only escalates to the team if the issue lingers, keeping noise off the security channel.
When to use it
Use it when GitLab secret detection is enabled and most hits are developer mistakes caught pre-merge. Ideal for teams that want education and gentle escalation rather than a PagerDuty page for every blocked MR.
How it works
- 1A GitLab pipeline/secret-detection webhook fires when an MR is blocked for a detected secret.
- 2A logic step records the author, project, and finding, and starts an acknowledgment timer.
- 3An action emails the author with the exact file, line, and instructions to remove the secret from history and rotate it.
- 4A logic step waits and checks whether the author acknowledged or fixed the MR.
- 5If unresolved past the window, the workflow outputs a Slack escalation tagging the author's lead.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect GmailRead, draft, send, label.
- 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.