Malicious requests, SQL injections, and exploitation of application vulnerabilities are examples of server-side attacks. This is where WAFs excel. Client-side attacks, on the other hand, exploit legitimate third-party scripts that your WAF has already approved and delivered to browsers. The attack happens when these scripts execute in your users' browsers and steal data like credit card numbers or login credentials. Your WAF sees the legitimate script delivery, but is blind to what that script does once it's running on the client-side.
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.