We've been using this solution for about five, six years now. Our primary use case for Forcepoint Data Loss Prevention is for internal and external compliance, based on banking regulations. It also allows us to ensure that data within the organization is also protected - whether this data is in motion, in use, or at rest. At any point in time, data is always in a three-state situation. Either the data is at rest, which means it's not being used at all, or the data is being used. If someone works on the data, the data is in motion, which means it's moving from one location to another in the network.
Owner at a tech services company with 11-50 employees
Ensures that data within the organization is also protected, whether it's in motion, in use, or at rest but support needs improvement
Pros and Cons
- "Another valuable feature is that it provides integration to things like Cloud Access Security Broker, which provides security around cloud applications."
- "I am really impressed by the interface and management console but the requirements are very high and the response time is too slow."
What is our primary use case?
How has it helped my organization?
This solution improved our organization in the sense that, when we switched over to Office 365, we were able to apply the DLP policies to our Office 365 traffic. It also increased the visibility of what is happening regarding data moving in and out. Thirdly, it offers executive reporting and allows us to see what is going on for executive decision making. Finally, it helps the organization in meeting the compliance requirements of the Central Bank.
What is most valuable?
One of the features I find most valuable is that it is very easy to install. Secondly, it has a very deep reporting mechanism, so it can give you a very detailed report. Then, thirdly, it gives you protection, either at the endpoint, at the network level, and also at the server level. Which also includes the endpoint.
It can also easily be integrated into the data cloud protection and be integrated with cloud protection software or application. This gives us wide visibility and control over our network, for both inbound and outbound data.
Another valuable feature is that it provides integration to things like Cloud Access Security Broker, which provides security around cloud applications.
It also gives integration with SIEM solution, which means that from a SIEM, you'll be able to actually see what is happening around your data. It has some very unique capabilities, such as optical character recognition and custom encryption identification. It has an out of the box library of templates, which enables you to easily set it up and deploy, making it possible for you to identify and stop data theft. You can even integrate it to your email if you want to extend it, where you can actually have DLP around the email and not just around the web and network.
What needs improvement?
The requirements for the implementation is quite heavy. Forcepoint needs to look at how they can reduce the terms of the requirement for implementation. They also need to look at providing training for the end user, to enable them to get on it at speed. Their support also need to improve, because the response to support time is not very fast. Their response time is about 8 to 12 hours, so something needs to be done about that.
Buyer's Guide
Forcepoint Data Loss Prevention
June 2025

Learn what your peers think about Forcepoint Data Loss Prevention. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
860,592 professionals have used our research since 2012.
What do I think about the stability of the solution?
It's reasonably stable. But for every solution there will always be challenges every now and then. Because of the high movement of data from one location to another things become challenging to the client. So it creates a false impression of instability.
We currently have 9,000 users.
What do I think about the scalability of the solution?
The solution is absolutely scalable in the sense that it is important to also have a discussion with customers about having visibility on their growth path.
If you have visibility of their growth path, for instance, a three-year visibility, it means that you can tell the customer that they will grow from 5,000 users to 10,000 users during this time. If the customer agrees, it is important to ensure that you have a solution that can accommodate the 10,000 users and one that has a three-year warranty.
So we can build on that from the beginning by extending the number of licenses. It is therefore very scalable.
How are customer service and support?
I will rate their technical support a seven out of ten because their response time is very slow.
How was the initial setup?
The initial setup was fast and straightforward and we did everything ourselves. Our implementation strategy was to assess the environment, in terms of the infrastructure. Most of the key departments were involved. Then we did a one-day workshop to enable some of the key stakeholders to understand what it's all about. After the workshop, we were able to come up with use cases. After that, we started with the implementation.
After installation and setting up of the database, we started configuring the application, which depended on our internal policies and security requirements.
Then we did some test runs on a few desktops. That went on well so we continued with quite a number of devices until everything was up and running.
What other advice do I have?
My advice would be to make sure that you do a BOT at the beginning before you take any DLP decision, do a BOT. If you're going with Forcepoint, ensure that you have the prices locked down properly, and the user licenses clearly defined.
Then finally, ensure that you sign the right support, you get the right support contract, or support flavor with them. Then you do your sizing properly, especially if you are using Office 365, because Office 365, the mini-environment, has huge performance issues around solutions. So be sure to do your sizing properly.
I rate this solution a seven out of ten. I am really impressed by the interface and management console but the requirements are very high and the response time is too slow.
Disclosure: My company has a business relationship with this vendor other than being a customer. Reseller.

