Acme Corp Cloudflare Cloud Workload Security demo

Demo library › Chapter 8

The evidence - every decision, recorded

ReadyExfiltration test~3 minCloud Workload SecurityProxy logs

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.

The problem

A control that cannot show what it decided does not survive an audit, and does not help an incident responder. "Was anything blocked?" and "what would have been blocked?" both need an answer from the record, not from someone's memory.

Lands with: auditors, SOC teams, and anyone who asks "how would I know?"

Before you start

Run it

The decisions

DoSay
Open the exfiltration test's Proxy decisions page.Every request the proxy evaluated, newest first: when, the outcome, the API call, the cloud service and operation, and the identity it came from.
Expand a denied request.The full record. The policy sets that matched, each policy's result, whether it was enforced - and why the request was refused.
Whybackground, if you are asked

The page reads the proxy's own JSON log from a shared volume; nothing is reformatted on the way. The proxy writes one JSON object per line to standard output, so any log shipper can send it wherever your logs already go - Splunk, Elastic, Datadog - with nothing extra to install.

From the VM

DoSay
On the VM, run sudo cws-lab decisions -f, then run the exfiltration test again.The same record, live, as one line per decision - the shape a SIEM would ingest.

What the audience should see

Where the evidence is

This chapter is the evidence. The raw log is /opt/cloudflare/cws-lab/logs/proxy.log on the VM.

Known limitations

The guide summarises the fields it recognises and always shows the raw event beside them. The proxy's log fields are its own; if a summary column is empty, the raw event has the answer.

Part of: Cloud Workload Security in 20 minutes · Guardrails for every pipeline · The data perimeter