Acme Corp Cloudflare Cloud Workload Security demo

Demo library › Walkthroughs

Guardrails for every pipeline

For platform engineering and DevSecOps. Parameter-level guardrails on AWS and Cloudflare, rolled out in monitor mode, managed as code, and scoped by identity.

~40 minutes · CI pipeline, Cloudflare dashboard, VM terminal, Exfiltration test

Before you start

Chapters

  1. A pipeline tries to make a bucket public A one-line change to acme-infra would make an S3 bucket world-readable. Cloud Workload Security blocks the API calls in the pipeline - with no plugin, no policy file in the repository and no change to the deployment scripts. · ~8 min · CI pipeline
  2. Rules IAM cannot write An unencrypted SQS queue and AdministratorAccess on a deployment role. IAM can say who may call CreateQueue and AttachRolePolicy; Cloud Workload Security decides on what the call actually asks for. · ~6 min · CI pipeline
  3. Guardrails for the Cloudflare API The same proxy and policy model, protecting changes to Cloudflare itself - a public R2 bucket and an unproxied DNS record that would expose an origin - from the pipeline and from the exfiltration test. · ~6 min · CI pipeline
  4. Enforce or monitor Turn Enforce off for one policy and the same requests are allowed - and still recorded as failing their check. How to roll guardrails out without breaking a single pipeline on day one. · ~5 min · Cloudflare dashboard
  5. Change the perimeter as data, manage policy as code Approve a new bucket by editing a JSON document, and watch exactly one exfiltration row change. Then the Rego module behind every policy, the unit tests, and the Terraform that deploys it all. · ~6 min · Cloudflare dashboard
  6. Different guardrails for pipelines and people Every client of the proxy has its own Basic Auth identity. Workloads select requests by identity, so the same request can be allowed for a platform engineer's break-glass shell and blocked for every pipeline. · ~6 min · VM terminal
  7. The evidence - every decision, recorded The proxy records every request it evaluates - the identity, the cloud, the operation, the policy sets that matched and the outcome - as structured JSON you can send anywhere. · ~3 min · Exfiltration test

Afterwards

Leave them with the rollout shape: start every policy with Enforce off, read the decisions for a week, then enforce - and keep the policies in Terraform next to the infrastructure they protect.

Reset: revert infrastructure.json, remove any workload exclusion, and turn Enforce back on everywhere.