Forcepoint Data Loss Prevention Reviews

The main purpose of DLP is to protect data from being sent outside of the organization without authorization. So, my client uses it to protect emails and web traffic and to integrate with content classification and USB blocking systems.

Some good features are basically its UAV Analytics engine. And even fingerprinting is really good in Forcepoint.

Forcepoint recently released an in-line proxy feature, which is a great addition. Previously, users had to add an extension to their browsers, but now that's not necessary. Now, that extension is not needed. 

One area that could be improved is the support. The current support is not very good. Because they don't come on time when a customer really needs it, they take a lot of time to troubleshoot anything.

For Mac, they should introduce the feature of airdrop. Currently, no DLP detects the airdrop feature. Like, if we have an airdrop. So, no DLP detects that any file is going from Airdrop. Our customers have these use cases. 

I have been working with this solution for five years. For Forcepoint, we are a titanium partner. 

It's scalable. We sell to medium and enterprise-level businesses. 

It is an easy installation for Forcepoint.

To deploy Forcepoint, we would take almost a week because it's an on-prem solution. But now they have even a cloud platform. So it can be done in one or two days. It depends on the customer and how they provide the insight and everything.

One person is enough for the deployment and installation process. 

For Endpoint DLP, obviously, we are the people who do maintenance. But for SaaS-based, it is GTP service only.

The pricing is fine. It's a yearly based license. For endpoint Forcepoint DLP, they have another license, and for network DLP, they have another license.

Overall, I would rate the solution a ten out of ten. It is a really good product. 

It is very user-friendly, even for admins. However, the support is very low otherwise the product is very good. 

I am using Forcepoint Data Loss Prevention for security.

We have not implemented the solution fully and it is still being configured.

The solution is stable overall.

The implementation could be improved.

I have been using Forcepoint Data Loss Prevention for approximately three months.

I did not experience any crashes. The solution has been stable in my usage.

I rate the scalability of Forcepoint Data Loss Prevention a four out of ten.

I have used the support from Forcepoint Data Loss Prevention.

I rate the support from Forcepoint Data Loss Prevention a seven out of ten.

Neutral

I have used a similar Microsoft solution to Forcepoint Data Loss Prevention, and the Microsoft solution was better. However, we were using Forcepoint Data Loss Prevention because we had a contract.

The initial setup of Forcepoint Data Loss Prevention is of medium difficulty level.

I have not seen an ROI at this time. I have only used the solution for a short time. I would need approximately one year to determine the ROI.

The price of the solution is expensive.

I rate Forcepoint Data Loss Prevention a five 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.

The primary use case is to protect sensitive data going out of the organization and helping the team to manage the incidents to create few to no false-positive incidents. 

Mac users can use Forcepoint DLP without any problem. They can create user-defined policies rather than using pre-defined ones. Using the fingerprinting policy can safeguard any data kept on a particular drive. We're using OCR to protect data being sent out through images implementing discovery policies to check if any particular file is been shared.  

The Forcepoint DLP is such a useful tool for organizations as it protects sensitive data with multiple kinds of functionality such as OCR and an analytics engine (which helps determine if any sensitive data is in danger of policy violations). It's easy to determine the incidents that have been triggered. This has helped to identify what sensitive data has been shared. The only part where it didn't work so well is during agent upgrading. If we automatically try to upgrade the agent it causes a lot of problems.

With OCR and Risk Analysis, we are able to determine if anything sensitive is been shared. OCR helps us to safeguard those things and with risk ranking, we can determine which user is trying to violate policies multiple times even though they have been blocked to him or her. It does require additional servers, as the processing and result of the incident is high, however, it's worth using to see all the use cases being met with these two features as well. They are the best features provided by Forcepoint.

The feature which needs improvement is the Forcepoint agent upgrading. When you automatically try to upgrade the agent it causes problems. For example, the system starts to behave abnormally or the agent is unable to communicate with the policy engine. If we try to upgrade to new version with the old version running, sometimes it works without any issue, but sometimes it causes a lot of issues and it gets disconnected from the DLP servers. 

You can see incidents via delays on the console even if the agent is properly installed and connected with the proper policy updates.

I've used the solution for two years.

Many organizations will have different use cases with Forcepoint Data Loss Prevention. Many companies are moving to an Amazon AWS cloud-based dashboard.

The solution has three deployed options, cloud, on-premise, and hybrid.

We appreciate the user-friendliness and ease of implementation of the Forcepoint Data Loss Prevention platform. The availability of the vendor support team is an added advantage.

The support could improve Forcepoint Data Loss Prevention.

I have been using Forcepoint Data Loss Prevention for approximately four years.

There are some improvements that can be made in stability.

I rate the stability of Forcepoint Data Loss Prevention an eight out of ten.

Forcepoint Data Loss Prevention is scalable. Our customers have between 3,000 and 10,000 devices using the solution.

The solution is scalable.

Customers that have voiced technical support could improve.

We have a flexible model to size customers' requirements to deploy the solution and the process for us is not difficult.

The charges that the vendor has for the implementation are expensive.

We have a team of three people who are certified in implementing the solution.

There is an annual subscription model and the amount depends on the type of implementation.

