SECOPS
Arm Sentry release monitoring when sensitive GitLab MRs merge
When a GitLab MR that touched sensitive paths is merged, this tags the corresponding Sentry release as security-relevant and alerts Slack so the team watches that deploy more…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR mergedGitLab
- ActionFetch merged MR changed-file pathsGitLab
- LogicCheck for sensitive paths; exit if none
- ActionTag Sentry release security-sensitive + raise alertingSentry
- OutputPost deploy-watch notice to SlackSlack
What it does
This workflow connects merge events to runtime monitoring. When an MR merges, it checks whether the merged changes included sensitive paths (auth, crypto, payment, infra). If so, it tags the matching Sentry release as `security-sensitive`, raises that release's alert sensitivity, and posts a heads-up to Slack so on-call knows this deploy carries elevated risk and to watch error rates for the next window.
When to use it
Use it when you want post-merge vigilance proportional to change risk — closing the loop between what shipped and how hard you watch it in production, without manually flagging every deploy.
How it works
- 1A GitLab MR merge webhook fires.
- 2The flow fetches the merged MR's changed-file paths.
- 3A filter checks whether any sensitive path was included; if not, it exits.
- 4It tags the corresponding Sentry release as security-sensitive and tightens its alert rule.
- 5It posts a deploy-watch notice with the MR and release to the security Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SentryErrors, performance, releases.
- 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.