WAF sits in front of your website and looks at everything that passes through it. cside is different. Instead of touching all your traffic, it only targets third-party scripts you choose to monitor, while the rest of your site runs as normal. We also offer an unproxied approach, an option that allows a customer to pick specific script sources it deems reliable and proxy everything else as a sandbox. Your users are not affected since they can connect directly to your website, but when their browsers request a third-party script, it gets routed through our proxy for analysis before delivery.
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.