This article takes an honest look at the features of Jscrambler Web Page Integrity, another company focussing on client-side security.
Since you’re on the c/side website, we acknowledge our bias. That said, we’ve built our case honestly and based our analysis on publicly available information, industry information, and our own or our customers' experiences.
If you want to verify these claims yourself, please navigate to their product page.
What is Jscrambler
Jscrambler is a cybersecurity tool that protects JavaScript code through obfuscation, runtime protection, and anti-tampering techniques. All three are embedded into one offering.
How Jscrambler works
Jscrambler protects first-party JavaScript code by transforming it through obfuscation. This makes the code difficult to reverse-engineer or steal. It's main use is to protect companies scripts with sensitive logic in the frontend such as proprietary algorithms, licensing enforcement, or in-browser app logic. Be sure to debug your own script after obfuscation to see if it functions as normal.
LLM's are increasingly getting better at deobfuscation however. Our own product c/side uses it in real-time to analyze even the most strong obfuscated scripts.
The “code locks” features allow developers to restrict where and when the code can run (e.g., on a specific domain or time window). It secures what’s already known (your own code), but it doesn’t track or analyze what other scripts are doing once the app is live.
Their runtime protections aim to detect tampering and debugging, but they are self-contained. These defenses can block execution if someone tries to interfere with the protected code, but they don’t extend to monitoring other scripts or the dynamic behavior of the full webpage.
One of the key issues with the Jscrambler client-side approach is that by design, they don't know what they don't catch. Any attack that successfully avoids their client-side hooks goes unseen and undetected making it much harder to improve detection capabilities and giving no ability to perform forensics.
This method most crucially places all detections in the browser, making an ideal sandbox for an attacker to develop an attack that circumvents their detection methods.
For securing those 3rd-party scripts, they use a Content Security Policy (CSP). This is a rules-based system which essentially trusts the source (domain). Should the source stay the same but the content changes, like in the biggest client-side attack of 2024 – Polyfill – a CSP won’t catch it.
We wrote an in depth article on Why CSP Doesn’t Work in regards to providing the best client-side security solution:
CSP operates on an allow-list model, which permits resources from trusted domains but cannot block individual scripts or resources from those domains.
How c/side goes further
c/side primarily offers a hybrid proxy approach which sits in between the user session and the 3rd party service. It analyzes the served dependencies code in real-time before serving it to the user.
This allows us to not only spot advanced highly targeted attacks and alert on them, c/side also makes it possible to block attacks before they touch the user's browser. It also checks the box for multiple compliance frameworks, including PCI DSS 4.0.1. We even provide deep forensics, including if an attacker bypasses our detections. Allowing you to more tightly scope the size of the incident us to make our detection capabilities better every day. No other vendor has this capability.
We believe this is the most secure way to monitor and protect your dependencies across your entire website. We've spent years in the client-side security space before we started c/side, we've seen it all, this is the only way you can actually spot an attack.
Sign up or book a demo to get started.