Forcepoint ONE Reviews

Forcepoint ONE is a very, very good product, especially for my SOC (security operations center) team though you'll need to get a lot of training to optimize the solution and ensure that it meets your needs. Forcepoint ONE is a very good monitoring solution, and it gives my organization a lot of information on how to boost security and how to keep new products or new applications secure.

Forcepoint ONE is okay for me, and I find it a very good solution. Its most valuable feature is monitoring. Its monitoring is very good, and it can communicate with a SIEM system. I also find the DLP feature of Forcepoint ONE good.

One area for improvement in Forcepoint ONE is that you'll need more training to install the solution yourself. I practiced in a laboratory and I needed more technical information to do the installation.

In the laboratory, Forcepoint ONE is stable, but I don't know if it's stable in a real environment because I have not installed it yet in the real world. In a laboratory setting, it is pretty stable.

Forcepoint ONE is a very scalable solution.

The technical support for Forcepoint ONE is very good, at least when I needed support in a laboratory setting. On a scale of one to five, with five being the best, I'm rating the support a four.

In terms of the initial setup for Forcepoint ONE, I'm rating it a three out of five. I'm giving it a score of 60 percent out of one hundred percent. I currently don't have an implementation strategy, but if I need to implement the solution, I would need more training, or even take a special course on how to implement Forcepoint ONE.

Forcepoint ONE was deployed through an integrator or consultant.

I don't have information on the ROI from Forcepoint ONE.

The licensing cost for Forcepoint ONE would depend on the features, but the pricing is very competitive here in Brazil. The solution offers a good price, and I would rate it a three or a four in terms of pricing. I don't have information on whether there are additional costs apart from the standard licensing fees for Forcepoint ONE.

My company didn't evaluate other options because it is an integrator of Forcepoint ONE, so it only has Forcepoint ONE as its solution. This means I didn't do any testing with competitors such as Zscaler and Netskope.

My company is a partner and reseller of Forcepoint ONE. I work with the solution, though I'm not as experienced with it. I had my training in the Forcepoint laboratory in Brazil because I just started working with the solution, but I know how Forcepoint ONE works, how to use it, and how to implement it. I'm using the latest version of the solution.

The number of staff required to deploy and maintain Forcepoint ONE depends on the number of users because the solution can also be used individually or by a single user.

My advice for people looking into implementing Forcepoint ONE is to take a course or go into training because the solution may seem easy, but it's not, particularly during implementation, because it would still depend on your tool. You need to understand your tool well and how you can adapt it to Forcepoint ONE. The solution is not easy if it doesn't have a direct integration with your tool. When you go direct to the cloud, there's no problem, but when you need it to be a hybrid solution, it could be a bit difficult in terms of integrating it well. The integration, though it's not very, very difficult, still requires attention and care for it to be successful.

My rating for Forcepoint ONE is eight out of ten. For me to rate it a ten out of ten, the support, price, and functionality should first be improved. There would be a need to speak with the Forcepoint team about it, and the team is very, very dedicated in terms of explaining and helping you understand the solution.

Bitglass allows us to leverage cloud applications with security. What that means for us is that, as our applications are moving from on-premise to the cloud, we can have security controls on who logs in, around when they log in, and what data they're accessing. That's what Bitglass allows us to do.

We're not using the proxies. We're only using it for the login policy management.

We can now allow people to access cloud apps on their laptops, safely and securely, when they're not in the office. It allows us to have more flexibility, working from home or remotely during COVID. This is a security platform that allows all that to happen. Without having Bitglass, our work from home strategy would be drastically different and our potential for productivity would be reduced.

The solution provides a single platform for CASB, web security, advanced threat protection, identity, data loss protection, and zero-trust network access. It does all that in one product. It's good because it allows us to adopt more and more cloud apps. It really gives us the flexibility to pursue any new technology that is going to benefit our organization and that is in the cloud.

