Loading story…
Nir Rothenberg, CISO at Rapyd, highlights that strong engineering correlates with robust payment security, regardless of region. He emphasizes the importance of collaboration, account takeover prevention, and especially advanced monitoring, which is often overlooked in high-volume payment environments. Rothenberg also advises against treating compliance as a checklist and encourages companies to view auditors as partners when preparing for PCI DSS 4.0.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Organizations pursuing **PCI DSS** compliance are being warned that compliance controls alone do not prevent **client-side payment data theft**, particularly when third-party scripts and outsourced payment flows are involved. Commentary highlights that changes to PCI DSS v4-related guidance (including updated **SAQ A** language for merchants using PCI-compliant payment service providers) can reduce mandated anti-skimming requirements, increasing the risk that merchants “trust but don’t verify” protections around browser-executed code and third-party dependencies. Separately, tokenization guidance emphasizes that **tokenization is distinct from encryption** and is intended to reduce exposure by replacing sensitive values (e.g., PANs) with non-sensitive tokens, potentially reducing PCI scope when implemented correctly. The same guidance cautions that implementation pitfalls are common and that using encryption as a stand-in for tokenization can leave organizations at risk—reinforcing that **data protection architecture (e.g., tokenization)** and **client-side/script visibility controls** address different parts of the payment-data threat surface, and both may be necessary to mitigate modern skimming techniques such as **MirrorMask** targeting select **Stripe** merchants via script/API redirection and reverse-proxy interception.
Jun 29, 2026
A recurring theme in executive security discussions is that **increased cybersecurity spending and tooling does not reliably translate into better outcomes** when organizations lack basic operational discipline. Commentary highlights that breaches and major security failures are frequently rooted in process and governance gaps rather than missing technology, despite growing budgets, expanding tool stacks, and compliance reporting. One account of a penetration test describes rapid compromise using **non-advanced techniques**: initial access via phishing to capture credentials, lateral movement aided by an **unpatched server**, and escalation to **domain admin** after discovering credentials in a shared location (e.g., `Admin_Password.txt`), followed by data exfiltration. The described root causes were foundational control failures—**inconsistent patching**, incomplete **MFA adoption**, and lingering/overprivileged accounts—underscoring that tool-heavy environments (e.g., EDR, SIEM, DLP, threat intel) can still be bypassed when identity, patch, and access-control hygiene are weak.
Jul 12, 2026
Organizations are increasingly moving beyond static compliance frameworks and annual checklists to adopt real-time, dynamic risk assessment models. Security leaders are recognizing the limitations of traditional gap analyses, which focus on adherence to frameworks like ISO or NIST, and are instead prioritizing tailored risk assessments that address specific threats such as unauthorized access. By customizing assessments to focus on critical risks and integrating findings into actionable remediation plans, CISOs can drive meaningful change and improve access control across their environments. Penetration testing is highlighted as a vital component of this modern risk management strategy, with an emphasis on understanding the business context and true impact of identified vulnerabilities. Rather than simply cataloging technical issues, organizations are encouraged to ask probing questions about the potential consequences of exploitation, the possibility of attack chaining, and the types of attackers who might target their systems. This approach enables security teams to identify systemic weaknesses and prioritize remediation efforts based on real-world risk, rather than compliance checkboxes.
Jul 12, 2026