Netskope Reviews

For now, we are scanning all the HTTP traffic with the cloud-based solution, the cloud broker solution. We are using it as a network proxy. It will detect all the data you are using. Let's say you go to Google Drive to try to upload something. In our case, we are putting up some rules or restrictions so that you can't upload PDFs or Word files, or maybe you can add Word files with limitations, like without any personal information, including name, pin number, date of birth. It's more like we are controlling the PII, the personal information with the solution, so that we restrict users from uploading whatever they want on the internet.

The solution itself is good because it categorizes many websites on its own, like the website or solution you trust. For instance, Yahoo is a good website. You can let your employees use Yahoo, but let's say a website like yandex.com is a little bit fishy, so they will put it into a category like server content. We can put in rules according to this. We can only allow the website with Netskope first.

We have to pay extra for some of those features, but we can connect our infrastructure like GCB. We can connect our instance via API so that Netskope itself scans whatever in our GCB storage or Azure Block storage. If someone is storing PII information, it can declare some alerts or restrict access to that particular file. It's mostly for this kind of solution, but there are many other things that you can do with the solution.

We have more than 30,000 workstations. The client version is 90, but we are using 87. Every three or four months, we do an installation for all the clients and workstations. That's maybe why we are not on the latest client version, but it works fine. There haven't been any problems with that. They launch one new version every month.

Normally on your side, you don't need anything. You only need to install the client on your workstation. After that, it's up to you. If you have everything already on cloud, like if you are using Azure AD, you can connect your Azure-ready account with their account for the same purposes and upload all the data of your users so that their solutions know about your environment. If you are not using cloud, you can provide an Excel list of all your users so they can register those users so you aren't paying more than you are consuming. You can install the agents on 1,000 PCs, but they are only working with the users and environment they are deployed on.

If I have 500 users and install on 1,000 PCs, I'm only paying for 500 users because now they work from home. Everyone has one Mac, one Windows device, or maybe one Linux device, but they are using the same username with the organization. We are paying the license for one user, even if we are using the client on multiple devices. The working environment is not a big mess. If you're on hybrid or 100% cloud based, or even if you are 100% in-house in your data center, you can go with the solution. There aren't any limitations.

If you implement the solution, it will give you visibility. If you have 1,000 or 50,000 people working in your environment, you don't know what solutions people are using. Personally, I'm using OneNote and Microsoft Office, but someone might be using a text file or third party software, or using a browser extension just to take notes. 

We don't know how much we can trust third party applications. The product itself provides visibility to us. When we started back in 2019, we activated the solution for everyone, but this is not the best way for 30,000 users in one shot because we started blocking people and the work environment because people were using their own solutions and software. Netskope doesn't know those softwares so we have to integrate with them and with the third party, for which we are paying the license. Netskope says, "Okay, this is the server. We are blocking the server," but we don't know if we can trust this one or not. 

After talking with the other teams, we realized, "No, we are paying the license for it. This is legit, so we don't have to block it." 

When we started deployment, each month we deployed the traffic for 1,000 people. When it was done, we could see what they were using, consuming, and what we were blocking.

This way, we can change our policies. We try to allow the legit solutions and third party applications that we are paying the license for. Then we go to the next thousand. Then we discover what these people are doing and the applications they're using. When people tell us that they don't have access to their Gmail, we tell them that we cut out Gmail because we are only using the Microsoft services, so there is no Gmail, unless there is a reason for it.

Netskope provides visibility in our case for the deployment.

The solution is useful for remote workflow access.

Netskope’s CASB provides good visibility of the applications being used. We can use Shadow IT based on the traffic. DLP and CASB are valuable features. The tool provides extensive DLP features. We can create any level of policies and protect our data on-premise or cloud. The tool integrates with all the components very well.

Most of our customers use Netskope for application navigation and the protection of the public cloud, such as Office 365. We primarily work with it as a substitution for URL filtering, but the SASE solution provides more than just URL filtering.

Netskope provides real-time protection as all traffic is analyzed in line. With the client on the device communicating with the Netskope cloud, it allows for immediate protection. 

Netskope is cloud-native, enabling differentiation of tenants in cloud applications, whether they are enterprise or personal, and provides control over shadow IT access. 

It also has a behavior engine with robust rules and machine learning capabilities, including image analysis with OCR capabilities.

Our one use case involved shadow IT. We had numerous cloud applications being used by the business without the IT team's awareness. A lot of data was being exchanged with these cloud applications. 

Another use case centered around our corporate applications, specifically Google Workspace. We integrated Google Workspace with Netskope to protect our cloud usage and data, including email IDs and Google Drive storage.

These are the use cases we applied the tools to.

The benefits revolved around effectively addressing the use cases using Netskope. Regardless of user location, as long as they were connected to the internet, their data remained protected at all times. These were the major benefits we obtained.

I use Netskope for cloud-based security within our organization's multi-cloud environments. It helps with ease of deployment and configuration, enabling us to manage security policies and integrate them with other solutions like identity providers.

Netskope has allowed us to effectively configure security policies and manage them across our environment while providing a secure and efficient solution.

We use the tool to control the use of our email going outside.  We use it to secure our data. We use it for data exfiltration, enforce policies for users who use both personal and corporate accounts, and ensure PCI compliance. We also use it to block malware by detecting and blocking any malware in cloud services immediately. Additionally, we monitor privileged accounts to prevent unauthorized access to our resources. We use it to protect our privileged accounts in Microsoft Azure.

The solution provides information about third-party applications registered to our corporate email address and alerts us when users enroll in other applications using their work email.

The tool helps us detect threats and provides insights. Then, we take necessary measures to ensure users have MFA enrolled and take other security steps.

We are an airline, so our users frequently move between locations. For example, a pilot might log in from one country in the morning and another within a few hours. Netskope helps us guard against threats by detecting if a data exfiltration attempt occurs from a specific location.

A feature that was valuable was the built-in website classification or safety ratings. Different websites would be rated according to analyses that the Netskope team had done, and we built policies on some of those scores. If the website scored less than a certain percentage, then we would have a different user experience around how the site would interact with the clients.

It needed some fine-tuning on core business sites that we used, which were sensitive to what we term a man-in-the-middle certificate by design. Some sites were not tolerant because they presented as potentially malicious. So, we just had to make some tweaks so that it would bypass or interpret it.

The features that we would like to see are available but require additional investment. We wanted more of the CASB type feature set, which was at a higher subscription cost, and we didn't have budget for it. We just went with their standard offering, which was the secure web gateway.

We use Cisco Umbrella and plan to replace it with Netskope. We will start with the security model and other policies. 

We use Cisco VPN for remote access. Additionally, we have started implementing Netskope with a strong focus on security. Our primary goal is to protect users from accessing malicious sites. We also plan to implement DLP based on our data, as data security is our main concern.

The solution offers granular control over uploads and downloads. Previously, we lacked monitoring and control over downloads from malicious sites, but now, with Netskope, we can block such downloads. We are currently in the testing phase of implementing DLP, specifically for personally identifiable information data. We don't want it to be uploaded to the cloud. 

I'm currently involved in integrating Netskope with SentinelOne in our organization. The goal is to consolidate our alert monitoring by setting up a virtual machine and establishing threat exchange protocols. This integration allows us to use a single console to monitor alerts from both Netskope and SentinelOne, enabling better correlation of security incidents.