Cloudflare DLP adds custom match validation
Cloudflare Workers can validate DLP matches. Review account access, sensitive context and failure behaviour before enabling the feature.
On 15 October 2026 Cloudflare announced DLP match validation through Workers. DLP addresses possible data loss. An organization's own logic can refine confidence or reject a match. Checked on 16 October, this is an external Cloudflare One capability, not a new AffiliateCore fraud detector.
Who may benefit
An editorial example is an advertiser team handling internal reports where a similar character sequence could be a harmless reference or sensitive information. A rule should distinguish these cases on verified grounds rather than treating every match as a leak. This is a possible use, not a client result.
The documentation makes access account-specific: the control appears when the feature is available. The Worker runs in the same account. Its input includes matched text with surrounding context, so access, processing and logging need separate review. Do not use real customer exports in an experiment.
What to do now
Assign a rule owner. Prepare a synthetic set of expected sensitive values, similar harmless strings and boundary cases. Compare decisions with manual labels first, then separately test a handler error or timeout. Document the intended failure behaviour and a return to the previous configuration.
Measure missed dangerous cases and false alarms separately. Fewer alerts alone do not prove better protection. Full costs include development, validation, maintenance and applicable service charges. Expand only after the data owner and security team have reviewed the evidence.
Check geography and contractual eligibility for your organization; the announcement does not promise access in every country. The AffiliateCore advertiser login belongs to our partner platform. Cloudflare DLP configuration is separate and does not establish the quality or payment status of affiliate conversions.