// AI Platform Drift
Cloudflare Cloud Workload Security beta available 19 October 2026
Cloudflare developer changelog · published 2026-10-19 18:45 UTC
WHAT CHANGEDCloudflare released Cloud Workload Security (CWS) in beta on 19 October 2026. CWS applies policy controls to cloud API requests before they reach cloud providers, using request filters and Rego checks. The proxy runs in the customer's environment and requires a Zero Trust subscription (Free plan sufficient).
WHY IT MATTERSTeams can now enforce preventive controls on cloud API calls—for example, blocking requests that would make storage buckets public—before those requests execute. This shifts policy enforcement from detection-after-the-fact to prevention-before-execution.
WHAT TO DOReview the CWS documentation to determine if preventive API controls fit your security model. If you want to pilot it, confirm you have a Zero Trust subscription (Free plan works) and follow the getting-started guide to deploy the proxy and configure a first policy.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Cloud Workload Security - Cloud Workload Security is now available in Beta +https://developers.cloudflare.com/changelog/post/2026-10-19-cloud-workload-security-beta/ +Mon, 19 Oct 2026 00:00:00 GMT + +Cloud Workload Security (CWS) is now available in Beta. Apply policy controls to cloud API requests before they reach your cloud provider. +Define policies with request filters and Rego checks. For example, block requests that would make an R2 bucket public. Use workloads and policy sets to target your cloud environments. +Manage your policies in the Cloudflare dashboard. Run the CWS proxy in your environment and route client requests through it to enforce your policies. +CWS requires a Zero Trust subscription. The Zero Trust Free plan is sufficient. +To configure your first guardrail, follow Get started with Cloud Workload Security.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.5 |
|---|---|
| triage reasoning | New beta feature with subscription requirement and deployment model affects platform capability and cost planning. |
| signals | new feature announcement · beta availability date (2026-10-19) · new subscription requirement stated (Zero Trust subscription) · new API/service capability (policy controls, Rego checks, request filtering) · deployment model change (proxy in customer environment) |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |