WAFs analyze incoming requests to determine if they're malicious, but third-party scripts are delivered from external CDNs and domains that your WAF considers legitimate. When a trusted script source like a popular analytics library gets compromised, your WAF continues to allow those requests because they're coming from a previously approved domain. The WAF has no way to analyze the actual JavaScript code content to determine if it has become malicious since the last time it was delivered.
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.