What is our primary use case?
Netskope Private Access is generally used to migrate customers from legacy VPN solutions they are currently using. We approach them to migrate to us to meet compliance standards and have secure connectivity.
Parallelly, it is used specifically for customers using VPNs, as Netskope Private Access provides outbound connectivity only. We acquire these customers who need this type of service.
What is most valuable?
There are five standout features in Netskope Private Access. First, it has a planned-out architecture, which means there is no inbound connectivity. All user checks, compliance, and security checks are done at the cloud level. There is no inbound connectivity to the network. There is only outbound connectivity.
Second, when a user is provided with Netskope Private Access, they can only access the specific private access granted to them. They don't have the ability to move laterally, which eliminates the risk of unauthorized access.
Third, unlike traditional VPNs that require high maintenance, Netskope Private Access only requires a simple VM that doesn't need much maintenance. There are no additional maintenance charges for that.
Also, unlike other solutions that place VPN concentrators in the environment, Netskope is more cost-effective. The fourth is for the pricing standards of this solution. The support is aligned with standard pricing, whereas VPNs tend to increase pricing due to maintenance charges.
Lastly, when using a VPN, users are limited to a specific bandwidth. For example, if there is a total bandwidth of 50 Mbps, the VPN will divide that bandwidth among the users. In contrast, with Netskope Private Access, each user has their own internet visibility and can access their private apps without bandwidth limitations. This eliminates latency concerns when multiple users require higher bandwidth.
What needs improvement?
Netskope Private Access needs improvement in the on-premises check. When users are out of the network, it's self-explanatory that they will be connected to their private app via the network. The area for improvement is that Netskope Private Access currently supports only one DNS mapping for an IP address.
This means that when users are on-premises, Netskope needs to turn off its Private Access tunnel since users can access the private apps locally.
Currently, Netskope Private Access allows mapping only one DNS server. If a user uses a secondary DNS on-premises, Netskope fails to disconnect them. This is an issue that needs to be addressed.
For how long have I used the solution?
I have been using this solution for two years. I have been involved in the implementation and providing support. Currently, I am working on POCs and have been appointed as a previous lead for Netskope.
What do I think about the stability of the solution?
In terms of stability, I would rate it around nine out of ten. The only reason I'm deducting one point is because of the occasional switch between data centers.
With Netskope Private Access, the traffic is routed through a tunnel to the Netskope cloud, which then directs it to the data center. If a user is connected from a mobile location, they will hit the nearest data center. However, in rare cases where the data center fails, the traffic needs to be rerouted to a secondary process, causing a temporary disconnection for the NetSuite Private Access users.
Although this is uncommon, there was one incident in the past 90 days where the data center failed, but the user was automatically switched to another data center. The only inconvenience occurred because their ongoing session was long. Overall, stability is excellent, and I'm using it with confidence.
What do I think about the scalability of the solution?
I would rate the scalability of Netskope Private Access as a ten. It's not a problem because a single Netskope publisher has a throughput of 500 Mbps and can handle up to 32,000 concurrent connections. It works in an active fashion, so even if one publisher goes down, another one automatically switches to ensure there is no latency or disruption.
In terms of scalability, it's excellent. We have several companies as customers. In one specific company, there are approximately 6,000 users. So our organization can handle a scale of 6,000 to 8,000 users without any issues, so it can handle even larger deployments.
How are customer service and support?
Regarding technical support, there were a few issues. Earlier, Netskope Private Access could be deployed and sent to a provider with different prerequisites, including CentOS. Right now, the current requirement specifies that CentOS is no longer supported with Netskope Private Access. Users now need to have Ubuntu. In this case, there were challenges for our customers who needed to migrate their existing architecture or face registration problems. Our support team assisted them with these issues and provided the necessary technical support, especially regarding connectivity loss and resolution. Once the migration was completed, there were no further problems in the reference zone.
How was the initial setup?
The initial setup of Netskope Private Access is pretty simple and straightforward. You just need to register one machine, create policies, and you're good to go.
The user interface of Netskope Private Access is very user-friendly, and the provided documentation is easy to follow. It allows anyone to create a private app and manage accessibility. In terms of initial setup, Netskope Private Access is currently leading compared to other solutions.
What about the implementation team?
Netskope Private Access is deployed in two ways. Firstly, as a Netskope client on users' machines who want to access their private apps through Netskope Private Access. Secondly, Netskope Publisher can be deployed on various platforms, including public clouds like Azure, AWS, GCP, or even third-party clouds like Oracle Cloud. It can also be hosted on-premises. Users generally connect to the publisher through the Netskope Cloud to access their desired services.
The deployment of Netskope Private Access is quite fast. It typically takes around 30 minutes. Within this time, I can deploy the publisher in just 15 minutes, then spend the next five minutes defining policies and configuring the app. The remaining five minutes are used to apply the policies and ensure the desired level of access. Overall, it's a straightforward and efficient process.
What's my experience with pricing, setup cost, and licensing?
When it comes to pricing, Netskope Private Access is relatively cheap compared to other solutions. We highly recommend it because it is cheap. It is a per-user-based per-year license.
The pricing is based on a per-user basis, making it cost-effective, especially for organizations with a large number of users. This pricing model is not a problem for us, and we find it to be very reasonable compared to other solutions. In fact, Netskope has started acquiring existing customers in India due to its competitive pricing.
Which other solutions did I evaluate?
We are a partner with Cisco. Our company is partnered with JetBlue, Flex, CrowdStrike, vScaleability, SentinelOne, Fortinet, Forescout, and Zscaler. We also deliver customers with Netskope. However, when comparing the pricing of different solutions, we find Netskope to be cheaper. Since we sell both Netskope and other products, we have a good understanding of the pricing models offered by each provider.
What other advice do I have?
Overall, I would rate the solution a nine out of ten.
*Disclosure: My company has a business relationship with this vendor other than being a customer: