Cloudflare DLP's new Data Classification lets you sort sensitive data your way!
Hey everyone, it's Shii-chan! Today I found a Cloudflare security update that's quiet but really handy in practice.
Cloudflare Changelog
developers.cloudflare.com
What was announced?
On Cloudflare's Changelog, Data Loss Prevention (DLP) got a new capability called Data Classification. It lets you classify sensitive data, label it, and protect it with consistent rules.
The story so far
DLP was originally built to detect sensitive info — like credit card numbers or national ID numbers — before it leaks out. But the data an organization handles doesn't always fit fixed patterns. Defining your own "we treat this as sensitive" criteria and reusing it cleanly used to be a bit of a chore.
What changes
With Data Classification, you can define your own sensitivity schemas and levels, and label your data accordingly. And since a classification you build once is reusable, your team stays consistent about "what is sensitive, and how important is it." That's a nice win for administrators.
Dive Deep
Here's the concrete stuff I could pull from the source:
- Define custom labels, including sensitivity schemas and levels
- Create data tag groups and individual tags
- Build reusable "data classes" by combining detection entries, other classes, sensitivity levels, and tags
- Start from Cloudflare-managed templates
- Apply classifications in custom DLP profiles to assess content severity
The detailed setup steps are in the Data Classification docs, so check there when you actually get hands-on.
Wrap-up
- Cloudflare's DLP now includes Data Classification
- Define custom labels with sensitivity schemas, levels, and tags
- Reusable "data classes" combine detection entries and tags
- Start from Cloudflare-managed templates
- Apply it in custom DLP profiles for consistent protection
I think this really lands for security folks and admins handling data loss prevention in Cloudflare One!
