SECOPS
Log GitLab security-review exceptions to a Postgres audit table
Captures every time a security-labeled GitLab MR is merged without a completed security approval and records the exception in Postgres for audit.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR mergedGitLab
- LogicKeep only security-labeled MRs
- LogicCheck for missing security approval
- ActionInsert exception row into Postgres audit tablePostgres
- OutputAlert security lead in SlackSlack
What it does
Detects merge requests carrying a security label that get merged without the required security approval, and writes a durable exception record to a Postgres audit table. Each row captures the MR, author, merger, labels, and timestamp so you have a clean trail for compliance reviews.
When to use it
Use it when policy says security-labeled changes need sign-off but reality sometimes overrides that, and you need defensible evidence of every exception rather than scrolling GitLab history during an audit.
How it works
- 1A GitLab webhook fires on MR merge events.
- 2A filter keeps only MRs that carried a `security::` label.
- 3A branch checks whether a security-team approval was recorded before merge.
- 4If approval is missing, the flow inserts an exception row into the Postgres `security_review_exceptions` table with full context.
- 5A Slack alert notifies the security lead with the MR link and who merged it, so the exception is reviewed while it's fresh.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.