What is our primary use case?
We didn't have a product or resource solution earlier, and we wanted to ensure that all the policies we defend for the internet are common whether working in the office or regularly working from home. So, it should be a standard policy that applies to every user. That would be possible through Netskope Next Gen Secure Web Gateway. It's our version of choice.
How has it helped my organization?
A lot of IT support overheads have gone down because the product also has a feature of ranking websites and Internet-facing applications. Earlier, we managed this with a combination of HDR and firewall. But now, through SWG, it's all automated because we are now able to define policies for a group, for a person, for a location — controls that we wanted to apply earlier to specific requirements are now possible. With Secure Web Gateway, it's only possible and quite simplified. It's a big improvement within our organization.
What is most valuable?
There are a lot of features, but the groups that are created for the policy groups available with Netskope are already relevant to any industry. So grouping the policies is the easiest part and a valuable feature.
We also like the feature where it gets integrated with the DLP and reads the metadata passing through the DLP solution to Netskope.
What we have done is all our lending of any request. So we have worked with three to four components on the SysysysTek. Any request that a user or a device is trying to access corporate resources, it always aligns first on the Netskope. So that way, we are also able to create all these frames for all the accesses to our data center, informing our data center.
What needs improvement?
There is room for improvement in streamlining policies. If I compare it with other products, the groups and are a little different in Netgroup. So what happens is that when you apply a specific Netskope policy, you never know the kind of content it will automatically block, or it will allow. So initially, when doing a pilot, at that time, it takes a lot of time to streamline the policies. So that is one thing they can work on. It should be easy to edit and easy to deploy.
The only thing is now, as part of the NexGen SWG, in the same IPU currently, the KATB and UBA portion is very limited. So maybe Netskope can extend it in future releases. That is point number one.
Point number two, integration with any DLP solution should be very seamless, irrespective of the brand or make of the DLP.
Netskope was also to come up with the endpoint DLP, which was expected in Q4 last year but which is still not out. So, that is the reason why we had to go with a separate DLP. If everything were available in one SKU, we would not have to search outside for the business solution.
So maybe Netskope can work on all four mediums of DLP, which are the endpoint, the network, email, and the web. All four mediums should be covered as part of the DLP solution.
For how long have I used the solution?
I have been using this solution for four months.
What do I think about the stability of the solution?
It is quite stable. I would rate the stability an eight out of ten.
What do I think about the scalability of the solution?
I would rate the scalability an eight out of ten. We are satisfied with the level of scalability. We use 3500 endpoints for Netskope.
We plan to further increase the use of the solution.
How are customer service and support?
It was a challenge to get the architect involved. It took some time for them to put an experienced architect for a specific problem.
So, there is an area of improvement here.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We used a mix of our XDR solution and NetGen Firewall. We were achieving Internet access control through a combination of policies deployed in these two tools, And with Netskope coming in, now we don't need to have the same policies in the firewall and XDR.
It was very difficult to have the same controls when the user is in the office versus when the user is at home. So this is why we wanted a uniform kind of environment. So it only depends on the job business role of a user, so where they are operating from, the policy should remain the same. So we wanted that standardization.
How was the initial setup?
I would rate my experience with the initial setup a seven out of ten, where one is difficult and ten is easy.
It is a bit difficult to deploy. There are a lot of things that need to be configured. We had challenges with the grouping of policies.
It took us around two months to deploy the solution for around 3500 endpoints. Deploying the client in those systems was a challenge for it.
Otherwise, if somebody works for somebody who has a very good patch deployment solution or software deployment solution, then it should not take more than two weeks.
What about the implementation team?
We had a network premier partner doing the deployment for us. We also have our own PMO to handle the project.
So that includes effort from the security team as well as the IT infrastructure team. So, all in all, through the deployment process, we had around eight or nine resources from our site.
And three resources from the partner. There is also a success manager of Netskope involved, who often, after a few days, will come and check if everything is going smoothly or not. Overall, it was a good experience.
We followed a typical project management process where we identified short-term, mid-term, and long-term deliverables. As far as the timeline of the project goes, we have multiple locations, so we deployed the policies at location by location.
Based on the type of users operating out of a certain location, we have created a specific policy for that location. So, location by location is the method that we approach that we do.
Otherwise, it was the same thing as weekly reporting, weekly status reporting, monthly schedule meetings, and ending out of the intergroup challenges.
Maintenance depends on how much the integration with other solutions like SIM and log manager, things like that. But, for my type of organization and the user base, which is, like, 3500, one or two resources should be fine.
What's my experience with pricing, setup cost, and licensing?
I would rate the pricing a four out of ten, where one is cheap and ten is very expensive. It is a cheap licensing fee.
We subscribed to one service, which was to validate the configuration done by a partner. So, the success managers keep on checking if everything is going fine or not. And it's configured properly or not, so and so forth. So we wanted a verification for the principal, so we have subscribed for this service.
Which other solutions did I evaluate?
We evaluated three options, like ZScaler. There were two reasons to choose Netskope.
One reason is that the client of Netskope is very small. So it would be easier to deploy compared to other solutions.
Second, the other solutions were quite costly for the cost we are paying for Netskope. The big license itself was very aggressive. It's very costly. So for the money that we paid, we got a lot of additional components as part of the Netskope.
What other advice do I have?
Every organization has different needs, and we created a very clear list of features that we wanted to have as a must-have in our organization.
Netskope met all our requirements. So we went for Netskope. I would recommend using this solution.
Overall, I would rate the solution an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud