Cside puts itself in the middle between the 3rd party and the end user, making it easy to stop attacks by analyzing JavaScript content asynchronously and hashing a list of bad scripts, preventing them from being loaded again. Cside also analyses client-side behaviours of scripts in the browser as well as data access and exfiltration attempts. While your WAF continues protecting your web infrastructure, cside examines every third-party script for malicious behavior, hashes content to detect changes, and blocks threats before they can execute in your users' browsers. Giving complete visibility into client-side executions, creating complete protection against client-side attacks.
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.