| While web security as SaaS is a very compelling proposition, delivering a satisfactory solution is a major challenge. The biggest technical problems to be solved are: |
| Rerouting traffic can create significant latency for the end user |
| Latency Due to Rerouting Traffic |
|
| SaaS Web Security requires traffic to be rerouted to the SaaS vendor’s data center to be scanned. Latency is especially important for web traffic. Latency in SaaS email security, for example, goes largely unnoticed—the user can receive an email several minutes late. However, in the case of HTTP, an interactive protocol, rerouting traffic to a SaaS vendor’s data center can add significant latency, ranging from hundreds of milliseconds to a few seconds, and making the SaaS solution unacceptable. Learn how Zscaler minimizes rerouting latency. |
 |
| Latency Introduced by a Proxy Server |
 |
| The only reliable way to inspect traffic is by using proxy architecture. Most traditional proxies designed for enterprises handle about 100 Mbps and introduce significant latency, especially if they start performing content inspection. Learn how Zscaler solves the proxy latency problem. |
| Consolidating Web Logs |
|
| Logs generated by web traffic can be incredibly large. A typical Fortune 500 company can have 50-100 GB of web logs per day. One of the biggest challenges is combining web logs from multiple locations to provide enterprises a consolidated and real-time view of web traffic and vulnerabilities. Learn how Zscaler has solved the web log and reporting problem using its NanoLog technology. |
 |
|
| In order to overcome these challenges, a web security SaaS service requires a multi-tenant architecture with a distributed, global network of high-performance proxies. |
| |
| |
The Cloud Security Company™
