Yes, this is where cside really shines compared to other solutions. Since we hash and analyze every script for every user session, we catch conditional attacks that only fire for 1 in 1,000 visitors or specific geographic regions. Most attacks are designed to avoid security solutions by only activating at specific hours and for certain user types on certain devices often targeting a small percentage of visitors for weeks at a time and avoiding security solutions. The Script method means these targeted threats are identified the moment they appear, not weeks later when a customer flags a data loss incident.
Does a CSP provide enough security?
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.
Why doesn't a Content Security Policy (CSP) make us PCI compliant?
PCI DSS requires monitoring scripts for changes. CSP can only control sources, not inspect payloads, so it cannot meet PCI DSS requirements.
Why do you offer CSP for free?
We fundamentally believe every individual and operation should be able to secure themselves, regardless of resources.
Can cside work alongside my existing WAF without conflicts?
We monitor an entirely different dimension of the application stack; hence, there is no interference.