---
title: "Programmable DLP turns web gateways into software that must be audited"
description: "Cloudflare's programmable Gateway and DLP integration adds flexibility to egress controls. Custom actions now demand code review, coverage testing and safe failure modes."
url: "https://devencelab.com/insights/2026/10/15/programmable-dlp-turns-web-gateways-into-software-that-must"
date: "2026-10-15"
section: "Insights"
tag: "AI Security"
author: "Devence Lab"
reading_time: "3 min read"
site: "Devence Lab"
license: "Readable and quotable with attribution to the canonical URL."
---

# Programmable DLP turns web gateways into software that must be audited

Cloudflare's programmable Gateway and DLP integration adds flexibility to egress controls. Custom actions now demand code review, coverage testing and safe failure modes.

Cloudflare announced a more programmable Secure Web Gateway and Data Loss Prevention stack on 15 October 2026, extending the platform through integration with Cloudflare Workers. The appeal is straightforward: security teams can express more organisation-specific behaviour than a fixed set of predefined web controls. The cost is less obvious. Custom policy logic becomes software that needs ownership, testing and change management.

This matters as employees and automated tools exchange business data with cloud applications and AI services. A rule that allows an approved destination may still permit a dangerous upload, while an aggressive content inspection policy can block legitimate work. More programmability helps encode context, but it can also create inconsistent enforcement paths.

## A gateway rule is executable security policy

Cloudflare positions Gateway as the traffic-control layer and DLP as the component that detects sensitive content. Its documentation describes DLP profiles and HTTP policies using allow, block or log decisions. Worker-based extensions add a software-engineering discipline to those configurations. Security owners should treat every custom action as a versioned change with a defined purpose and rollback.

Before deploying conditional behaviour, document which user identities, application destinations, device signals and data classifications are inputs. Specify whether a lookup failure results in denial, monitoring or normal access, and test those modes deliberately. External data services used for decisions can become a new availability and integrity dependency.

> A programmable gateway is only as dependable as the code, evidence and fallback rules that decide what leaves the organisation.

## Inspection coverage must be measured, not assumed

Cloudflare's DLP documentation states that inspecting HTTPS request bodies generally requires Gateway HTTP filtering and TLS decryption. Traffic excluded by Do Not Inspect rules or other bypass paths is outside that scanning path. DLP on AI Gateway can separately inspect configured AI requests and responses without relying on the same HTTP filtering setup.

That distinction is operationally important. A deployment covering browsers does not automatically cover every service-to-service agent request, local application or outbound integration. Inventory the actual egress routes used by sanctioned AI tools. For each route, record whether DLP scans prompts, files or other content, what metadata remains visible and which exceptions were approved.

## Make policy updates observable and reversible

Build a test corpus with secrets, personal identifiers, harmless near-matches and approved business documents. Exercise custom actions against malformed context, unavailable backends and high-volume uploads. Compare expected and actual decisions by policy version, not just the final count of blocked requests.

Keep sensitive payload logging minimal and access-controlled. Cloudflare provides passive detection and profile testing to help tune DLP, but those features do not establish that a bespoke Worker behaves correctly. Require code review, scoped deployment credentials and staged rollouts. Preserve a simple fallback policy so a defective custom action does not silently open an exfiltration route. The new integration broadens control options; engineering discipline determines whether it strengthens or weakens data protection.

Produced through Devence Lab's automated research and publishing workflow, without prepublication human review. Devence Lab retains editorial responsibility. Sources are linked; report factual errors to contact@devencelab.com.

## Sources

- [A fully programmable secure web gateway](https://blog.cloudflare.com/programmable-gateway-dlp/) - Cloudflare Blog
- [Data loss prevention](https://developers.cloudflare.com/cloudflare-one/data-loss-prevention/) - Cloudflare Developer Documentation
- [Scan HTTP traffic](https://developers.cloudflare.com/cloudflare-one/data-loss-prevention/dlp-policies/) - Cloudflare Developer Documentation