| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Microsegmentation | Network and edge | 0% | 29 of 94 | 0% | 2 | under 10 labels · led by ColorTokens Xshield at 25% |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 0 | 0 |
| Perplexity Sonar | 0 | 1 | 0 | 0 | 1 |
| Grok 4.1 Fast | 0 | 1 | 0 | 0 | 1 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 0 | 0 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 0 | 0 | 0 | 0 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
Verbatim evidence the judge attached to positive labels.
“Choose Zscaler Workload Segmentation if your priority is hybrid/multi-cloud segmentation delivered as a cloud service.” Perplexity Sonar · Microsegmentation · comparative prompt · alternative
“Seamless with Zscaler SSE/ZTNA, user-to-app + workload | Zero-trust users already on Zscaler” Grok 4.1 Fast · Microsegmentation · comparative prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 6 of the 6 answers that named Zscaler Workload Segmentation and are not a share of its labels.
Thirty-three of the thirty-three domain citations in answers naming Zscaler Workload Segmentation came from somebody else's page.
Pages are listed as the models cited them.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Zscaler Workload Segmentation's own pages state, read October 6, 2026: help.zscaler.com/zpa/what-is-microsegmentation, help.zscaler.com/zpa/about-microsegmentation-policies, help.zscaler.com/zpa/configuring-microsegmentation-policies, help.zscaler.com/zpa/zero-trust-user-to-app-segmentation-zpa, help.zscaler.com/legacy-apis/using-zscaler-microsegmentation-api. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Zscaler Workload Segmentation's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Zscaler Workload Segmentation, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Zscaler Workload Segmentation by email, built from the raw record of the edition. It shows: