What is your primary use case for Bitglass?

I use Forcepoint ONE to protect sensitive data, enforce security and compliance policies, and ensure secure access to cloud applications, web resources, and endpoints. It enables me to monitor user activity, detect and prevent unauthorized data sharing, enforce access controls based on roles, devices, or locations, and secure interactions across cloud and web platforms. Additionally, it helps safeguard against malware, phishing, and other threats, providing comprehensive visibility and control over the organization’s IT environment while maintaining compliance and reducing risk.

My main use case for Forcepoint ONE is deploying Force for customers, so I help them to configure policies according to my customer environment; what they mainly want to do is use it from a content filtering perspective, where they would want to block users from accessing the internet or certain parts of the URL or anything like that. A quick specific example of how I've set up Forcepoint ONE for a customer is that they were trying to port over from an on-prem Forcepoint Content Gateway to a cloud one. As a deployment team, I receive a purchase order where my pre-sales and sales size the customer environment and suggest going with Forcepoint ONE, and what we did was port over certain parts of the policies, so it's more of a migration where we migrated the URLs that can be allowed and cannot be allowed to the particular Forcepoint ONE portal. I have nothing unique to add about how my customers use Forcepoint ONE; they mainly use it for the content filtering perspective of it.

The primary use case was web filtering. My organization used Forcepoint ONE ( /products/forcepoint-one-reviews ) for blocking and reporting on websites.

I use the solution as a secure web gateway, similar to a proxy, to control access to the Internet for users. It is implemented on our equipment, such as laptops, to block certain categories like gambling and games. This is particularly important in the financial services industry where clients access the Internet through our network.

The primary use case of the product is to ensure security and protection in a SASE (Secure Access Service Edge) environment. It serves multiple purposes, including securing roaming users and protecting users accessing resources outside the office. Another key aspect is safeguarding Insight applications using ZTE (Zero Trust Exchange) and preventing data leakage. In daily operations, it is primarily utilized through ZPA (Zero Trust Network Access), ensuring users have secure access to the internet. It involves protecting corporate devices from advanced threats and malicious sites and enforcing data isolation policies to prevent unauthorized data access or leakage. Additionally, the solution facilitates the secure transfer of sensitive data through various applications like Dropbox, utilizing policies set within the SSE (Secure Web Gateway) solution, potentially incorporating a model such as CASB (Cloud Access Security Broker).

Forcepoint ONE's primary use case involves safeguarding the browsing activities of users who bring their laptops home. Specifically, we aim to protect their internet navigation while in their residences. Additionally, we need to secure specific applications to ensure that sensitive data and resources remain protected.

We use Bitglass for real-time scanning and its unique VM that enables reverse proxy capabilities. Bitglass can also act as an IDP for us when we don't have an identity provider.

The use case is around protecting data on BYOD devices where users can access any type of data.

We started with a very clear primary use case, which is what landed us on Bitglass: The need to protect Office 365. More specifically, we wanted to make sure that untrusted devices would not be able to download the full O365 client. Granted, you can do that with Microsoft tools, if you purchase some of their additional solutions. However, we decided that it made more sense for us to go with an independent CASB that we could leverage for other things as well. Since the initial deployment, we have looked to expand well beyond the initial use case to protect additional cloud-based environments as well as implement additional functionality, such as DLP.

We use it for our cloud-based solutions. For instance, we use it for Office 365, Salesforce, and a couple of web applications that are cloud-based. It gives us an added layer of security with a little more visibility into those applications, as far as: who's logging in and who's not. It's kind of a firewall, in a sense. Since none of our business is really overseas, we don't really have employees or customers who should be logging in from outside of the United States. We just block any attempt that is coming in from offshore. Another thing that it does, if people are not able to connect, then it gives us an easy view into why they may not be connecting. For instance, if their iPhone is not connecting, then sometimes we can see if they are entering the wrong password or something else. It has a little simpler navigation than what Office 365 gives us. It is also a little quicker to see login failures.

There are several use cases that we use it for: * DLP purposes. * Multi-factor, step-up authentication. * In conjunction with Okta. We have a lot of sensitive data that goes back and forth into the cloud. Also, to some cloud offerings where our mail is, with Office 365 being one of them. Bitglass helps us secure that traffic. It allows us to see where our data is going, who's accessing our data, and what people are trying to access our data.

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.

It's our CASB, our cloud access service broker. It also does our SaaS-based based DLP, our data loss prevention, for our SaaS-based applications. We use it to protect our sensitive information. Since we are a healthcare corporation, we have to do everything we can to keep PHI data from leaking outside of the organization. It's a SaaS offering, but there is an online appliance, a VM server, for the Active Directory sync back to the SaaS.