Because client-side security monitors an entirely different dimension of the application stack, there is no interference. Our platform co-exists with your existing security solutions. Your WAF continues to protect your main website inbound traffic while cside focuses specifically on client-side JavaScript security. Cside operates at a different dimension; your WAF handles incoming requests to your servers, while cside handles outgoing requests from browsers to third-party script sources. There's no conflict or overlap in functionality.
CSP is a great base-layer for client-side security, but it cannot see script contents. Depending on your needs and risk profile, it may or may not be sufficient.
PCI DSS requires monitoring scripts for changes. CSP can only control sources, not inspect payloads, so it cannot meet PCI DSS requirements.
We fundamentally believe every individual and operation should be able to secure themselves, regardless of resources.
cside only adds 8-20 milliseconds (the blink of an eye typically lasts between 100 and 400 milliseconds) of latency to the specific, highly dynamic JavaScript files we proxy.