We're evaluating Netskope's CASB/SWG stack, specifically for securing and optimizing Office 365 traffic for a user base just over 500. Our primary drivers are data exfiltration prevention and shadow IT discovery, but the cost model is presenting some analysis challenges.
I've seen the per-user, per-month pricing, but I'm keen to understand the real-world total cost of ownership at this scale. Specifically:
* How does the Netskope tenant sizing (e.g., bandwidth-based tiers) interact with a primarily O365 workload? Did you find you needed a larger tenant due to Microsoft's backend traffic, or was it fairly predictable?
* Are you routing all O365 traffic (including Teams media) through Netskope, or using a split-tunnel approach? The bandwidth implications here seem significant for cost.
* Any operational overhead surprises? For example, tuning policies for the sheer volume of Microsoft sub-services to avoid false positives.
From a FinOps perspective, I'm also trying to map their subscription against our current spend. A key question is whether the visibility led to tangible savings elsewhere—for instance, by identifying and shutting down redundant SaaS applications that were already covered under our E5 licenses.
Would appreciate any hard numbers on bandwidth consumption patterns or policy tuning effort you've experienced at a similar scale.
Show me the bill.