The solution helps to allow access only to what is explicitly needed. This means restricting access to specific applications rather than providing broad access to multiple resources, some of which may not be necessary for the user. For example, if a user's laptop registers from an unexpected location like the UK, access to certain applications can be blocked based on location or IP address, providing more control.
Restricts access to applications but improvement is needed in integrations
What is our primary use case?
What is most valuable?
The most valuable feature of this product is restricting and controlling what people have access to. If I want a contractor to connect to my network, I can give them access to only the specific things they need without giving them full VPN access to my entire network. That's the main benefit everyone gets from it. The value depends on how many users and applications you have and what you want to share.
What needs improvement?
For areas of improvement, the main issue is with integrations. The Symantec ZTNA comprises many products cobbled together on the back end. Sometimes, the integrations work well; sometimes, they don't. For example, if you want to use two-factor authentication, you need to integrate that into the solution. Or if you want to accept protocols other than web coming to your secure gateway, that's another integration. Supporting different devices like Macs, Samsung phones, or iPhones also requires more integrations. Ensuring all these integrations work properly is an ongoing process and a moving target.
How are customer service and support?
If the product is sold through a distributor, it becomes the first support line. However, things are changing, and even as partners, we sometimes have to go through the distributor's help desk for assistance. This can be challenging because we often know more than the distributor's help desk. Overall, support is becoming a challenge.
How would you rate customer service and support?
Neutral
What was our ROI?
You're going from not having something to implementing it, so there isn't a clear financial return. It's about securing something that was previously insecure. It's like putting bars on your windows at home - how do you quantify the return on that? Unless a customer can say they had a specific number of breaches before that cost them a certain amount, and now they haven't had any since implementing Symantec ZTNA, it's hard to calculate.
What's my experience with pricing, setup cost, and licensing?
Pricing varies depending on the situation. In competitive situations, it's usually priced competitively. Nobody pays the full MSRP. Typically, you negotiate and work with them on the pricing.
What other advice do I have?
Over the last year, I have been working with customers because it's changing and maturing. These things are rolled out in segments and chunks, not all at once. Additional internal work is often required to make it functional, such as properly configuring the active directory. This internal work can take up to three months. The process varies, and implementing Symantec ZTNA quickly is not realistic.
I wouldn't recommend the tool to non-core customers because you won't get the support you need.
I'd rate Symantec ZTNA a seven on a scale of one to ten. They're still integrating different pieces into their solution. The challenge with ZTNA is that different companies implement it slightly differently, with some features present in one product but missing in another. ZTNA is a tricky acronym that companies use, but when you look closely, you find that each vendor might only have some of the expected features.
