Cside analyses every third-party script on our side before it runs, 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.
Why is the browser environment invisible to WAF monitoring?
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.
Can a WAF protect against supply chain attacks on third-party JavaScript libraries?
WAFs cannot protect against client-side supply chain attacks because they don't intercept the fetch to the 3rd party endpoint and therefore have no visibility into the JavaScript files from the 3rd party sources.
How do conditional client-side attacks avoid WAF detection?
Sophisticated client-side attacks use conditional logic that only triggers under specific circumstances - certain geographic locations, specific times, or particular user behaviors.