In March 2022, the Payment Card Industry Security Standards Council released a revised version of its Data Security Standard, commonly known as PCI DSS v4.0. In this revised version are two new sections, 6.4.3 and 11.6.1 which offer guidance regarding 3rd, 4th, and nth party JavaScript running on your websites.
The articles, video and downloadable guide below are for anybody in the PCI DSS industry who focus on PCI DSS security and compliance and can be used as a resource for Qualified Security Assessors (QSA) who want to learn more about staying PCI compliant.
The shift online, with all of its benefits to businesses and consumers, also introduces serious risks to your business. As someone involved in the business side of digital, you need to understand these risks.
Digital skimming, formjacking, e-Skimming, Magecart – these are all methods used to steal credit card data and PII from transaction oriented websites. What should QSAs know?
Related Posts: [Infographic] Magecart by The Numbers [New Threat] JS Skimmer ‘Pipka’ Attacks eCommerce Businesses
We’re taking a closer look at PCI 11.6.1, what it entails, and how you can enhance your security strategy to meet this new guidance.
PCI 6.4.3 gives a nod to proprietary script management systems which have been created to specifically handle malicious script execution.
PCI’s latest guidance, 6.4.3 prompts security teams to prioritize managing and mitigating client-side web application attacks.
In order to eliminate website data breaches and compliance violations, you need to implement prevention-first client-side web application security.
Partnership Enables Source Defense to Enhance PCI Security Standards to Protect Corporate Websites – the Primary Origination Point of Payment Data As seen on Newswire
The Payment Card Industry (PCI) has given serious thought to payment page guidance in DSS v4.0. New sections including 6.4.3 and 11.6.1 indicate the seriousness of this problem.Every security practitioner responsible for a public-facing website that accepts payments should inform themselves thoroughly of the implications of this change.
These guidelines inform organizations of the necessity to make changes now. In this guide, we dive deep into PCI DSS v.4.0 and specifically:
