SECOPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab push webhookGitLab
- LogicScan diff for secret patterns
- ActionRevoke exposed credential at providerHTTP webhook
- ActionOpen tracked remediation issue with purge stepsGitLab
- OutputAlert committer and team in SlackSlack
What it does
Intercepts secrets the moment they land in GitLab. When a push event carries a detected credential, the workflow revokes the live key, files a tracked remediation issue covering history rewriting, and pings the committer directly so they fix it while the change is fresh.
When to use it
Choose this if your source of truth is GitLab rather than GitHub and you want detection tied to the push itself. It is especially useful for catching the case where a secret was committed and merged before anyone noticed, because it also drives the history-purge follow-up.
How it works
- 1A GitLab push webhook fires on every commit to watched branches.
- 2A logic step scans the diff for secret patterns and branches only when a real credential is found.
- 3An action calls the issuing provider to revoke the exposed key.
- 4A GitLab issue is opened, assigned to the committer, with explicit `git filter-repo` purge steps and the revoked key reference.
- 5A Slack alert names the committer, repo, and commit so the team has immediate visibility.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 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.
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.
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.