The initial setup is very straightforward and simple. It’s not overly complex or challenging.

In terms of maintenance, there is none at all, actually. If you implement it correctly in the initial phase, it requires very little interaction throughout.

Forcepoint Secure Web Gateway is an agent-based solution, so my company uses a remote deployment tool to take care of the installation phase.

If a person understands all the important tools and how they can be integrated with all other security products, it's easier to set up. It's a little bit of a challenge for any new person. There should be a blueprint or a condensing intro matrix. The Secure Web Gateway must be integrated with multiple other security products within the enterprise. There needs to be a compatibility matrix, like how this virtual VDA enrollment and other solutions. Nowadays, VDA enrollment is also coming as a hosted solution in the cloud and virtual software enrollments. It can be either on Azure, AWS, or some other third-party tools, probably that's like VMware Horizon, or it may be coming from Nutanix Frame. There are so many integration complexities in a large enterprise. If there's a blueprint, automation, or workflow, it improves the early adoption of these tools and provides a better onboarding experience.

Most of the deployments we manage through the deployment tools collected, either via IBM patch management solutions, or some automation tools, like Python. Using these agents helps with the rollout.

Initially, we took a week to ten days to deploy the product. However, rolling out the agents now, the agents are adding automated tools. For the initial implementation in our organization, we had more than 2,000 finder servers, plus other NTPs, which is why it took almost ten days.

I'd rate the overall process a four out of five in terms of ease of deployment. 

Following deployment, the maintenance is minimal. It's on the cloud and we have a subscription, so there isn't much to manage. 

The initial setup is easy. We need to install an agent on the end user’s device. It takes two to three minutes to install. It’s a completely cloud-based solution. We need not alter our environment.

The solution’s initial setup is straightforward.

The initial setup was complex. The time taken for deployment was a year.

The deployment process involved the making of software-based applications. Then, we install it.

For the deployment and maintenance, we need five to seven people, including engineers and managers.

The initial setup is straightforward. 

You just need to put a server to sync your user information with the cloud for the authentication perspective. If you're not using the AD environment, you can just send an invitation link for your user, so they can register themselves with that Cloud Web Security console and use the functionality and the admin can apply the policy for specific or the email ID based users. 

Definitely, if we are talking about the Cloud Web Security solution, not only Web Security solution, any cloud solution, so generally, they're asking for the email addresses when they are going to integrate the AD environment on the cloud. So, that is recommended for all of the web solutions.

This is a flexible environment; you can just put that agent on machines through AD or any third-party deployment tools. There is the flexibility of the port connectivity, where you can just keep open the ATA 443 port that is generally used in the organization environment, and you can suggest the customer open the specific port for the specific cloud ranges. 

You cannot open that traffic for all of the internet.

The initial setup can be complex depending on the location. For instance, in the Middle East, we have to use our direct endpoint client. In Europe, we use the proxy endpoint client.

The initial setup was simple.

The initial setup for Forcepoint Secure Web Gateway isn't easy. When you compare it to Fortinet, it's very complicated.

For example, for Fortinet FortiProxy, you don't need to install the database or SQL, and there's no need to prepare a server. You also don't need to do a lot of authentication because it's only one appliance, so it will work via proxy, then you can do the installation.

For Forcepoint Secure Web Gateway, you need two servers: one for installing the management software and the second server for SQL, and only then can you control the appliance.

The initial setup for Forcepoint Secure Web Gateway is complicated, especially when compared to Fortinet FortiProxy.

The initial setup for Forcepoint SWG is straightforward and user-friendly. The basic configuration is not very complicated, and you can have the solution deployed in a day. However, when it comes to more advanced configurations or customer-specific enhancements, it can get a bit complex. While the initial steps are smooth, customization might require more effort and expertise.

In terms of the policy, the initial setup can be complex.

The solution is simple, however, the complexity comes when you are writing the policy for the data leak part. Even web security is all policy. You would need to translate your business requirements into cyber security requirements so that basically whatever policy that is being in place, covers your business requirements for your cyber footprint.

The product's setup is straightforward. 

The initial setup is not overly difficult. 

The time it takes to deploy the product depends. If I have all the items I need in my hand, it doesn't take that much time. However, compared to other products, it takes a little while time since you need to get it on the client's field servers for reporting, and you need to have some access with admin privileges. 

it was a fairly straightforward implementation.