I rate Forcepoint Data Loss Prevention a nine out of ten.

The most valuable feature of this solution is that it captures where the data is being moved.

Forcepoint is the one I see most frequently mentioned in a lot of webinars or insider threat discussions. 

It is a product that is commonly referenced.

Everything takes a long time, as it does in every software company, especially since COVID. That is something I notice with every product I use.

I have been working with Forcepoint Data Loss Prevention for three years.

We are working with the most up-to-date version.

Forcepoint Data Loss Prevention is a stable solution.

Forcepoint Data Loss Prevention is scalable.

It is widely used throughout the business.

Response time is slow.

The initial setup is typically straightforward. 

It is unique to every environment. Some things break when you set up a new network or system. It's trial and error.  

Compared to other products, it wasn't overly complicated, It is the same or standard.

I would rate Forcepoint Data Loss Prevention a seven out of ten.

It is a good product. 

I am not overly excited about it, but I believe that all of the software has the same issues that I do.

It is the same problems I have had with other software, such as the customer service being slow, something breaking, or there's a patching issue. 

We are using it for PCI compliance.

One of the most valuable features is the set of built-in policies that Forcepoint has for PCI compliance. We just need to activate them and start working. Without them, it would be a big task to do a data transformation. Another advantage is that Forcepoint also updates these policies. If there is a new control for PCI compliance, Forcepoint updates it in its system and it can be downloaded.

Forcepoint is also easy to use and manage.

The reporting features, the real-time reporting, can be improved in Forcepoint. On the dashboard, we don't have a feature that shows real-time incidents. We have to schedule a report in the environment.

I have been using Forcepoint Data Loss Prevention for two years. I am a partner for Forcepoint and Symantec. I suggest DLP solutions to my customers.

Forcepoint is very stable. Symantec is also very stable.

Forcepoint is quite scalable. If we have more network traffic, we can add an appliance and it will be enough for that increased traffic. It scales up.

The number of users in environments where we have deployed Forcepoint is between 5,000 and 7,000.

I would rate Forcepoint's technical support at eight to nine out of 10. The support has separate sections, including essential support and basic support.

The initial setup of Forcepoint is straightforward. It uses a Microsoft SQL database and the solution is implemented on Microsoft Windows Servers. When it's based on Microsoft, the solution is very integratable. Optimization of the installation is not complex. It is just like installing other software on Windows. We just need to learn the setup process and click some tabs and the solution is installed.

In general, the initial setup of the different components of Forcepoint takes only two to three days.

Our process is that we first install the database and then we install the Forcepoint Security Manager, which is the centralized location for policy management and reporting for all the solutions' components. Then, if required, we install the additional Security Manager. It is straightforward. Next, we implement the DLP on the endpoints, and then we work through the network side.

One of our recent deployments of Forcepoint was for a bank that has requirements for PCI compliance. In terms of what they invested in the solution, they got the value back within a quarter.

The licensing of Forcepoint is quite straightforward. It's based on the number of users. The support fees are a separate cost.

The main functionality of both Forcepoint and Symantec is actually the same. But when it comes to deployment, Symantec's solution is difficult to deploy. To deploy Forcepoint I only need three Windows servers, but to deploy Symantec DLP I need eight Windows Servers.

With Forcepoint, we can take backups automatically from the appliance itself, using the Security Manager, in case of disaster. We just schedule a backup job and it takes the backup from there. But with Symantec DLP there is no feature for backing up and we have to do the backup manually.

But for larger enterprises, Symantec provides an Oracle Database where there are no limitations for keeping incident data in the database. Forcepoint uses a SQL database that can't hold as much data. Large enterprises often use the Linux operating system for their core applications. Symantec fully supports a Linux implementation of the core architecture of PLP in a Linux environment, but Forcepoint is only installed on Microsoft. This is one of the biggest factors for larger organizations, given that they often require a PLP solution.

If an organization is small or medium in size, I would deploy Forcepoint for it. The price and the architecture requirements, and the equipment required for small and medium businesses, is reasonable. For large enterprises, with more than 20,000 users, I would deploy Symantec.

We are mainly using this solution to protect internal documents. It's an internal document creator for the customers.

The most valuable feature is the endpoint DLP. It's specific to copying to the USB or copying to the internal storage in our office.

It's user-friendly and the interface is good.

In terms of display, the support and the Mac platform requires a lot of improvement.

When working with different browsers, we need to upgrade.

Being able to upgrade the agent from the console itself would be great.

I have been using Forcepoint Data Loss Prevention for two years.

It's stable. Forcepoint is a very old product.

It's scalable, but we don't have many requirements to scale it.

We have approximately 50 users in our company.

Technical support is always good with providing a solution and understanding the issues.

They are able to resolve the issue and provide a solution.

Overall, I would say that the support is good.

We moved from Symantec.

The initial setup was not completely straightforward, but not too complex.

The migration takes some time, but that is with any solution.

It took approximately two months to deploy.

The deployment was completed in-house.

Pricing is handled by another department. I don't have any information in this area.

This is a product that I can recommend to others who are interested in using it.

I would suggest evaluating it and do some testing before making a decision. It's a different environment.

I would rate this solution a nine out of ten.