A WAF (Web Application Firewall) operates at the perimeter, analyzing traffic as it crosses between external networks and your internal network towards your web servers. The browser environment is a separate execution context that happens on your users' devices, completely outside your network perimeter. Once JavaScript code reaches the browser and begins to execute, it's operating in an environment that your WAF has no visibility into or control over. By design, a WAF is ineffective against client-side threats.
Can cside work alongside my existing WAF without conflicts?
We monitor an entirely different dimension of the application stack; hence, there is no interference.
Does cside's JavaScript proxy add latency like a WAF does to all traffic?
cside only adds 8-20 milliseconds to specific dynamic JavaScript files we proxy, with static scripts cached for faster loading.
How does cside's approach compare to the complexity of managing a WAF?
cside is much simpler because we're only handling JavaScript files, not your entire web infrastructure.
What happens if cside's proxy goes down? Will my website break?
Your website will continue working as intended with our fail-open design and 99.99% uptime SLA.