Data Loss Prevention Software: What 15 Vendors Cost

Updated: November 2026

Fifteen data loss prevention vendors, three published prices. That's what we found checking every vendor's own pricing page on 14 September 2026 and re-checking the three published prices on 10 November 2026, and it's why budgeting for DLP feels like guesswork. Here's what the category costs, what leaks in 2026, how the endpoint DLP vendors compare, and how to cut fifteen options down to two.

TL;DR

• What it is. Data loss prevention software classifies sensitive data, watches the exits (email, USB, browser uploads, cloud sync, AI prompts) and blocks or logs what shouldn't leave.
• What it costs. Three of fifteen vendors publish a price. The rest quote privately.
• What leaks. Accidental loss outnumbers deliberate theft by about two to one.
• Where it leaks now. Generative AI tools, and source code is the most common cargo.
• Endpoint DLP. Microsoft Purview's endpoint DLP covers Windows and macOS and comes with E5 or the $12.00 Purview Suite. Cyberhaven lists Windows, Mac, Linux and VDI, tracks where data came from, and publishes no price.
• What sets the bill. Tuning labour, more than the licence.

Fifteen Vendors, Side by Side

Every row below was checked against the vendor's own site on 14 September 2026, and the three published prices were re-checked on 10 November 2026. Where a price isn't published, the cell says so rather than guessing.

Two names in that table moved recently, which matters if you're reading older comparisons. Code42 was acquired by Mimecast in July 2024 and sells as Mimecast Incydr. LayerX was acquired by Akamai on 2 July 2026 and renamed Akamai Workforce Protector on 5 August 2026. If a roundup still lists either under the old name, check its date before trusting the rest of it.

What DLP Does

You'll also see it called data leakage protection or data leak prevention. Same category, same acronym, and the tools in this guide sell under all three names. Whatever the label, the work is three steps, and the jargon maps onto them cleanly.

First it classifies: it works out which files and which strings are sensitive. That's card numbers, patient records, source code, a contract. Some tools match patterns, some read content, some track where a file came from.

Then it watches the exits. Email, USB sticks, web uploads, cloud sync folders, print, screenshots, and now the prompt box in a chat tool. Each of those is a channel, and no single product covers all of them equally well.

Then it acts. Block the action, warn the user, or log it quietly for review. Running in log-only mode first is standard practice, and skipping that step is how teams end up with an angry sales floor on day two.

If you want the mechanics rather than the theory, this walkthrough builds one policy end to end in Purview: picking sensitive information types, scoping it, setting the action, running it in simulation mode, and what the user sees when it fires.

Who Loses the Data, and How

The picture the category is sold on is a disgruntled employee walking out with a database. The measured one is different.

Verizon's 2026 Data Breach Investigations Report splits insider incidents into two patterns. Plain mistakes (sending to the wrong recipient, misconfiguring a share, losing a device) account for nearly 9% of all breaches, and every one of them involves personal data in 98% of cases. Deliberate misuse of access accounts for just under 4%. Accidents outnumber theft about two to one.

The motive data is the part worth sitting with. Among deliberate insider breaches, Verizon puts convenience at 60%, ahead of financial gain at 33%. Their own example of convenience is an employee emailing company data to a personal account so they can work from home. The person in that example is trying to finish a task.

Which reframes what you're buying. DLP earns its keep on the accidental and the convenient, not on the spy. Proofpoint's 2025 survey of 1,000 security professionals lands in the same place: 58% attribute their most significant data loss to careless employees or contractors, against 32% to malicious insiders. The same research found 1% of users generate 76% of all data loss events, which is a strong argument for finding those users before buying anything. Our insider threats guide covers the warning signs and offboarding controls that sit around DLP.

The Leak Moved to the AI Box

Here's where the category changed in the last two years.

Verizon's DLP telemetry recorded 858,440 policy events in 2025 where the destination was a generative AI tool. Shadow AI is now the third most common non-malicious insider action in that dataset, up fourfold in share year on year. The most common cargo, by a wide margin, is source code.

The account is the problem more than the tool. Verizon found 67% of AI users on corporate devices are logged into non-corporate accounts, which puts the session outside every tenant control you own. Netskope's 2026 report counts 223 genAI policy violations per month at the average organisation and 2,100 in the top quartile, more than double the previous year. Browser telemetry from LayerX in 2025 put generative AI at 32% of all corporate-to-personal data movement, making it the single largest exfiltration channel they measured.

MSPs hit this in the field before the reports landed.

The layered answer in that thread holds up: policy at the org level, tenant DLP with labelling, block app consent, block non-corporate AI at the device, force corporate login where you can, and train for the rest. One reply names the limit plainly, and vendor pitches skip it. You can block downloads, printing, screenshots and copy-paste. You can't block someone photographing the screen and running OCR on their phone.

Worth knowing which half of the problem you have. Harmonic Security's Q2 2025 study of a million prompts found 4.37% of typed prompts carried sensitive content, against 21.86% of uploaded files. People are more careless with attachments than with typing. If AI use is your exposure, our AI governance tools guide sorts the shadow AI discovery and data control products by the job they do.

