Happy Monday! ⛅
Make sure to subscribe to our monthly newsletter to receive all the latest news on Jscrambler's initiatives and products. We bring you the latest on client-side protection, PCI DSS v4.0 compliance, and JavaScript-related tutorials at eu1.hubs.ly/H0yHnq-0 📰
At IAPP Privacy. Security. Risk. + AI Governance Global 2026, we’ll be talking about the growing gap between privacy policies and what actually happens in the browser at runtime.
Join Jscrambler in Seattle on October 8–9 to learn how runtime enforcement can help close this gap and protect data where it matters: in the browser. 💻
You can meet the team at the event: Sean O'Leary, Bryan Powell, Tyson Whitten, Nathan Coppinger, and Gareth Bowker 👥
📍 Seattle Convention Center
🗓️ October 8–9, 2026
Planning to attend? Let’s connect at jscrambler.com/events-and-we… 🔗
#IAPP #Privacy #DataProtection #AIGovernance #Cybersecurity #CIPA #CMP #Jscrambler
CIPA litigation is shifting, not disappearing ⬇️
If passed, California SB 690 will curb pen register lawsuits, but §631 wiretapping claims against tracking pixels, chatbots, and session replays remain an active risk.
For organizations operating websites with visitors in California, that means website tracking and third-party scripts are still under scrutiny.
And a CMP alone isn’t enough.
A CMP records consent. Runtime enforcement helps ensure it’s actually enforced in the browser.
Our latest blog breaks down 5 steps to help reduce CIPA litigation risk - including why organizations need to move beyond passive consent management to active browser runtime enforcement.
👉 jscrambler.com/blog/steps-pr… 📘
#CIPA #DataPrivacy #PrivacyCompliance #WebPrivacy
SAQ A compliance doesn't mean your checkout is safe.
A prime example: a Magecart campaign abused Google Tag Manager and Stripe's own API to skim payment data, storing payloads in metadata and exfiltrating data right back through Stripe's legitimate channels.
In our latest blog post, we dive into:
🔹 Why skipping the SAQ A Eligibility Criteria is riskier than it looks
🔹 How attackers and over-collecting marketing pixels exploit trusted platforms
🔹 Why client-side security must extend beyond payment pages and checkbox compliance
Read the full breakdown on the Jscrambler blog: jscrambler.com/blog/pci-dss-… 📘
#PCIDSS #Ecommerce #CyberSecurity #Magecart
AI is making reverse engineering a lot easier.
LLMs can now help analyze obfuscated JavaScript, uncover business logic, and speed up a process that used to require significant time and expertise. So, is traditional obfuscation still enough to protect your client-side code? ⬇️
In our latest blog, we look at how the threat has changed and what teams can do to make their JavaScript harder to reverse engineer - from polymorphic obfuscation to runtime protections.
🔐 Read it now at Jscrambler's blog jscrambler.com/blog/llms-ip-… 📘
#Cybersecurity #AppSec
LLMs have changed the reverse-engineering game. 🔓⬇️
Traditional obfuscation is no longer enough to protect client-side IP from AI-assisted analysis.
In this week's blogpost, we dive into:
🔹 The Old vs New Threat Model
🔹 Why Static Obfuscation Fails Against LLM-Assisted Analysis
🔹 What “Polymorphic” and “Self-Defending” Actually Mean in Practice
🔹 5 Ways to Mitigate LLM-Assisted Reverse Engineering Today
Read it now at Jscrambler's blog jscrambler.com/blog/llms-ip-… 📘
#Cybersecurity #AppSec #LLM #JavaScript #ReverseEngineering
Come meet the Jscrambler team at OWASP AppSec Days Portugal 2026 and discover how to:
→ Secure AI-assisted code at runtime
→ Govern third-party scripts and embedded AI agents
→ Neutralize active client-side threats
→ Protect sensitive data where it’s created and accessed
📍 Fundação António Cupertino de Miranda, Porto
📅 September 23–24
📌 Booth #14
Security can’t stop at the edge. It needs to extend into the runtime.
Schedule a meeting with the team at jscrambler.com/events-and-we… 🔗
See you in Porto! 🇵🇹
#OWASP #AppSec #AppSecDays #Cybersecurity