Easy to configure and offers good support
Pros and Cons
- "The ease of configuration was probably one of its biggest selling points."
- "I can't push a report by a certain organizational entity or unit without a lot of work. The reporting could be better."
What is our primary use case?
We use Forcepoint primarily for data loss prevention and detection.
What is most valuable?
The ease of configuration was probably one of its biggest selling points. I know that we took a long time to get it configured properly but it just takes a while. It's a big tool and it does a lot of work.
What needs improvement?
I don't know where they are going as an organization vendor, because my job ends the moment its implemented, so I would go onto other things.
If I were a betting man, though, I would say that they're going to have to find a way of creating what we call multitenancy, because if for example we have a constituency group set of users who don't work for the department and they contract out, then our work with them is highly sensitive. Being able to separate in segment amounts separately from our core would help. We could use better ways of customer or users segmentation capabilities.
For example, if I wanted to push a report by a certain organizational entity or unit, I wouldn't be able to do that without a lot of work. The reporting could be better.
For how long have I used the solution?
We've been using Forcepoint for about 18 months.
What do I think about the stability of the solution?
I think it's going to be hard to beat if they ever decide to replace it. Forcepoint is a pretty good product, we're all pleased with it.
What do I think about the scalability of the solution?
I think it is pretty scalable, at least to the point that we've deployed it to.
We have a workforce of 1,300, of which we have deployed to approximately 800. We also have another set of users who don't work for the department but are contracted out through our agents and sub-agents and they handle the vehicles. We have not deployed to their devices yet, so we have both endpoint and central server data loss prevention technology in place.
We can tell you where anybody went, when they went, how they went, and what they used to get there.
Everybody uses it whether they know it or not, we put out reports monthly on what we call PII information (Personally Identifiable Information). If you know anything about data loss prevention and detection, anytime someone hits a website or even tries to go on, it's logged and captured and we know who went where and what they did, we know what files they looked at and what files they sent, so more power to you. If you want to try something go for it.
We have a CISO, six ISOs (information security officers) or analysts, and over fifteen field service personnel who can work with it. We are pretty broad that way and deep. We have got quite a number of people. Our ISO team itself is comprised of six individuals, a CISO and five analysts.
Security doesn't stop, nor does the pervasiveness of data and its ubiquitous nature. Here at this organization, we don't stop security. We expand it to cover other avenues or channels that come into play. We cover other data structures that are created when another solution takes off. We don't stop simply because it is implemented. It's an ongoing tailored activity we do all the time.
We have six people whose job is just this. Just like technology, we have to stay with it. You can't just throw it up and forget about it. It grows and the rules and policies need to be modified. What people need to remember is that public service is at the whim and fancy of our constituency groups. We report to the legislator, the governor's office, and the citizens of the state. As such, when we put in a system, it has to comply not only with federal regulations but also with state legislators' intent, as well as the governor's office. That is the difference and that is why we take security really personally here.
How are customer service and technical support?
I have heard good things of the support that Forcepoint gives us, so I would have to say that its good.
I don't work with the product directly but I am very well attuned to what they are doing.
Which solution did I use previously and why did I switch?
I don't believe that we had a DLP in place prior to now.
We had security, but two and a half years ago our agency set out to really step up its information security program.
During that time we have made major investments, in process, like data classification, security concerns, risk assessments, risk management, etc. We do this for a living, so it is important to us.
There were products out there for data loss prevention technology, but we didn't believe that they had yet achieved the maturity that they have today, so it would have been premature to pull something in sooner.
The marketing in and of itself is growing, expanding, and changing. Wait until you get ready to do business intelligence and artificial intelligence and try to secure that when it can bypass you on its own. Give learning machines enough instructions and they will figure a way out.
How was the initial setup?
To the best of my knowledge, the initial setup was pretty straightforward. We also had quite a bit of coaching that was done for us by the vendor.
What about the implementation team?
We are still working on deployment. It's going to take two to two and a half years.
It all depends on the political climate that we're in. We are not a normal state agency. We do not have one constituency group, we have multiple constituency groups. We license vehicles, drivers, and professionals, such as lawyers, attorneys, landscapers, architects, etc.
In addition to all of that, we also have a lot of partnerships with law enforcement agencies, courts, lawyers, and insurance companies, so we do a lot of highly technical security programming here.
We don't just throw it out. We are methodical in how we do this.
We didn't use an integrator reseller or consultant for the deployment. We are doing it our selves.
What other advice do I have?
If I were to give some advice, I would say don't try to do it all at once, it won't work. Know that you're going to go. It's different from building line-of-business solutions. Whereas from a line-of-business solution you work from the outside in, with security programs you work from the inside out. You have to get your data governance in place, as well as information security governance. You need to assign who will be responsible. Decide who to send information to if something does happen. All that has to happen before you begin trying to bring in a system.
You have to know your organization well enough to be able to configure a product to make effective use of it. Don't do it unless you have the guts to do it.
I would rate this solution as eight out of ten. There are better solutions, but this was better when it came out. When it did come out, this was the best solution we could find. At the same time, I don't know if I would rate anything else higher than that now, either. Every security tool that we have seen has pluses and minuses, advantages and disadvantages.
Another reason we didn't go with the IQ or any management type of component is the deconstruction and the reconstruction of existing security roles. The biggest problem information security has today is the decoupling and deconstruction of active directory designated accounts which for all practical purposes were based on functionality. One role can have multiple pieces of functionality associated with it, so going to a role-based type of solution muddies the waters.
The vernacular needs to change to be more adaptable if they're gonna put out the configuration types of solutions.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Forcepoint Data Loss Prevention
June 2025

