IT OPS

Quarterly Cloudflare Access Audit Evidence Pack

Once a quarter, snapshots every Cloudflare Access grant, reconciles it against the HR roster, and builds a dated reconciliation report in Confluence with totals, orphan list…

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerQuarterly schedule (period close)
  • ActionSnapshot all Cloudflare Access apps and grantsCloudflareCloudflare
  • ActionRead HR roster snapshot from PostgresPostgreSQLPostgres
  • LogicReconcile grants; compute matched/orphaned/remediated
  • ActionStore immutable audit-period snapshot in PostgresPostgreSQLPostgres
  • OutputPublish reconciliation evidence page to ConfluenceConfluenceConfluence

What it does

Generates the access-review evidence auditors ask for. It captures a point-in-time snapshot of all Cloudflare Access grants, reconciles each against the HR roster, and publishes a structured Confluence page documenting matched grants, orphaned grants, and their remediation state.

When to use it

Use this at the close of each audit period when you need durable, shareable proof that access was reviewed and reconciled against employment status. Replaces the manual spreadsheet that someone usually scrambles to assemble before a SOC 2 or ISO assessment.

How it works

  1. 1A quarterly schedule triggers the workflow.
  2. 2It pulls the complete set of Cloudflare Access apps and grants.
  3. 3It reads the HR roster snapshot from Postgres, including terminated-this-quarter records.
  4. 4A logic step reconciles grants, computing matched, orphaned, and newly-remediated counts.
  5. 5It writes the immutable snapshot to Postgres tagged with the audit period.
  6. 6It publishes a dated reconciliation page to Confluence with summary tables and the full orphan list ready for auditor review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect ConfluenceSpaces, pages, blueprints.
  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.