Our model of deployment is on-premises. The only issue with deployment that we've found is that sometimes OPC is not able to connect to SCM or to a particular vendor. The deployment took around 20 minutes. Everyone was involved in the deployment of this solution, every department. It takes about two to three people to maintain this solution.

Forcepoint Data Loss Prevention is a medium level of difficulty for the initial setup. It's not easy or very complicated. 

I heard that the implementation was pretty simple. Only the policy creation took time because we had to build use cases for it. Your industry might have a different use case, and my industry might have a different use case. It took a little bit of time, and it came from an implementation standpoint, and I felt it was pretty good. 

You just need one person working in shifts to use this solution. As we have 8,000 employees, we are doing it in shifts with three professionals.

The initial setup is simple. It's now easier than Microsoft, for example.

We currently use a hybrid model with on-premises deployment for the top and cloud access for laptops.

The initial setup was not that simple. The solution itself is too big, too vast, to really learn properly. It also wasn't as flexible as we needed it to be 

In terms of the initial setup, they have bifurcated in a way so that each and every channel has to be protected. I don't understand why can't we enable something on the fly. For example, with a checkbox, I should be able to enable it as part of the feature to enable the future. That is not available, so I have to go ahead and deploy different components on different channels.

However, it is rather easy. I'd rate it a four out of five in terms of ease of setup.

Skill-wise and license-wise there is no major challenge. 

If I have all the prerequisites, all the firewalls open and everything, I can deploy in one day. The initial setup requires some expertise to implement. It's easy for me because it's something I've been running for a couple of years. Policies are the issue and they have to be tweaked every day. 

The initial setup is very simple and can be completed without an integrator.

The initial setup of Forcepoint DLP is neither easy nor complex. The technical setup is easy, however, the user education takes time and can be a bit of a strain. 

The initial setup for Forcepoint Data Loss Prevention is easy. My company did a POC and demo session, and the solution is currently in the deployment phase.

I rate Forcepoint 10 out of 10 for ease of setup. It's one of the simplest DLP solutions I've used. Symantec is more difficult than Forcepoint. Setting up Forcepoint is straightforward. 

They have an extensive knowledge base online, and the steps are well-defined in those documents. We have a console server called Forcepoint Management Center. We also need to deploy DLP agents a Protective Appliance on the network server. Forcepoint has extensive support for integrating with other vendors, so the setup is quite fast. We can integrate the product with any of the proxies available in the customer environment.

I rate the initial setup of the solution nine out of ten. The solution's deployment time depends on the customers' requirements. It also depends on the environment of the customers. If the customers have a deployment tool, the deployment will be done quickly. Else, it will take some time. To deploy the solution, we provide the customers with a technician to assist them. After that, the customer is responsible for taking care of the people they need for any additional assistance.

The initial setup was straightforward but setting up the rules was very complex. It is something where things don't actually work as we think they will work. It generated a lot of false positives in the beginning.

Our deployment took about a month.

Our strategy was to start with auditing first. We haven't actually moved to blocking yet. When we tried to move to blocking critical files, it ended up blocking some other people at work. There are some issues around that and we have had to be careful.

We let it run on its own. I look at the data in Forcepoint on a weekly basis, but we don't have any administration of it, per se. My IT team handles the deployment of new employees coming in, meaning the deployment of the Forcepoint agent on their laptop. That's about it in terms of admin.

The product's initial setup phase was easy.

The solution is deployed on an on-premises model.

The time taken to deploy the product is something which depends on the solution or the setup. Mostly, the solution can be deployed within three days, after which some finetuning is required to meet the requirements of our company's customers.

The setup is not complex and it will take around two to three hours for deployment to complete.

The initial setup is straightforward. 

I believe the initial setup is complex and is handled by another team.

The deployment was done over the weekends and it took the IT team approximately two to three months to deploy bank-wide.

I was not involved in the initial deployment, but we've had it ever since I've been on the team here. I've been managing it ever since. I was there for the initial deployment in one of our sister companies. It wasn't anything unusually difficult. It just required installing some hardware and getting all the firewall rules worked out. Once you get all that in place, everything usually works pretty well. That's been my experience, even with upgrades. Most of the time our issues have been firewall blocks within our own company. That's usually the biggest hurdle, overcoming our firewall-related issues.

We use it on about 5,000 endpoints and we have two people who administer  it. They're both information security analysts.

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.

Implementing Forcepoint DLP can be a bit complex, as it requires a DLP expert to help with the setup. However, day-to-day administration is quite user-friendly. We are currently using the on-Prem version of Forcepoint DLP as no cloud version is available yet.

We have five resources to handle Forcepoint DLP's maintenance. 

The deployment is straightforward once you understand the solution's architecture. A proper understanding of the different components of Forcepoint DLP is essential, as deploying an enterprise-level DLP could be confusing because the policy server is separate from the main engine sitting on the Triton server. Understanding the components of the enterprise DLP suite is the most critical element for a successful deployment. Still, I rate the solution seven out of ten in terms of ease of setup.

The scale of the particular DLP deployment is also a factor; we had cases where the customer only required endpoint or network DLP, a relatively quick job that two staff can complete. A complete DLP suite, including email, web, and network DLP, plus data classification and labelling, would require four associates. Our most recent deployment was a complete enterprise DLP, which required four staff. The entire deployment took almost three months, including a one-month planning phase. During the planning phase, we prepared the documentation, designed the HLDs and LLDs, and high and low-level diagrams. Following acceptance from the customer, we started the implementation, which took roughly 50 to 60 days.