What It Costs, and Why You Can't Find Out

Three vendors out of fifteen publish a number. That's the state of the category, and it's worth saying out loud because nothing else on the first page of Google for this search will tell you.

Microsoft publishes the clearest ladder, and it's also the one buyers misread. DLP for Exchange, SharePoint and OneDrive is included in Microsoft 365 E3 and in Business Premium, so you may already own part of it. Endpoint DLP and Teams DLP are not: those sit at E5 tier or come through the Purview Suite add-on, renamed from E5 Compliance, at $12.00 per user per month on an annual commitment, on top of an E3 base. E5 is $60.00 per user per month billed yearly on Microsoft's Purview pricing page on 10 November 2026, and E3 is $39.00 after Microsoft's July 2026 price change. If someone tells you DLP comes free with Microsoft 365, ask which channels they mean.

Safetica publishes "starts at" figures of $72, $96 and $144 per user per year across three tiers. Teramind publishes a per-seat monthly price with a five-seat minimum, which makes it one of the few options a ten-person firm can price without a sales call. Their page geolocates, and EUR 30.00 per seat per month for the DLP tier, or EUR 28 on yearly billing, is what we could verify from our location on 10 November 2026.

The other twelve quote privately. Some are quiet about it, some are loud: one has no pricing page at all, and another prints the unit, "$ per user/year", with the figure left blank.

Quote-only isn't automatically a red flag. Enterprise DLP pricing varies with seat count, data volume and which channels you light up. But it does mean a shortlist costs you calendar time before you see a number, so build the shortlist on architecture first and let price break the tie.

The Suites, the Specialists, the AI-Native

Three groups, and they're bought for different reasons.

The suite modules are Microsoft Purview, Proofpoint, Trellix and Symantec. You buy these because you already own the platform and DLP is a line item inside it. The advantage is one console and no new vendor. The catch is coverage that stops at the suite's own edges, which is the recurring complaint about Microsoft DLP on structured data and PDF content.

The specialists are Forcepoint, Fortra, Netwrix Endpoint Protector, Safetica, Teramind and Mimecast Incydr. These are bought when the data problem is the main problem rather than a checkbox: intellectual property on endpoints, device control, insider investigations. Forcepoint and Symantec are the two with a full on-prem deployment if you can't put classification in someone else's cloud. Netwrix Endpoint Protector covers Windows, macOS and Linux with feature parity, which narrows the field fast if you run mixed endpoints.

The AI-native tier is Cyberhaven, Nightfall, Harmonic Security, Akamai Workforce Protector and Netskope. These start from the channel the older products were never built for: the browser, the prompt box, the OAuth grant to an AI agent. Harmonic Security, for one, sells itself as an AI governance and control platform. If the risk in front of you is staff pasting into chat tools, this group deserves a look before the incumbents, and Netskope is the one of them with a multi-tenant MSP path shipping today.

For email, check what your mail security layer already includes before you buy a separate DLP product. We've covered what to look for in email security separately.

Endpoint DLP Vendors

Endpoint DLP is the agent on the laptop that sees the USB copy, the print job, the paste into a browser and the upload to a personal cloud folder. It sits next to the antivirus and EDR agents covered in our endpoint security guide, and buyers search for it as its own category.

In the table above, four vendors sell endpoint DLP as their core product: Teramind, Safetica, Netwrix Endpoint Protector and Mimecast Incydr. Forcepoint, Symantec, Fortra and Trellix pair an endpoint agent with network and discovery coverage, and Cyberhaven pairs one with a browser extension and cloud connectors. Microsoft Purview, Proofpoint, Netskope and Nightfall cover the endpoint as one channel in a wider product. Only Microsoft, Teramind and Safetica publish a price.

Check these before price:

• Operating systems. Microsoft documents Purview endpoint DLP on Windows 10 and 11, Windows Server 2019 and later, and the three latest macOS releases, with no Linux agent. Netwrix Endpoint Protector covers Windows, macOS and Linux, and Cyberhaven lists Windows, Mac, Linux and VDI.
• Channels. Confirm the agent can block, warn or audit each exit you care about. Purview's list runs from USB and network shares through print, clipboard, Bluetooth and RDP to browser uploads and pastes.
• Documented gaps. Microsoft's own documentation notes that a file saved from Word straight to a USB drive, without first being stored on the device, can't be inspected or blocked by endpoint DLP.
• Device control. For removable storage, Microsoft points to Defender for Endpoint device control, which is a separate policy surface from DLP.

If you already run an EDR platform, check what its own modules cover before adding another agent. Our CrowdStrike device control and DLP guide shows how that works for Falcon customers.

Cyberhaven vs Microsoft Purview for Endpoint DLP

The two start from different ends. Microsoft Purview classifies content with sensitive information types, labels, fingerprints and trainable classifiers, then applies policy to the item as it moves. Cyberhaven builds on data lineage: its site says it traces data from its origin through every paste, copy and rewrite, by people and by AI agents, so protection follows the content.

