Saturday, December 2, 2023

PCI DSS Version 3.2.1 Released – Changes that You Need to Know About PCI Data Security

PCI Security Standards Council (PCI SSC) published PCI DSS Version 3.2.1 with minor revision to the PCI Data Security Standard (PCI DSS), which businesses around the world use to safeguard payment card data before, during and after a purchase is made.

The Payment Card Industry Data Security Standard (PCI DSS) is a defined standard that acknowledges a set of Policies and Procedures planned to enhance the security of payment card, cash card exchanges and ensure cardholders against abuse of their own data.

The PCI Security Standards Council is a worldwide open body framed to create, upgrade, scatter and help with the comprehension of security measures for payment account security and Last year PCI published  Best practices for securing E-commerce Websites

The PCI DSS was made together in 2004 by four noteworthy Credit-card organizations: Visa, MasterCard, Discover and American Express.

PCI certification ensures the security of card data at your business through a set of requirements established by the PCI SSC. These include a number of commonly known best practices, such as:

  • Installation of firewalls
  • Encryption of data transmissions
  • Use of anti-virus software

You can also get the quote for PCI-compliant security that provides a valuable asset that informs customers that your business is safe to transact with.

PCI DSS Version 3.2.1 replaces version 3.2, no new requirements added to version 3.2.1 and the version 3.2 remains valid upto 31 December 2018 and will be retired as of 1 January 2019.

PCI SSC Chief Technology Officer Troy Leach says “It is critically important that organizations disable SSL/early TLS and upgrade to a secure alternative to safeguard their payment data.”

After 30 June 2018, all entities must have stopped use of SSL/early TLS as a security control, and use only secure versions of the protocol.

POS POI terminals (and the SSL/early TLS termination points to which they that can be verified as not being susceptible to any known exploits for SSL/early TLS, may continue using these as a security control after 30 June 2018.

Removal of multi-factor authentication (MFA) from the compensating control, now MFA is required for all non-console administrative access; an addition of one-time passwords as an alternative potential control for this scenario.

The updates in PCI DSS v3.2.1 do not affect the Payment Application Data Security Standard (PA-DSS), which will remain at v3.2.

POS POI terminals that can be verified as not being susceptible to any known exploits for SSL/early TLS, may continue using these as a security control after 30 June 2018.

The widespread of SSL/early TLS has many vulnerabilities (POODLE, BEAST, CRIME, Heartbleed) making it unsafe for protecting data.

“Online and e-commerce environments using SSL/ early TLS are most susceptible to these vulnerabilities and should be upgraded immediately.” reads PCI Dss statement.


Latest articles

Active Attacks Targeting Google Chrome & ownCloud Flaws: CISA Warns

The CISA announced two known exploited vulnerabilities active attacks targeting Google Chrome & own...

Cactus Ransomware Exploiting Qlik Sense code execution Vulnerability

A new Cactus Ransomware was exploited in the code execution vulnerability to Qlik Sense...

Hackers Bypass Antivirus with ScrubCrypt Tool to Install RedLine Malware

The ScrubCrypt obfuscation tool has been discovered to be utilized in attacks to disseminate the RedLine Stealer...

Hotel’s Hacked Logins Let Attacker Steal Guest Credit Cards

According to a recent report by Secureworks, a well-planned and advanced phishing attack was...

Critical Zoom Vulnerability Let Attackers Take Over Meetings

Zoom, the most widely used video conferencing platform has been discovered with a critical...

Hackers Using Weaponized Invoice to Deliver LUMMA Malware

Hackers use weaponized invoices to exploit trust in financial transactions, embedding malware or malicious...

US-Seized Crypto Currency Mixer Used by North Korean Lazarus Hackers

The U.S. Treasury Department sanctioned the famous cryptocurrency mixer Sinbad after it was claimed...

API Attack Simulation Webinar

Live API Attack Simulation

In the upcoming webinar, Karthik Krishnamoorthy, CTO and Vivek Gopalan, VP of Products at Indusface demonstrate how APIs could be hacked.The session will cover:an exploit of OWASP API Top 10 vulnerability, a brute force account take-over (ATO) attack on API, a DDoS attack on an API, how a WAAP could bolster security over an API gateway

Related Articles