Acme Corp Cloudflare Cloud Workload Security demo

Acme Corp, behind Cloud Workload Security

A fictional company with a CI/CD pipeline that deploys to AWS and to Cloudflare, a workload that can leak data through cloud APIs, and Cloudflare Cloud Workload Security in the path of every API call they make - all in one lab, with no AWS account.

Cloud Workload Security (CWS) puts a policy check between your workloads and the cloud APIs they call. A proxy you run in your own environment loads its policies from Cloudflare, reads each API request - the operation and its parameters, not just the hostname - and blocks the risky ones before they reach the cloud provider. It is Cloudflare's productisation of Kivera, acquired in 2024.

The quickest ways in

Cloud Workload Security in 20 minutes - the exfiltration test, a pipeline stopped mid-deploy on AWS and Cloudflare, and the evidence.

Setup first, though: it has this lab's credentials and a two-minute pre-flight check.

What is in the lab

What it isReached as
Exfiltration testThe Kivera data exfiltration test, rebuilt for Cloudflare - straight to AWS or through CWS, one click each
Git serverGitLab and its runner, with the acme/acme-infra repository and its pipeline. GitLab on a VM with 8 GB or more, Gitea on a smaller one.
CWS proxycws-proxy from Cloudflare's package repository, on the lab networkhttp://cws-proxy:8080, inside the lab
AWSThe AWS Emulator, answering for the real *.amazonaws.com hostnamesInside the lab only
CloudflareThis lab's own account: the CWS deployment and policies, R2, DNS, the tunnel and Accessdash.cloudflare.com
This guideScripts for every demo, and this lab's credentials

This guide is public. The exfiltration test and the git server are behind Cloudflare Access: sign in with a one-time PIN.

How it fits together

A Git repository feeds a runner, whose job containers send every cloud API call through the CWS proxy. The proxy loads its deployment from the Cloudflare account and forwards allowed calls to the AWS Emulator or the Cloudflare API. The exfiltration test can go through the proxy or straight to AWS.
Every cloud API call in the lab goes through the CWS proxy - or, for the "before" half of each demo, around it.

8 demos

Stop exfiltration

Five writes of company data to an attacker's S3, SQS, SNS, Kinesis and DynamoDB. All land; then none do. Chapter 1

Guard the pipeline

A one-line change would make a bucket public, leave a queue unencrypted, or hand out admin. Chapters 2 and 3

Guard Cloudflare too

A public R2 bucket and an exposed origin, blocked by the same proxy. Chapter 4

Run it for real

Monitor before enforcing, policy as data and code, identities, and the record of every decision. Chapters 5 to 8

Before you run anything

  1. Setup - sign-in details, the pre-flight check, and what to do if something is not ready.
  2. The lab - how AWS is emulated, the resources, and how the proxy gets into the path.
  3. Policies - every guardrail, its filter, and its Rego.