Forcepoint Data Loss Prevention Reviews

Most of the time we leave it at the first party level because of its ease of use and they do not need too much knowledge to use it. We offer it within the SMB market because it's not complex like other DLP solutions on the market, like McAfee. It is good for retail and the SMB, but I think they must have a COM-LAN with a stand-up LAN.

The GUI is very intuitive. That is the way I would explain its ease of use. It is straightforward.

I have been using Forcepoint Data Loss Prevention for over a year.

As for its stability, it is very stable.

I believe it is very easy to scale.

Our clients are small and medium businesses.

Support is quite good for this product

The initial setup is very simple. You can deploy for 10 users or up to a hundred users in the same way.

In all cases we do the data classified setup. Usually for the biome of a small company, like 50 users, setup takes more than one week.

I think it's the most cost-effective and affordable solution compared to other solutions that I have. I have not heard anything bad from customers.

If anyone is looking for simplicity in a DLP solution, they must go with Forcepoint. 

On a scale between one and ten, I would rate Forcepoint a nine.

We mainly use this solution for data protection and access to our critical company information.  

I do not think I should name a specific feature that is the most valuable because it is a product we are using as a unified solution and that is very important because it is one of the leaders in the Gartner Magic Quadrant. So there is not a specific feature that is more important than the whole of it together.  

The product is actually quite a good and reliable product and I don't know what to suggest because we are quite satisfied with it. So I would not want to name something that could be improved because it is a product that the vendor company is continually improving and upgrading on their own. The new features that they add in are quite satisfying for our needs. They seem to stay one step ahead.  

There are customers that are moving from Fortinet or Cisco to Forcepoint. I think that is mainly because it is coming from military technology, from Raytheon (defense contracting), so it is quite well rated even though it has not been around for a long time.  

In the next release of Forcepoint DLP, I don't really think that there a lot of things that I would need. I guess that there is always a way to improve the experience surrounding the user interface.  

We have been using this solution for about two years now.  

The product is very stable.  

It is very easy to scale this product because it is made to be used by big enterprises and also fleet management sites all over the world. We have about 100 users who are working with the solution within our company. They are normal end-users, not administrators, and the product is installed on each computer. We only require one person on staff for deployment and maintenance. It is actually less than one person. But it is one person dedicated to the task of supporting the product.  

We have had the opportunity to use their technical support. They were very prompt and very good about getting us what we needed. They are very skilled and we were satisfied with their work.  

We did not use another solution previously before using Forcepoint DLP.  

The setup for the product is quite straightforward. It takes maybe 10 or 15 minutes to be installed before it is ready to be used. For the integration, it took maybe one day. In all, it was very fast.  

We did the deployment of the solution with the help of our own team. I was not directly involved.  

The cost for the product for us is less than $10 per user. We do not pay any additional costs for technical support. Everything is included.  

Before choosing Forcepoint DLP we did evaluate other options in the product category like from CA Technologies (Computer Associates, acquired by Broadcom, Inc.). We also considered a DLP product by Symantec.  

Advice that I would give to someone looking into implementing Forcepoint DLP is to take care and compare it to other solutions. Other solutions may have a more established reputation because Forcepoint is a new name on the market. But I would recommend taking a look at all the technical features and the pricing as part of their consideration before making a decision.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Forcepoint DLP as a nine-out-of-ten. The thing that would make it a ten for me would be for the company to improve the technical implementation. It should be better organized.  

The primary use case of this solution is to manage personal identification, and for data loss prevention in government.

What I like most is that it's quick. 

It's fast and it prepares loss reports.

The data loss prevention and personal data need improvement. 

The protection of personal data needs to be improved.

I would like to see integration with OCS in the next release of this solution.

We have been using this solution for four years.

We are using the latest version.

130 people using Data Loss prevention.

I prefer Forceoint because it is cheaper than Symantec.

I prefer Forcepoint for data discovery and data loss prevention. I have evaluated Symantec data loss prevention and ICT (Information Centric Tagging) for classification and discovery.

My advice would be to use these same components. 

I would rate this solution an eight out of ten.

The primary use case for this solution is DLP.

Some of the features that I find to be valuable are the data loss features, such as CASB, Network, and Email.

The Database needs to be improved and fine-tuning is required on this product.

If they fine-tune it more, It will reduce the time that the client is spending on doing it. There are competitors on the market who are doing that now.

I realized that the engineering team is working on updates and improvements, so it is possible they are working on this now and will make it better. There are more things to see with this solution.

There are default policies regarding the source code and your instant messages. They should have been upgraded. I had already raised this and opened a ticket regarding this issue, and they are working on it.

The way DLP is now, people are using many different electronic things. DLP needs to put some focus on improving.

I have been using this solution for the last two years.

This solution is one hundred percent stable.

After the configuration, it is very stable, and in the last two years, I haven't been faced with many issues or product-related challenges.

This solution is scalable.

The technical support is very nice. I don't have any issues other than the time zones. It's a bit of an issue for me.

The support is over email only.

The initial setup is a bit complex. You will need help from the peer support team in the configuration.

The environment is based on your environment and there were some policy-related issues, but they have been fixed internally.

It is better to use this solution first, before using others.

Overall it's a nice product.

I would rate this solution a nine out of ten.

We primarily use the solution to stop the loss of data through various channels. 

The fingerprinting technology is the solution's most valuable feature. It's unique to Forcepoint.

Forcepoint should consider developing its own classification technique to complement its fingerprinting technique. That way it will be the most sorted after DLP Solution in the market.

Technical support needs improvement. There are long stretches of time between queries and responses. It's worrisome.

There's zero Forcepoint presence in West Africa. Customers typically like having these things close to them. It would help if they had a presence here. Right now, Forcepoint West Africa has been administered from South Africa. Because of this, customers can't access premium support in our region.

The stability of the solution is very good. I'd rate it ten out of ten.

The solution is perfectly scalable. We have thousands of users on different deployments. The highest amount of users on a deployment is somewhere around 6,500. We do intend to increase usage.

There's no support presence in my region. Because of this clients can't access premium support.

From the DLP perspective, I have only used Forcepoint, but from the perspective of general edge firewall URL filtering, I've used Checkpoint. I've also used Sophos in the past.

If you understand what it is you want to achieve, then the setup is straightforward. Deployment takes anywhere from three or four weeks all the way up to six or eight weeks. If clients don't give us all the requirements it takes a bit longer. For maintenance, you need about two people. As long as they have Forcepoint administrator certification they can handle maintaining the solution.

I do try to handle the implementations myself, but I also have a list of consultants that can assist as necessary. Forcepoint has very good documentation I can reference if I need to, which has been very helpful during implementations.

I'm a Forcepoint reseller. I typically handle the on-premises deployment model, but I do have a client who is currently moving to the cloud.

I would rate the solution nine out of ten.

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.

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.

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.

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.

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.

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.

I will rate their technical support a seven out of ten because their response time is very slow.

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. 

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.

We use Forcepoint primarily for data loss prevention and detection.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Our primary use case for this solution is to prevent leakage of enterprise legal data and company confidential documents.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Before choosing this solution we evaluated Symantec Data Loss Prevention, but the pricing is too high for most of our customers.

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.