WAFs are designed to analyze HTTP requests coming into your server, but client-side attacks happen after your legitimate content has already been delivered to the user's browser. A malicious script would execute within the browser environment, collecting sensitive data and sending it to attacker-controlled servers. A WAF would not have visibility into that payload by design. Since this activity happens on the client-side after your webserver responds, your WAF never sees the malicious behavior or data theft occurring.
Can cside work alongside my existing WAF without conflicts?
We monitor an entirely different dimension of the application stack; hence, there is no interference.
How does cside solve the client-side blind spot that WAFs can't address?
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.
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.