Start with Purview if you're Microsoft-first, already on E5 or on E3 with the suite, and your fleet is Windows and Mac. The endpoint agent comes through Defender, and the policies sit next to the ones already covering Exchange, SharePoint and OneDrive. Look at Cyberhaven when Linux or VDI endpoints are in scope, when the asset is source code or IP that gets copied and rewritten, or when staff paste into AI tools.

Cyberhaven markets itself as filling the gaps Purview leaves, so a trial can run both: keep the Purview policies, put Cyberhaven on a pilot group in log-only mode, and compare what each one catches over the same two weeks. If the comparison on your list is Cyberhaven against Code42, that product now sells as Mimecast Incydr, an endpoint and browser insider risk tool with no published price.

The Bill Nobody Quotes Is Labour

Licences are the visible cost, and the quote stops there.

Ponemon's 2026 insider risk study, across 354 organisations that had a material insider event, puts the total average annual cost of insider incidents at $19.5 million, up from $17.4 million. The negligent share alone is $10.3 million, up 17% year on year. Containment averages 67 days, and the speed matters enormously: incidents closed inside 30 days averaged $14.2 million against $21.9 million for those running past 90.

That's the enterprise end. At the small end, practitioners have been consistent about where the money goes for years.

Five separate people in that thread reach the same conclusion independently: the software is the cheap part, and making the policy engine fit the business is where the hours go. One puts it as a choice rather than a saving. You're either paying in labour or paying for software, and in practice both.

So price the labour before the licence. Someone has to define what sensitive means in your business, write the rules, run them in log-only mode long enough to see the noise, tune the false alarms down, and answer the people whose work just got blocked. Netskope's 2026 data shows 63% of organisations now use DLP to watch movement into personal apps, which is a far broader policy surface than the card-number matching the category started with. A rollout that skips the monitoring phase produces alert fatigue in week one, and an ignored console is worse than no console because it looks like coverage.

Open Source Has No Entry Here

Search for open-source DLP and you'll find lists. Check the repositories and the lists fall apart.

OpenDLP's last release was version 0.5.1 in August 2012. Its GitHub mirror hasn't been pushed to since May 2014, and opendlp.org is now a parked domain listed for sale. MyDLP's repository last saw a commit in February 2014; the project was acquired that year and the free version was withdrawn. Its site is still up, with a blog frozen in 2010 and spam injected into the post bodies. Neither is a 2026 option, and a roundup recommending either hasn't checked.

What does exist is adjacent and partial, which is worth knowing before you budget for a commercial tool you may not need in full.

None of these is a DLP platform. There's no policy engine, no console, no endpoint enforcement. What they do is cover specific slices well: if your actual risk is API keys reaching a public repository, a secrets scanner solves more of it than an enterprise DLP suite would, at no licence cost. Presidio is also worth watching for a governance reason. It moved out of Microsoft's GitHub organisation in 2026 to a community-governed home, with the project stating it won't be owned or operated by a commercial entity.

Compliance That Has a Date

Compliance is what put DLP on the shortlist in both threads above, and the dates get misreported, so here they are precisely.

PCI DSS is live and past its deadline. Version 4.0.1 is the only active version, and the 51 future-dated requirements stopped being best practice and became mandatory on 31 March 2025. Requirement 3.4.2 is the one that reads like a DLP control: technical measures preventing copy or relocation of card data during remote access.

The HIPAA Security Rule update is not law. The proposed rule published in January 2025 would make encryption of patient data mandatory rather than addressable, add multi-factor authentication and require 72-hour incident reporting. It has been moved to long-term actions with an anticipated final action date of July 2027. Treat it as a planning input, and be sceptical of anything claiming HIPAA already requires encryption today.

GDPR hasn't changed, but enforcement has scaled. Articles 32 and 33 still require appropriate technical measures and notification within 72 hours. DLA Piper's January 2026 survey counts EUR 7.1 billion in cumulative fines since 2018 and 443 breach notifications per day across Europe, a 22% annual rise. Three more US state privacy laws took effect on 1 January 2026, in Indiana, Kentucky and Rhode Island, bringing the total to twenty. Rhode Island's has no cure period. If you're mapping controls to frameworks, our cybersecurity frameworks list covers how these map together.

DLP also feeds compliance tracking. Policy matches, overrides and blocked transfers are a record that a control ran, which is the kind of evidence an assessor asks for when checking PCI DSS requirement 3.4.2 or GDPR Article 32. If you track that evidence across frameworks, our compliance automation software comparison covers the tools that collect it.

Which One Fits You

There's no single answer to which DLP tool is best, and any page that gives you one is answering a different question than yours. Start with where your data leaves, not with a feature grid.

Then run it before you sign. Two weeks in log-only mode against real traffic tells you more than any sales call: how many alerts per day, how many are wrong, and how long a policy change takes. If a vendor won't let you test that, you've learned something useful anyway.

Fifteen vendors, three prices, and one category that has quietly moved its centre of gravity from the USB port to the prompt box. If you take one thing into a vendor call, make it the log-only trial: it prices the labour that the quote won't. Next, read our MSP security stack guide for where DLP sits against the rest of the controls.