SECOPS

Daily privileged-access change digest to Slack

Each morning it compiles the prior day's permission and access changes from Cloudflare and Datadog audit logs into a single digest — role grants, token lifecycle.

CategorySecOps
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionPull Cloudflare access-change audit entriesCloudflareCloudflare
  • ActionPull Datadog access-change audit eventsDatadogDatadog
  • LogicMerge and group changes by actor and type
  • OutputPost privileged-access digest to SlackSlack

What it does

Once a day it sweeps the last 24 hours of audit data for everything that changed someone's access — new members, role escalations, API tokens created or revoked, SSO changes — and delivers one tidy digest so the team can eyeball who gained or lost privilege overnight.

When to use it

Use it as a standing access-governance ritual. Instead of reactive alerting, this gives a calm daily summary that satisfies least-privilege review habits and creates a lightweight paper trail of access drift over time.

How it works

  1. 1A schedule fires once each morning for the prior 24-hour window.
  2. 2The flow pulls Cloudflare audit entries filtered to membership, token, and role events.
  3. 3It pulls Datadog audit events filtered to the same access-change categories.
  4. 4A merge step normalizes both sources into a single list grouped by actor and change type.
  5. 5The digest is formatted with counts, notable escalations highlighted, and a 'no changes' fallback.
  6. 6The digest posts to a Slack access-review channel to start the day.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect DatadogMetrics, traces, log search.
  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.