SECOPS

Log every GitLab security acknowledgment to an immutable audit trail

Captures each security review acknowledgment, override, and merge-gate event from GitLab and writes a structured, append-only record to BigQuery.

CategorySecOps
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitLab security MR event (approve, label, merge)GitLabGitLab
  • LogicNormalize into common audit record
  • ActionAppend record to BigQuery audit tableGoogle BigQueryBigQuery
  • LogicCheck merged MRs for missing acknowledgment
  • OutputSlack alert on gate bypassSlack

What it does

Compliance needs a durable record of who acknowledged which security MR and when — plus an alarm when someone merges around the gate. This workflow normalizes acknowledgment and merge events into one schema, appends them to BigQuery, and flags any merge that lacks a matching ack.

When to use it

Use it when auditors or SOC 2 / ISO controls require evidence that security review acknowledgments happened before merge, and you want bypasses detected rather than discovered later.

How it works

  1. 1A GitLab webhook fires on security-relevant MR events (approval added, label changed, merged).
  2. 2A logic step normalizes the event into a common audit record (MR id, actor, label, action, timestamp).
  3. 3An action appends the record to a BigQuery audit table.
  4. 4A logic step checks whether a merged MR has a prior acknowledgment row.
  5. 5If a merge has no recorded ack, an action posts a high-priority bypass alert to the security Slack channel naming the actor and MR.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.