The level of maintenance required depends on how many events per hour a particular tool is putting out. If a customer wants to check analytics or identify an email or data leak, that situation doesn't require much policy fine-tuning, and a single staff member could deal with it. The customer can also decide what coverage they want, which may be 24/7, an admin to monitor events only, or Monday-to-Friday support. The coverage determines how many engineers will be required.

Another factor in maintenance requirements is the volume of events, as an extensive client could have more than 10,000 servers with many sensitive data in motion. The customer had 24,000 users for our last deployment, and there wasn't a dedicated team for the DLP. The engineering team took care of the network, endpoint, and data security together. There were ten of us on the team, with two engineers per shift for 24/7 coverage.

The implementation is not as easy as people make it out to be. Once you get it right, the product is fine, but this requires understanding it and getting the proper training. A novice that has begun to work with the tool can find it quite difficult to implement if they don't have a good understanding of the product, and do not have the right support.

For example, in one organization it took us about three months to implement it, whereas it should have taken about a month.

Our clients have hybrid deployments, where they are part on-premises and part cloud. The choice of cloud provider is made by the client but they either choose Microsoft Azure or AWS.

The implementation strategy that we use varies depending on the client. For example, at the bank, we wanted to prevent data breaches, especially with credit card information, and ensure compliance. Therefore, our strategy was focused on just the PCI requirements so that we could take reasonable measures to protect the organization. Essentially, we wanted to go from zero to hero quite quickly. That was possible because of the flexibility and agility of the product.

When it came to the telco, it was a completely different strategy. It was a long-term strategy in terms of protection of personal information and preventing it from being divulged without authority to would-be criminals.

When we deployed it, we literally had to look at the requirements and configure it from a POPI perspective. In this regard, the deployment was skewed toward personal information breaches.

In terms of implementing the solution, it's not easy and not complex. It's average. The deployment's level of difficulty is average as well. You just need to have the prerequisites satisfied. 

I appreciate their support because their support was with us to assist us until we deployed the two instances in our infrastructure.

I was the CISO, the Chief Information Security Officer of the company, at the time. My scope was to assist and to manage the project from the start to the close. I worked with the operational security to deploy it.

My scope was to cover governance. For example, elaborating on the policy for classification. It was a prerequisite to define the policy target in the DLP and to organize or to plan for the workshop with the strategic and sensitive entities in our group. I made sure they tried the solution and integrated the entities into the pilot side as well. 

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.

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

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.

As compared to other DLP solutions, it is quite complex because they do have their policy server and analytics server in place, and their Forcepoint manager is also there. With other solutions, we need to have an Oracle Database in place, which is not required with Forcepoint. For Forcepoint, SQL Server can be quickly installed and is ready for use.

The installation duration depends on the organization and the size of the organization. For the same set of organizations, Forcepoint will take 30% less time as compared to others. In many organizations, I have implemented it within a month, and in many organizations, the project took one year.

The implementation strategy depends on the customer, but we do follow the implementation steps, such as gathering information and then deciding which detection server to go for, where to place it, and how many counts are required. If I have more than 30,000 agents, then I definitely need to think about one more endpoint prevent server. So, it depends on the organization size and the response of the organization in terms of how quickly they adapt DLP and how friendly they are with the DLP solution. The biggest implementation that we had done had 30,000 users.

A mandatory process that should be done before implementing the tool is a data classification analysis and the setting of a policy for data classification. These processes are done through an analysis session with different departments. The session includes teaching them about data classification policies and getting information from them regarding the data that needs to be protected and the recommended classification level that data should have.

We then deploy the server-side in the data center and start installing a sample agent. We test this agent and we test sample policies to ensure everything is okay on the sample agent. Finally, we do a full deployment.

Maintenance, post-deployment, involves making sure the solution is updated to the latest version. It has different components, and each component should be updated to the appropriate version. The same goes for the agents on the computers. The configuration should be reviewed and maintained over time, as well. One person is enough to maintain a Forcepoint instance.

The initial setup is very easy. It has only one console for multiple channels like email, network, and DLP capability.

The deployment depends on the customer’s environment. We have to configure the DLP framework for the categories. Overall, the deployment takes around one or two years for a complete DLP solution.

It is straightforward to set up. It's not difficult at all. I'd rate the ease of setup eight out of ten.

The deployment process took us about two months.

We only needed two people to handle the deployment and maintenance tasks. 

The deployment may be a bit difficult. 

We only need one or two people for maintenance and deployment tasks. 

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.

Because the solution is deployed on premise, you need to deploy every component based on SQL.

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 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.

The initial setup and time it takes to deploy is dependant on the customer's environments and requirements.

After it is deployed, Forecepoint Data Loss Prevention requires maintenance and support.

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.  

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.

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.

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.

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.

Deployment can take anywhere from four to five hours. It can take up to two days depending on the infrastructure.

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. 

The initial setup was not complex, but not simple.

The initial setup is complex. 

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.

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. 

The initial setup is not really complex, but not straightforward either. We had some issues because it requires an SQL server and at that point, we were experiencing some issues with our SQL server. Some of the steps in the initial setup process were not really mentioned, precisely. 

The good news is that only one person is needed for both deployment and maintenance; however, that person has to be quite knowledgeable with Sysco, some Linux, and windows.