Learn what your peers think about Forcepoint Data Loss Prevention. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
860,592 professionals have used our research since 2012.
I-Security Engineer at Nhq Distribution Ltd
Enables us to keep our legal and confidential documents safe and secure
Pros and Cons
- "We don't require a lot of downtime, but when we do then we are getting proper support with no issue."
- "There is no support for the Bangla (Bengali) language, so we cannot use the Forcepoint technology for Bangla documents."
What is our primary use case?
Our primary use case for this solution is to prevent leakage of enterprise legal data and company confidential documents.
How has it helped my organization?
This solution has been very useful for myself, my colleagues, and our customers by helping us to be more informed about IT concepts and DLP systems. This includes how to deal with enterprise legal data, legal documents, and especially confidential documents. There are IT cultural activities that we learn from this solution.
What is most valuable?
We use several components in this solution, including Endpoint Discovery, CEIT technology, Network Discovery, and NT integration. The most valuable feature in this solution is the support for templates.
What needs improvement?
The user interface for this solution should be improved.
We would like to see OCR from handwritten documents.
There is no support for the Bangla (Bengali) language, so we cannot use the Forcepoint technology for Bangla documents. It does support other languages, but Bangla is not one of them.
Finally, there are some of our customers who want to have a greater resolution when dealing with these technologies.
For how long have I used the solution?
Three to five years.
What do I think about the stability of the solution?
This is a very stable solution. We don't have a lot of downtime, but when we do then we get proper support with no issue.
What do I think about the scalability of the solution?
This is not a product for small enterprise level customers, so most of the time we have to implement Forcepoint DLP for our large customers.
We have four to five customers using this, with several thousand users. They are doing fine, and we are trying to increase usage. The majority of users work in the Information Security department.
How are customer service and technical support?
I have contacted support many times and I am pleased. We get support without any issues, either from India, England, or the USA. If there is a personnel shortage then sometimes it takes longer, but this is not a very big problem, most of the time.
Which solution did I use previously and why did I switch?
Before Forcepoint, we used the McAfee solution for internet security. It had flaws and was lacking in terms of technological advancement.
We still use McAfee ePolicy Orchestrator, but most of the time not for DLP. We use it for endpoint solutions such as malware detection.
How was the initial setup?
The initial setup is not that complex. I would say that it is easy to set up.
The deployment time depends on whether the solution is being integrated with third-party products. If you are installing Forcepoint DLP with Forcepoint proxy and security then it is not a problem but, if you try to integrate it with Google, Cisco, or another third-party then sometimes there are problems and it takes longer.
We use four or five staff for deployment. Post-deployment, you can use just two or three for maintenance. The people are normally from Information Security, although some customers engage their operational team, as well.
What about the implementation team?
Most of the time we handle the deployment for our customers. If something is not working properly, such as not getting the proper data or traffic, then we contact Forcepoint for support.
What's my experience with pricing, setup cost, and licensing?
The pricing and licensing fees could be improved. Some customers feel that the pricing is too high. For instance, Forcepoint doesn't sell less than two hundred and fifty licenses, and some customers find this is problematic.
For my office, it is a one-year license. For most of the customers, licensing is on a three-year basis. Some customers have requested perpetual licenses.
Which other solutions did I evaluate?
Before choosing this solution we evaluated Symantec Data Loss Prevention, but the pricing is too high for most of our customers.
What other advice do I have?
I suggest that before implementing this solution, people should decide which servers they want to keep at which location. This is a good strategy because after implementation and deployment, changing the server position creates problems. Proper homework is necessary before the full deployment.
This is one of the best solutions in the world but without support for our local language, Bangla, I cannot rate it ten out of ten. Overall, I would rate this solution a nine out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer. There are several languages which are detected by the Forcepoint. We expect Bangla as a language in the DLP for data detection/blocking.
We receive a lot of insights from this product
Pros and Cons
- "We receive a lot of insights from this product."
- "We want to be able to do data classification better in the product and reduce false positives, especially on data loss prevention."
What is our primary use case?
We have some financial stuff which is critical for us and don't want to lose that data. This is the primary focus.
We use this product everyday in our organization. We plan to increase our usage this year.
What is most valuable?
We receive a lot of insights from this product.
What needs improvement?
We want to be able to do data classification better in the product and reduce false positives, especially on data loss prevention. Because of this, we are currently looking for another solution for the data classification.
For how long have I used the solution?
Three to five years.
What do I think about the stability of the solution?
The product is stable.
We have one person who is managing the IT for this and doing the maintenance.
What do I think about the scalability of the solution?
The scalability is good. We have about 150 users in our environment with a mix of project managers, a technical team, product managers, sales, accounting, and finance.
How are customer service and technical support?
I have not contacted this solution's technical support.
We use our own technical team, which is very strong.
Which solution did I use previously and why did I switch?
We did not have a solution prior to Forcepoint DLP.
How was the initial setup?
The initial setup was not complex, but not simple.
What's my experience with pricing, setup cost, and licensing?
The pricing and licensing are okay.
What other advice do I have?
Go for it. I would recommend this solution.
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner.
Network Security Specialist at SEFISA
Includes a custom template so you don't need to compute one and was easy to implement
Pros and Cons
- "It has helped us meet CTI requirements. Some employees accidentally shared information and it was able to block that information. That is one of the biggest benefits we have seen from this tool."
- "It should integrate better with email."
What is our primary use case?
Our primary use case is for PCI certification so that the company employees' credit card information doesn't get lost.
How has it helped my organization?
It has helped us meet CTI requirements. Some employees accidentally shared compromising information and it was able to block that information. That is one of the biggest benefits we have seen from this tool.
What is most valuable?
I was working with other customers with the integration of the solution of web protection with DLP and it allows the same agent to bring it and you can protect them and in some cases share web pages or emails. The other thing is that they already have a custom template so you don't have to compute that.
What needs improvement?
Sometimes the agent has trouble communicating with the central management. You need to push a lot of different times to get the policy. Another issue is that the templates are primarily in English and Japanese. They have a lot of Spanish speaking customers and should have more options in Spanish.
It should integrate better with email.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
It's quite stable. Sometimes, when we do an upgrade, we get some trouble but otherwise, it's very stable.
What do I think about the scalability of the solution?
Scalability depends on the operation of the system. We have around fifty users.
How are customer service and technical support?
Their technical support is great. The technicians are very experienced. We don't have any trouble with them.
How was the initial setup?
The initial implementation was easy because we implemented 25 to 50 agents. We didn't have a lot of problems. It was truly easy to implement this product. The deployment took one month. We saw what data we needed to protect and we told the agents.
We required two people for the setup who were IT people. We use it every day.
What about the implementation team?
We implemented it ourselves.
What's my experience with pricing, setup cost, and licensing?
It's not the cheapest solution but it's not the most expensive. It's a good price for a good product.
What other advice do I have?
The first advice is that you should know what data you need to protect then you can implement everything. If you know what you need it'll be a lot easier. You also need good hardware and resources in the computer hardware to be able to implement.
I would rate it an eight out of ten. An eight because you need to have a lot of security experience to properly implement it, in order to know what you need to activate. It's not a plug and play solution.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Consultant at a financial services firm with 10,001+ employees
Provides visibility under a single console and is good with integration
Pros and Cons
- "Has multiple modules and is good with integration."
- "The solution lacks sufficient customization."
What is our primary use case?
We use this solution for data loss prevention, enforcement and monitored file labeling.
How has it helped my organization?
Having visibility under a single console has helped us.
What is most valuable?
The solution has multiple modules and is good with integration. It also enables data classification and monitored file labeling. It's a classic solution.
What needs improvement?
They should support additional customization of SMTP or port customization.
For how long have I used the solution?
We've been using this solution for four years.
What do I think about the stability of the solution?
The stability is very good.
What do I think about the scalability of the solution?
Scalability comes with the license so it's based on your requirements. If you want to increase the number of users you may need to rescale. To do that requires different hardware.
How are customer service and support?
The customer support is far from perfect but it's okay.
How was the initial setup?
Because the solution is deployed on premise, you need to deploy every component based on SQL.
What other advice do I have?
It's important to work your way through the console first because you'll need it to manage the solution. There are multiple components and they all need to be understood.
I rate this solution nine out of 10.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
General Manager - Consulting & AMS at a tech services company with 51-200 employees
Stable and scalable data protection solution with good technical support
Pros and Cons
- "Stable and scalable solution for data protection. It offers good technical support, and has no major installation issues."
- "An area for improvement for Forcepoint Data Loss Prevention is its price. It would be good if they could offer better pricing."
What is our primary use case?
Forcepoint Data Loss Prevention is used for data protection.
What needs improvement?
An area for improvement for Forcepoint Data Loss Prevention is its price. It would be good if they could offer better pricing.
For how long have I used the solution?
I started using Forcepoint Data Loss Prevention three or four years ago.
What do I think about the stability of the solution?
This product is very good. It's very stable.
What do I think about the scalability of the solution?
Forcepoint Data Loss Prevention is scalable.
How are customer service and support?
I'm satisfied with the technical support for this product.
How was the initial setup?
Though I didn't install Forcepoint Data Loss Prevention, there were no major issues with its installation. I had the help of technicians in terms of installing this solution.
What's my experience with pricing, setup cost, and licensing?
Pricing for this solution could be better.
What other advice do I have?
I'm satisfied with Forcepoint Data Loss Prevention in general. It's okay.
We don't have much expectation in the next upgrade of this solution, because we still have no plan for any expansion or growth in our business. Currently, Forcepoint Data Loss Prevention is okay.
We have 100 users of this solution in our company. For deployment and maintenance, we only have IT staff who is in charge, e.g. our IT admin.
We currently don't have plans to increase usage for Forcepoint Data Loss Prevention.
I will definitely recommend this product to people who need a DLP solution.
I'm rating Forcepoint Data Loss Prevention a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Technical Support Engineer at a tech services company with 11-50 employees
Provides ease to users in capturing any data leakages
Pros and Cons
- "The product's configuration phase is easy."
- "The main area of concern is the tool's technical support."
What is our primary use case?
In most of the banks that my company has implemented the tool, we have EMI and credit card information, and they don't want it to go outside the bank. It is also used to prevent company and other financial information.
What is most valuable?
There is a feature in the product that I use the bank with which it is really easy to capture any data leakages.
What needs improvement?
The main area of concern is the tool's technical support. I would suggest the technical engineers reply to users as soon as possible since it usually takes them some time to respond.
For how long have I used the solution?
I have been using Forcepoint Data Loss Prevention for six months. My company functions as a distributor of the tool.
What do I think about the stability of the solution?
I would suggest that the tool's interface or UI needs to be redesigned since it is a bit outdated. The UI needs to be redesigned for the tool's productive working.
What do I think about the scalability of the solution?
For scalability, we just have to deploy the agent, and we can push it through a CCM tool or something like that to manage it, making it an easy process.
How are customer service and support?
I rate the technical support a five or six out of ten.
How would you rate customer service and support?
Neutral
How was the initial setup?
The product's configuration phase is easy.
Less than two people can deploy the solution.
The solution can be deployed in less than an hour.
What was our ROI?
Cost-saving is possible with the tool. The tool has saved time and costs.
What's my experience with pricing, setup cost, and licensing?
I don't actually know about prices. I am the technical support engineer of the tool.
What other advice do I have?
The real-time analytics feature is good, and the tool is really easy to use. I have no concerns regarding the tool.
It is easy to integrate the product with other solutions like SIEM solutions. We have multiple products that we have integrated with Forcepoint Data Loss Prevention, including Microsoft.
I have only used the machine learning part of the tool, which is easy to use.
I recommend the tool to others.
I rate the tool an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer. Reseller

