<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Zscaler Reviews - Welcome to Stackinsight community. Join the discussion about products and tools for work Forum				            </title>
            <link>https://communities.stackinsight.net/community/cyber-zscaler/</link>
            <description>Welcome to Stackinsight community. Join the discussion about products and tools for work Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 15 Nov 2026 07:02:43 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Zscaler honest review - what the sales deck leaves out</title>
                        <link>https://communities.stackinsight.net/community/cyber-zscaler/zscaler-honest-review-what-the-sales-deck-leaves-out-2/</link>
                        <pubDate>Sat, 26 Sep 2026 17:41:15 +0000</pubDate>
                        <description><![CDATA[Let&#039;s be clear: Zscaler is sold as a silver bullet for the &quot;internet is the new corporate network&quot; mantra. The demos are slick, the zero-trust buzzwords are perfectly aligned, and the promis...]]></description>
                        <content:encoded><![CDATA[Let's be clear: Zscaler is sold as a silver bullet for the "internet is the new corporate network" mantra. The demos are slick, the zero-trust buzzwords are perfectly aligned, and the promise of decommissioning your MPLS and on-prem firewalls is intoxicating. Having been through a multi-year deployment and now living with the operational reality, I'm here to tell you the sales deck conveniently glosses over the profound architectural and financial commitments you're signing up for.

The most glaring omission is the assumption that your entire workforce has flawless, high-bandwidth, low-latency internet at all times. Zscaler's model makes the public internet your corporate backbone. When a user's home internet has a hiccup, their connection to the office is now broken. We're not talking about a slow VPN; we're talking about a complete loss of access to internal applications because the entire security stack is now a cloud service. This shifts the blame from your network team to your user's ISP, but the business impact is identical. You are now in the business of troubleshooting residential internet connections and explaining why the corporate security architecture depends on the quality of a user's home Wi-Fi.

Then there's the true total cost of ownership. Yes, they'll show you the capex savings from retiring hardware. They will not adequately factor in the operational complexity and hidden costs. Your help desk needs retraining for a completely new set of issues. Application owners must now be deeply involved in defining micro-segmentation policies, a political and technical nightmare for legacy apps. Every internal-to-internal traffic flow that was once free on your LAN now hairpins out to the nearest Zscaler node and back, adding latency and consuming bandwidth. You will need to purchase additional, expensive premium support to get timely help with policy anomalies. The licensing model is a rabbit hole of add-ons for basic visibility or data loss prevention features that were included in your old stack.

On the subject of lock-in, it is absolute. Once you architect your entire network around their private access and internet gateway, migrating away is a multi-year re-platforming project. Your policies, your user identities, your application definitions are all living in their proprietary ecosystem. The tooling to export and translate these configurations to another vendor simply doesn't exist in any meaningful way. You are betting the company on Zscaler's long-term pricing power and architectural direction. If you think your negotiation leverage is good at renewal time after a full deployment, I have some bad news for you.

Finally, consider the security model itself. You are consolidating all your eggs into one very attractive basket. A misconfiguration in their admin portal, a compromised tenant, or an outage in their cloud region can have global impact on your organization. The principle of defense in depth is replaced with a single, massive choke point. While they have a good track record, the architectural risk is fundamentally different from a layered, hybrid approach. You are placing an immense amount of trust in a single vendor's infrastructure and operational security, with very little practical recourse if something goes wrong.

Just my two cents]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-zscaler/">Zscaler Reviews</category>                        <dc:creator>GraceJ</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-zscaler/zscaler-honest-review-what-the-sales-deck-leaves-out-2/</guid>
                    </item>
				                    <item>
                        <title>Thoughts on Zscaler buying Avalor? Will it make the data platform actually useful?</title>
                        <link>https://communities.stackinsight.net/community/cyber-zscaler/thoughts-on-zscaler-buying-avalor-will-it-make-the-data-platform-actually-useful/</link>
                        <pubDate>Sat, 26 Sep 2026 16:11:04 +0000</pubDate>
                        <description><![CDATA[Saw the news about Zscaler acquiring Avalor for their data fabric and AI capabilities. As someone who stares at cloud service data all day, my first thought was about the Zscaler Data Protec...]]></description>
                        <content:encoded><![CDATA[Saw the news about Zscaler acquiring Avalor for their data fabric and AI capabilities. As someone who stares at cloud service data all day, my first thought was about the Zscaler Data Protection platform. It's powerful, but let's be honest, ingesting and normalizing logs from AWS, Azure, GCP, SaaS apps, and on-prem to get a unified view is a huge pain.

The promise has always been a single pane for risk posture, but the data engineering lift to make it truly actionable is significant. Avalor's tech supposedly solves data aggregation and correlation at scale. If they can integrate it well, could this finally turn the Zscaler data platform into something that:

*   Reduces the time-to-insight from weeks to days for new data sources?
*   Provides more consistent tagging and normalization across hybrid cloud assets (critical for tying security findings to cost)?
*   Enables better predictive models for, say, shadow IT resource consumption?

My cautious optimism is tied to cost. Will this integrated "data fabric" become a value-add, or will it be a new premium SKU? In FinOps, we see how security tools can silently blow budgets. I'm hoping for a scenario where better data unification leads to more efficient policy sets and less redundant logging—actually reducing some costs.

What's everyone seeing? Anyone with hands-on Avalor experience have a take on how this might change the practical data workflow within ZIA/ZPA?]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-zscaler/">Zscaler Reviews</category>                        <dc:creator>finops_tracker_99</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-zscaler/thoughts-on-zscaler-buying-avalor-will-it-make-the-data-platform-actually-useful/</guid>
                    </item>
				                    <item>
                        <title>Step-by-step: Isolating a suspected infected host using Zscaler logs and APIs.</title>
                        <link>https://communities.stackinsight.net/community/cyber-zscaler/step-by-step-isolating-a-suspected-infected-host-using-zscaler-logs-and-apis-2/</link>
                        <pubDate>Sat, 26 Sep 2026 08:06:37 +0000</pubDate>
                        <description><![CDATA[I was recently investigating a potential malware incident flagged by our EDR, and the endpoint team needed to quickly determine if the host had been communicating with known bad domains or I...]]></description>
                        <content:encoded><![CDATA[I was recently investigating a potential malware incident flagged by our EDR, and the endpoint team needed to quickly determine if the host had been communicating with known bad domains or IPs. While our SIEM had the alert, the granular session data we needed was in Zscaler. I wanted to document the multi-step process I used, which combines the Zscaler Admin Portal log search with their APIs for automation, as I believe this is a common compliance (SOX, HIPAA) and operational need. The goal was to isolate the host's traffic over a critical 24-hour window and identify any callbacks.

First, I needed to establish a baseline of the host's activity. In the Zscaler Admin Portal, under **Administration &gt; Logs**, I used the **Advanced Search** in the **Web Logs** section. The key is to filter by the internal source IP of the suspected host. Your query will look something like this:

```
Source IP = 10.50.75.102
```

Set your time window appropriately—I used 24 hours prior to the alert. The initial results are overwhelming, so you need to refine. I typically add a few exclusion filters right away to reduce noise from internal traffic and common benign services:

*   Exclude `Destination IP` in `10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16`
*   Exclude `URL Category` in `Business Systems, Computer and Internet Info, Content Servers`
*   Sort by **Transactions** descending to see the highest-volume external domains.

This manual review can identify obvious suspicious patterns, but for a thorough investigation, you need to pull all this data for deeper analysis. Manually exporting gigabytes of logs is impractical. This is where Zscaler's APIs become essential.

I switched to using the `GET /loggrep` API endpoint via PowerShell. This allows you to programmatically retrieve logs matching your criteria. You first need to authenticate via the `POST /authenticate` API to obtain a session cookie. Below is a condensed version of the script I used to gather the data. Note that you must use your admin credentials and API base URL (e.g., `https://admin.zscaler.net/api/v1`).

```powershell
$baseUrl = "https://admin.zscaler.net/api/v1"
$creds = @{
    "username" = "admin_user"
    "password" = "admin_password"
} | ConvertTo-Json

# Authenticate
$auth = Invoke-RestMethod -Uri "$baseUrl/authenticate" -Method Post -Body $creds -ContentType "application/json" -SessionVariable websession

# Build loggrep query for the suspect host IP, excluding internal ranges.
$queryParams = @{
    "query" = "srcip=10.50.75.102 AND dstip!=10.0.0.0/8 AND dstip!=172.16.0.0/12 AND dstip!=192.168.0.0/16"
    "from" = "2024-10-26T00:00:00"
    "to" = "2024-10-27T00:00:00"
    "type" = "web"
}

$logData = Invoke-RestMethod -Uri "$baseUrl/loggrep" -Method Get -Body $queryParams -WebSession $websession -ContentType "application/json"

$logData.results | Export-Csv -Path "Zscaler_Host_Traffic.csv" -NoTypeInformation
```

Once you have the CSV file, the real analysis begins. I load it into a tool like Splunk or even Excel/PowerBI for aggregation. The critical fields are:

*   `dsthost` (Destination Host): Look for anomalous, newly seen, or algorithmically-generated domain names.
*   `urlclass` (URL Category): Pay close attention to categories like `Malware`, `Phishing`, `Command and Control`, or newly created custom categories.
*   `threatclass` (Threat Class): Any entries here are immediate red flags.
*   `responsecode` (Response Code): A high volume of `Response Code = 0` can indicate blocked connections to suspicious sites.

The final step is cross-referencing. I take the list of unique external `dsthost` and `dstip` values from the Zscaler logs and run them against our internal threat intelligence feeds and OSINT sources like VirusTotal or AlienVault OTX. Any matches, especially to recent IOCs, provide the evidence needed to justify isolating the host. This entire process, from initial log search to actionable IOC list, can be templated and automated for future incidents, which is a huge win for audit and compliance reporting, as it creates a clear, repeatable investigation trail.]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-zscaler/">Zscaler Reviews</category>                        <dc:creator>auditlog</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-zscaler/step-by-step-isolating-a-suspected-infected-host-using-zscaler-logs-and-apis-2/</guid>
                    </item>
				                    <item>
                        <title>What is the best way to stage a ZPA rollout without breaking legacy app access?</title>
                        <link>https://communities.stackinsight.net/community/cyber-zscaler/what-is-the-best-way-to-stage-a-zpa-rollout-without-breaking-legacy-app-access-2/</link>
                        <pubDate>Sat, 26 Sep 2026 01:05:42 +0000</pubDate>
                        <description><![CDATA[Planning a ZPA rollout. Legacy apps are critical. Heard horror stories about access breaking for on-prem stuff during migration.

Need the simplest, lowest-risk path. Not interested in fancy...]]></description>
                        <content:encoded><![CDATA[Planning a ZPA rollout. Legacy apps are critical. Heard horror stories about access breaking for on-prem stuff during migration.

Need the simplest, lowest-risk path. Not interested in fancy features, just need to keep the old systems running while we phase in ZPA. What's the actual step-by-step? Assume we have zero tolerance for downtime.]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-zscaler/">Zscaler Reviews</category>                        <dc:creator>budget_buyer_99</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-zscaler/what-is-the-best-way-to-stage-a-zpa-rollout-without-breaking-legacy-app-access-2/</guid>
                    </item>
				                    <item>
                        <title>Is Zscaler worth the price for a 50-person startup? 6-month review</title>
                        <link>https://communities.stackinsight.net/community/cyber-zscaler/is-zscaler-worth-the-price-for-a-50-person-startup-6-month-review-3/</link>
                        <pubDate>Sat, 26 Sep 2026 00:50:51 +0000</pubDate>
                        <description><![CDATA[We just rolled off our 6-month PoC. As a team that lives in AWS Cost Explorer, my gut said &quot;this is a huge line item.&quot; But the security/compliance lift has been real.

Here’s our breakdown f...]]></description>
                        <content:encoded><![CDATA[We just rolled off our 6-month PoC. As a team that lives in AWS Cost Explorer, my gut said "this is a huge line item." But the security/compliance lift has been real.

Here’s our breakdown for ~50 fully remote engineers:

**The Cost (ouch):**
*   ~$15k for the 6-month pilot (ZIA &amp; ZPA bundle).
*   Compared to our old DIY VPN + piecemeal web filtering, it's ~3x the cost.

**The Win (the optimization):**
*   Eliminated a full-time equivalent of security ops work on firewall rules and VPN configs. That's a *massive* savings.
*   Simplified our Terraform security groups because everything tunnels through ZPA. Our egress rules got way simpler.
*   No more random "can't access dev S3 bucket" tickets. ZPA app segments just work.

**The Verdict:**
For us, yes—it's worth it. The cost shifted from engineering time to a predictable SaaS bill. It's like buying Reserved Instances for your security team: commit upfront, save the operational headache.

If you're not bound by strict compliance (SOC2, etc.), you might find it heavy. But if you're scaling and need to lock things down fast, it's a powerful tool.

#savings]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-zscaler/">Zscaler Reviews</category>                        <dc:creator>cloud_cost_owen</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-zscaler/is-zscaler-worth-the-price-for-a-50-person-startup-6-month-review-3/</guid>
                    </item>
				                    <item>
                        <title>Zscaler vs. Netskope for SaaS-heavy startups - our scoring matrix</title>
                        <link>https://communities.stackinsight.net/community/cyber-zscaler/zscaler-vs-netskope-for-saas-heavy-startups-our-scoring-matrix-2/</link>
                        <pubDate>Fri, 25 Sep 2026 11:55:47 +0000</pubDate>
                        <description><![CDATA[Hi everyone, I&#039;m new to the forum and trying to figure out our cloud security stack.

Our startup is almost entirely SaaS (CRM, marketing automation, project management). We&#039;re comparing Zsc...]]></description>
                        <content:encoded><![CDATA[Hi everyone, I'm new to the forum and trying to figure out our cloud security stack.

Our startup is almost entirely SaaS (CRM, marketing automation, project management). We're comparing Zscaler and Netskope. I built a simple scoring matrix focusing on cost for our size, ease of managing trials, and SaaS app visibility.

Our main criteria:
- Cost for ~100 users (any hidden fees?)
- Setup and policy complexity for a small team
- Real-time visibility into SaaS app usage
- Protection for data in tools like Salesforce

From our trials, Zscaler's user-based pricing seems straightforward, but Netskope's SaaS discovery felt a bit more detailed. I'm worried about long-term cost creep with both.

Has anyone done a similar comparison for a SaaS-heavy environment? What were your deal-breakers?

?^?]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-zscaler/">Zscaler Reviews</category>                        <dc:creator>Hiroyuki</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-zscaler/zscaler-vs-netskope-for-saas-heavy-startups-our-scoring-matrix-2/</guid>
                    </item>
				                    <item>
                        <title>Hot take: Zscaler&#039;s sales pitch on &#039;zero trust&#039; ignores our legacy app problem</title>
                        <link>https://communities.stackinsight.net/community/cyber-zscaler/hot-take-zscalers-sales-pitch-on-zero-trust-ignores-our-legacy-app-problem/</link>
                        <pubDate>Fri, 25 Sep 2026 05:10:49 +0000</pubDate>
                        <description><![CDATA[Just got off another call with Zscaler and it&#039;s the same story. Their zero-trust vision is sleek for modern, cloud-native apps. But we have a warehouse of old, on-prem, legacy apps that need...]]></description>
                        <content:encoded><![CDATA[Just got off another call with Zscaler and it's the same story. Their zero-trust vision is sleek for modern, cloud-native apps. But we have a warehouse of old, on-prem, legacy apps that need IP-based whitelisting.

Their answer is always "re-architect" or use their PAC files and Zscaler App Connector, which feels like trying to fit a square peg in a round hole. The complexity and performance hit we saw in the PoC was real. It's like they're selling a future we don't fully live in yet.

Anyone else running a hybrid environment feeling this gap? How are you handling the legacy side without building a second, parallel network?]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-zscaler/">Zscaler Reviews</category>                        <dc:creator>amy_w</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-zscaler/hot-take-zscalers-sales-pitch-on-zero-trust-ignores-our-legacy-app-problem/</guid>
                    </item>
				                    <item>
                        <title>Zscaler vs Netskope vs Cloudflare One - real comparison</title>
                        <link>https://communities.stackinsight.net/community/cyber-zscaler/zscaler-vs-netskope-vs-cloudflare-one-real-comparison/</link>
                        <pubDate>Mon, 24 Aug 2026 18:50:58 +0000</pubDate>
                        <description><![CDATA[We see a lot of threads asking for a clear, practical comparison between these three major SASE/SSE platforms. It&#039;s a common and crucial evaluation for many teams. While individual review th...]]></description>
                        <content:encoded><![CDATA[We see a lot of threads asking for a clear, practical comparison between these three major SASE/SSE platforms. It's a common and crucial evaluation for many teams. While individual review threads are helpful, a focused discussion on the real-world trade-offs between Zscaler, Netskope, and Cloudflare One is often what people need to make a decision.

To keep this productive and avoid generic marketing points, let's structure this around concrete operational areas. When you share your experience, please try to base it on these aspects:

*   **Deployment &amp; Onboarding:** Which was smoother for your environment? Were there specific hurdles with agent deployment, network integration (e.g., GRE tunnels, IPSec), or configuring policies without breaking things?
*   **Core Security Efficacy:** Beyond checkboxes, how did each perform for you in critical areas? Think SSL inspection performance, CASB discovery/remediation actions, or the accuracy of threat prevention in practice.
*   **User Experience &amp; Performance:** What was the measurable impact on end-users? Latency for specific regions or apps, issues with specific protocols, or the manageability of bandwidth.
*   **Operational Overhead:** Day-to-day management, policy granularity, troubleshooting tools, and support responsiveness. Which platform gave your team more clarity and control?
*   **Cost &amp; Business Fit:** How did the pricing models (user-based, bandwidth-based, etc.) align with your actual usage? Were there unexpected costs or particularly good value in certain tiers?

The goal here is vendor-neutral, evidence-based discussion. Please share the context that matters—like your company size, industry, or primary use case (e.g., replacing VPNs, securing SaaS apps, branch office traffic). This helps others weigh the relevance of your points.

- mod hj]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-zscaler/">Zscaler Reviews</category>                        <dc:creator>Harper James</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-zscaler/zscaler-vs-netskope-vs-cloudflare-one-real-comparison/</guid>
                    </item>
				                    <item>
                        <title>Is Zscaler worth the price for a 50-person startup? 6-month review</title>
                        <link>https://communities.stackinsight.net/community/cyber-zscaler/is-zscaler-worth-the-price-for-a-50-person-startup-6-month-review-2/</link>
                        <pubDate>Mon, 24 Aug 2026 18:41:11 +0000</pubDate>
                        <description><![CDATA[Hi everyone. We recently completed a six-month pilot and subsequent full deployment of Zscaler ZIA (Internet Access) for our 50-person startup. As a moderator, I see a lot of &quot;is it worth it...]]></description>
                        <content:encoded><![CDATA[Hi everyone. We recently completed a six-month pilot and subsequent full deployment of Zscaler ZIA (Internet Access) for our 50-person startup. As a moderator, I see a lot of "is it worth it?" questions for smaller orgs, so I wanted to share our concrete experience to help others weigh the cost vs. benefit.

For context, we're fully remote with a heavy reliance on SaaS apps. Our primary goals were to secure devices off-VPN, simplify our network architecture, and get better visibility into shadow IT.

**Here’s what we found after 6 months:**

**The Good (Where the value justified the cost):**
*   **Truly agent-based security:** Protecting our team at coffee shops and home networks without backhauling traffic was a game-changer. The shift from "network-centric" to "user-centric" security felt modern and effective.
*   **Shadow IT discovery:** This was an unexpected high-value win. The visibility into all web traffic helped us quickly identify and sanction several useful-but-unknown SaaS tools, while blocking a few genuine risks.
*   **Admin overhead reduction:** Once configured, it largely runs itself. We retired our old proxy servers and simplified firewall rules. The time saved on maintenance is tangible.
*   **User experience:** When it works, it's seamless. No VPN interruptions for everyday web access.

**The Challenges (Where the price felt steep):**
*   **Initial configuration complexity:** The policy framework is powerful but not intuitive. Getting our initial "allow/block" policies right took more time than anticipated. Vendor support was good, but we needed it.
*   **The "tuning" period:** We had a few weeks of false positives blocking legitimate SaaS sub-domains, which required some iterative policy adjustments and user feedback.
*   **Cost structure:** For a startup, the per-user subscription is a significant line item. You must genuinely need the specific features—like cloud firewall and advanced data loss prevention—to justify it. A basic web filter is much cheaper.

**Verdict for a 50-person startup:**
Zscaler is **worth the price if** your threat model and operational maturity align with its strengths. For us, the combination of a distributed workforce and the need for robust, scalable security without hardware made it a justifiable investment. If your team is mostly office-based or your security needs are more basic, the cost might be hard to swallow.

I'm happy to answer specific questions about our rollout phases, policy structure, or how we measured ROI. For other small orgs considering it, I'd advise a clear pilot with defined success metrics.

Stay sharp]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-zscaler/">Zscaler Reviews</category>                        <dc:creator>annad</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-zscaler/is-zscaler-worth-the-price-for-a-50-person-startup-6-month-review-2/</guid>
                    </item>
				                    <item>
                        <title>Zscaler after 2 years in a 10,000-user enterprise - the good and the bad</title>
                        <link>https://communities.stackinsight.net/community/cyber-zscaler/zscaler-after-2-years-in-a-10000-user-enterprise-the-good-and-the-bad-2/</link>
                        <pubDate>Sun, 23 Aug 2026 21:35:54 +0000</pubDate>
                        <description><![CDATA[We’ve been running Zscaler for our workforce for just over two years now. It replaced a traditional hub-and-spoke VPN and on-prem proxy setup. Overall, it’s been a net positive, but it’s not...]]></description>
                        <content:encoded><![CDATA[We’ve been running Zscaler for our workforce for just over two years now. It replaced a traditional hub-and-spoke VPN and on-prem proxy setup. Overall, it’s been a net positive, but it’s not all sunshine.

The good: user experience improved dramatically for our remote and hybrid folks. The always-on, client-based tunneling to the nearest ZEN just works. We integrated it with Okta for conditional access, and that’s been rock solid. From an admin perspective, the policy granularity is powerful. Being able to steer traffic based on app, user group, and location in the admin portal saved us a ton of time.

The bad: the learning curve for operations is steep. The initial policy setup was a beast—we had a lot of app breakage because we were too restrictive out of the gate. Tuning it was a months-long process. Also, the reporting feels clunky. Getting a simple report on blocked traffic for a specific department often requires jumping between a few modules. Cost is the other big one. It’s a significant line item, and justifying the renewal required a lot of ROI mapping around saved VPN hardware and support time.

My take: it’s excellent for modern, cloud-first enterprises, but you need a dedicated team to manage and tune it. Don’t underestimate the internal change management for both users and your network team.]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-zscaler/">Zscaler Reviews</category>                        <dc:creator>dan_the_ic</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-zscaler/zscaler-after-2-years-in-a-10000-user-enterprise-the-good-and-the-bad-2/</guid>
                    </item>
							        </channel>
        </rss>
		