Bitglass also provides a single policy page to secure all of our interactions to the cloud applications. It does not do it for on-prem, in our case. It could do so, but not the way that we have it configured. But for our cloud interactions, we have unifying policies; a single spot on the platform. From there, we can say, "This set of cloud applications needs to follow this policy." From that point, we can see which policies are being applied. So it's a single spot for policy management. It simplifies our security operations.

The core CASB solution is the most valuable part. It allows us to put policies in place around which devices can log into our cloud applications. We have a policy that states that only company devices can access these cloud applications. Our most sensitive data lives in our email, which is in the cloud, and in Slack, which is our messaging platform, and it lives in Box which has all of our files. The ability to access all of that, our critical data, has to be from a device that's company-issued so we know that the security level and the encryption level are up to a certain point.

It does a great job of securing us against data breaches and attacks. Prior to our moving over to Bitglass, we had one incident where someone's password was compromised. Whoever the hacker was, was able to log in and then send emails on behalf of this individual at our company. After we implemented the Bitglass solution in front of email, that scenario was no longer possible. They can't log in from a device that's not company-issued because now we have these policies set in place.

In terms of how the solution secures us against data leakage, their technology is good in the sense that it resides at the login point. That means that at the point that you're trying to get to the application, you need to fulfill a certain set of applications or a certain set of policies.

Their new SASE (secure access service edge) product would have been the one thing I would have requested. Now that they have that platform, I'd like to see it as integrated and seamless as possible with the core product. That's what they're working towards and that's where we're seeing the advancements.

I have been using Bitglass for over two years.

The solution's overall uptime is good. We haven't had downtime for Bitglass in production. 

For us, it's scalable. We have not seen any issues.

We've got a 50-user license for our company. The users are from across the company, and our adoption rate is 100 percent.

Their tech support is good. They're a 10 out of 10 in responsiveness and they're an eight out of 10 in getting the resolution, which usually involves code changes.

This is our first CASB solution. We went with Bitglass for the security of our cloud apps.

The setup is fairly straightforward. It's not perfectly straightforward because you need to understand how it integrates within your cloud apps. Once you have the connection, the identity providers, then setting up the policies is easy.

We ran deployment and testing for about a month before going live.

In terms of our implementation strategy, we had a separate instance of the cloud apps running in parallel to test out all the policies and to fine-tune all of our policies. Once that was complete, we used that on our production tenant.

We worked with an integrator called RFA, but we did most of the testing on our side.

We have absolutely seen return on our investment with Bitglass. From a cybersecurity standpoint, we have more controls. And from a productivity standpoint, we have more and more cloud apps that we have deployed, and that's really working in our favor.

We looked at Netskope and Skyhigh, but that was this two years ago so our comparisons are fairly outdated now. But at that time, Bitglass had the best SAML integration, which is the identification and integration services. That was the key for us as we were looking to connect into a lot of cloud applications.

You should definitely look at Bitglass as part of your process. I think it's still best of class and I think there is a lot of innovation that's happening at Bitglass. In terms of a CASB, and in terms of this new product for SASE as well, they are the best in terms of the feature set that they're offering.

As for maintenance, we've got one infrastructure engineer and part of his responsibilities is to look at the weekly logs for Bitglass to see if there are any unusual connections.

• Location proximity mapping
• Data type inventory
• Simple integration

It allows a window into who is sharing what types of data internally and externally. It allows us know where sensitive data is really stored and offers the ability to quarantine based on data types and sharing criteria.

• Reporting
• Simpler policy creation

I have used it for 16 months.

The cloud-based portal tends to get slow as the number of events increase.

The sales staff promised more than they can deliver, but the technical staff is excellent.

I did not previously use a different solution.

Initial setup was simple.

Negotiate for the pricing model that fits your budget. The vendor is willing to customize pricing.

Before choosing this product, we also evaluated CloudLock, CipherCloud and Skyhigh Networks.

Take your time and have each vendor set up an actual proof of concept, rather than just relying on a demo. Get your network and support staff engaged in the process early on because they will be instrumental in deployment and support. Know what you’re trying to accomplish.