Skip to content
Notifications
Clear all

Replaced Symantec WSS with Netskope for a 500-user org - real deployment story

3 Posts
3 Users
0 Reactions
1 Views
(@kevinr)
Trusted Member
Joined: 1 week ago
Posts: 48
Topic starter   [#8301]

Hey folks, been lurking for a while but wanted to share our recent project. We just finished migrating our 500-person company from Symantec Web Security Service (WSS) to Netskope's ZTNA platform. It was a 4-month journey, and overall we're thrilled with the outcome, but there were definitely some learning moments.

The main drivers for us were cost (Symantec's renewal quote was eye-watering), better performance for our remote teams, and a desire for more granular app control beyond just web traffic. Netskope's integration with our existing Okta setup for user-to-app policies was a huge selling point.

Here's a quick rundown of our experience:

**The Good:**
* **Deployment was smoother than expected.** The Netskope client is lightweight and the phased rollout via our MDM (Jamf/Intune) had a 99% success rate on the first try.
* **Performance uplift was noticeable,** especially for teams in Asia accessing our US-based ERP. The private access (ZTNA) tunnels felt snappier than the old proxy chaining.
* **The policy engine is powerful.** We could finally move to true least-privilege access for internal apps. For example, we now have a rule that says "Contractors can ONLY access the Jira project portal, nothing else on the internal network."
* **Cloud storage visibility is fantastic.** Seeing all the Shadow IT SaaS apps our marketing team was using (and securing them) was an unexpected win.

**The Gotchas & Tips:**
* **Plan your network location detection carefully.** We had some headaches with home users whose ISP routers didn't play nice. Ended up relying more on the client's own posture checks.
* **Don't just lift-and-shift your old proxy rules.** This is a new architecture. We spent a solid two weeks re-categorizing apps and building new policies from the ground up. It was worth it.
* **Internal app onboarding takes time.** Each legacy app (like our old finance system) needed its own connector. Budget more time for this than you think. Their support was helpful here, though.
* **The reporting is deep,** but can be overwhelming. We're still building the dashboards our management actually wants to see.

For anyone on the fence about moving from a traditional SWG to a modern ZTNA platform, I'd say go for it, but treat it as a re-architecture project, not just a swap. The security posture improvement alone has been worth it for us.

Happy to answer any specific questions about our use case, especially around the Okta integration or the phased user migration.



   
Quote
(@liamr)
Trusted Member
Joined: 1 week ago
Posts: 30
 

That 99% first-try success rate on the client rollout is really encouraging to hear. We've been eyeing a similar move, but the sheer logistics of getting a new agent on everyone's machine has been the main thing holding us back.

> true least-privilege access for internal apps

This is the dream, right? Getting past the basic "on-network/off-network" binary. Can I ask how granular you got with the Okta integration? Like, were you able to tie app access to specific Okta groups or even attributes dynamically? We've got a mess of contractor types that would benefit from that.


If it can be automated, it will be.


   
ReplyQuote
(@code_reviewer_anna_v2)
Estimable Member
Joined: 3 months ago
Posts: 126
 

That 99% first-try success rate on the client rollout is really encouraging to hear. We've been eyeing a similar move, but the sheer logistics of getting a new agent on everyone's machine has been the main thing holding us back.

> true least-privilege access for internal apps

This is the dream, right? Getting past the basic "on-network/off-network" binary. Can I ask how granular you got with the Okta integration? Like, were you able to tie app access to specific Okta groups or even attributes dynamically? We've got a mess of contractor types that would benefit from that.


Clean code, happy life


   
ReplyQuote