SECOPS

Secret-Leak Incident Audit Trail Logger

On every secret-leak response event, this workflow writes a normalized, immutable record to Postgres and archives the raw evidence to S3.

CategorySecOps
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerLeak lifecycle event webhookHTTP webhook
  • LogicNormalize event into audit schema
  • ActionArchive raw evidence to S3 with hashAWS S3
  • ActionInsert audit record into PostgresPostgreSQLPostgres
  • OutputReturn record ID and evidence link

What it does

Gives your secret-leak responses a permanent, queryable history. Whenever a leak is detected or remediated, it normalizes the event and stores both the structured record and the raw evidence so auditors and post-mortems have ground truth.

When to use it

Use it alongside your detection and rotation workflows when you need to prove handling for SOC 2, ISO 27001, or breach reporting — and when you want metrics on mean-time-to-revoke across all leaks.

How it works

  1. 1A webhook receives a secret-leak lifecycle event (detected, revoked, or closed) from upstream workflows.
  2. 2A logic step normalizes the payload into a consistent schema: secret type, source, actor, timestamps, and action taken.
  3. 3An action archives the raw event JSON and any scan artifacts to an S3 bucket with a content hash for tamper-evidence.
  4. 4An action inserts the normalized record into a Postgres audit table keyed by incident ID.
  5. 5The workflow outputs the stored record's ID and S3 link for downstream reporting.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect AWS S3Buckets, objects, signed URLs.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  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.