You need to plan it out carefully, so your deployment is good.

Forcepoint Secure Web Gateway, setup-wise, is complex unless you get some support. It's challenging to set up using an internal ID.

I'd rate its setup as three out of ten.

The initial setup is straightforward, we deployed in-house and implementation required one person. The initial setup takes two or three days, but rolling it out and making sure that everybody has the required access, and that business applications are accessible, can take a month or so. 

The initial setup is relatively straightforward. You need to spend some time defining the template of the environment that you would like. After that, the deployment in different domains is pretty easy.

The initial setup is not complex, but requires being setup from the beginning. There is no default setting, so you must go to the console and configure the product from the beginning. It takes about 10 days.

It is a cloud-based deployment so the initial setup is not complex. There are a couple of things to configure, pointing them to your mail servers, but it is easy and straightforward. 

The initial setup was pretty straightforward.

In fact, you could literally load it, install it, and have it up and working in no time. All you had to do was point a browser to it and you could prove it worked. Now, if we wanted to take it and fully integrate it onto the network, then nine times out of ten, we used one particular method called WCCP.

It was straightforward, since I had deployed it at my previous company. The engineer assigned to our deployment was also on hand to make sure that I followed the updated best practices.

We didn't face any major issues at the time of implementation. We were using the facility management of both HP and IBM. They each have their own in-house capability to manage the software. Also, the OEM would have supported them well. As such, we didn't see major issues on any of the software implementation. There were just a few initial hiccups that can happen on any major project.

The initial setup is complex, it requires an expert engineer to complete but managing the solution afterwards is not complex.

The initial setup is very simple and not overly difficult. 

The initial setup was straightforward. The upgrades, however, are not straightforward, and they don't always go as per the plan. It also depends on your environment and the configuration. The advantage of going for a cloud solution is that you don't have the overhead of managing upgrades and downtime. The advantage of an on-premises solution is that you have more control, which is really nice. You have ownership, and you have the chance to develop your own solution, which is fantastic.

Complex, only in it offers a huge amount of features.

With any box security, we need vendor support during the first installation each time. After that, we don't need any support for operations. But the deployment could be easier. It might take from one day to three days. Usually, that involves an engineer from the vendor and a working team at the enterprise.

The initial setup of the product did not take long and was uncomplicated. Its deployment took three days.

Straightforward. Very easy to implement.

In terms of implementation, if you are going to implement Forcepoint, you have to think about how you will deploy it in your proxy environment. You have the ability code, as well as other items. 

If you are implementing Forcepoint in web proxy, it has to be P1 or P2. It has to be on the user onsite as V2 on V5. You could, for some environments, have two interfaces that communicate with each other. You cannot get both to interface, however. If you use the P1 for a user's internet, you then have to make P1 access the internet.

The initial setup is straightforward. Deployment, like the initial setup, to configure with the licensing, can be done in two days.

Our use of Forcepoint Web Security is not built on the calculation or the policies, i.e. how the configuration will take place. Based on that, we have two different areas.

The setup is very easy.

Setting up the solution for our clients can be difficult because we are dealing with different timezones and different geography. It also depends on their data center.

The clients sometimes depend heavily on the partners, rather than take time to understand the product themselves.

Implementation can take some time, but there are lots of resources online to help.

The initial setup is somewhat complicated. Implementing this solution and deploying the servers is the challenge. It has to be planned properly but once it is complete, the security features work properly.

The length of time for deployment depends on whether the customer is ready and has all of the prerequisites in place. If everything is ready then the deployment will take a maximum of one week. One problem we sometimes face is that the customer says they are ready and has verified that the prerequisites are in place, but in fact, once we visit the customer we find out that they are not. In cases like this, or when the information we need is not clear, it can take longer to implement.

Our environment is complex, so it is hard to say.

The deployment is a bit complex. If you have all of the prerequisites and know all of the sites then the deployment can be done in a few days or a week. It's very rare not to encounter issues because customers will make requests, and you get stuck because of the different environments. You have to contact the customer to figure out how to resolve problems, and it can be time-consuming. The important thing is to have the planning done before starting the implementation.

The simple part of the deployment is the installation on the VM. You just have to get the license, visit the support portal, download the image, and install it on the virtual machine. When deploying on the cloud, you just have to make sure that you have space in Azure.

It was complex with a lot of technical issues.

We have not had any big issues installing the solution.

Straight forward

It went as planned.