Acme Corp Cloudflare Cloud Workload Security demo

Demo library › Walkthroughs

Cloud Workload Security in 20 minutes

The exfiltration test, a pipeline stopped mid-deploy on AWS and on Cloudflare, and the record of every decision. For any audience.

~23 minutes · Exfiltration test, CI pipeline

Before you start

Chapters

  1. Stop data exfiltration through cloud APIs Five writes of "company secrets" to an attacker's S3, SQS, SNS, Kinesis and DynamoDB. Straight to AWS they all land; through Cloud Workload Security every one is blocked, and the company's own bucket still works. · ~6 min · Exfiltration test
  2. 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
  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. 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

Close on the architecture, from The lab: one proxy in the path of the pipeline and the workloads, its configuration loaded from Cloudflare, and nothing in the repository or the deployment scripts that a developer could remove to get round it.

Then reset for the next audience: revert any change still in infrastructure.json, and Empty the attacker's account.