WAF signatures are designed to catch known attack patterns in HTTP requests targeting server vulnerabilities by analyzing inbound requests. Client-side attacks use completely legitimate HTTP requests to deliver JavaScript that only becomes malicious when it executes in the browser. Often client-side attacks are fetched by the users browser from a 3rd party endpoint meaning the website' owners WAF is not even in the flow of the request rendering it useless Further still the malicious payload is often obfuscated or uses conditional logic that appear harmless in the HTTP request but reveals its malicious intentions only when running in a specific browser environment that your WAF never sees.
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.