Buyer's Guide
Download our free Forcepoint Data Loss Prevention Report and get advice and tips from experienced pros
sharing their opinions.
Updated: June 2025
Product Categories
Data Loss Prevention (DLP)Popular Comparisons
Zscaler Zero Trust Exchange Platform
Varonis Platform
Microsoft Purview Data Loss Prevention
Check Point Harmony Email & Collaboration
Symantec Data Loss Prevention
Digital Guardian
Mimecast Incydr
Safetica ONE
Netwrix Endpoint Protector
McAfee Total Protection for Data Loss Prevention
Palo Alto Networks Enterprise Data Loss Prevention
Trend Micro Integrated Data Loss Prevention
Netskope Data Loss Prevention (DLP)
GTB Technologies Inspector
Buyer's Guide
Download our free Forcepoint Data Loss Prevention Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Symantec Endpoint vs. McAfee Complete Endpoint Protection: Technical Comparison Between Data Loss Protection Solutions
- When should companies use SSL Inspection?
- What software solution would you recommend to monitor user machines?
- What is the difference between "data protection in transit" vs "data protection at rest"?
- Looking for recommendations and a pros/cons template for software to detect insider threats
- Endpoint DLP for Mac Network
- Best alternatives to Digital Guardian for data protection?
- What is Cognitive Cybersecurity and what is it used for?
- Which solution do you prefer: Symantec DLP, Proofpoint DLP, or Microsoft Purview DLP?
- When evaluating Data Loss Protection, what aspect do you think is the most important to look for?