Friday, March 29, 2024

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.

Website

Latest articles

GoPlus’s Latest Report Highlights How Blockchain Communities Are Leveraging Critical API Security Data To Mitigate Web3 Threats

GoPlus Labs, the leading Web3 security infrastructure provider, has unveiled a groundbreaking report highlighting...

Wireshark 4.2.4 Released: What’s New!

Wireshark stands as the undisputed leader, offering unparalleled tools for troubleshooting, analysis, development, and...

Zoom Unveils AI-Powered All-In-One AI Work Workplace

Zoom has taken a monumental leap forward by introducing Zoom Workplace, an all-encompassing AI-powered...

iPhone Users Beware! Darcula Phishing Service Attacking Via iMessage

Phishing allows hackers to exploit human vulnerabilities and trick users into revealing sensitive information...

2 Chrome Zero-Days Exploited at Pwn2Own 2024: Patch Now

Google has announced a crucial update to its Chrome browser, addressing several vulnerabilities, including...

The Moon Malware Hacked 6,000 ASUS Routers in 72hours to Use for Proxy

Black Lotus Labs discovered a multi-year campaign by TheMoon malware targeting vulnerable routers and...
Guru baran
Guru baranhttps://gbhackers.com
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Mitigating Vulnerability Types & 0-day Threats

Mitigating Vulnerability & 0-day Threats

Alert Fatigue that helps no one as security teams need to triage 100s of vulnerabilities.

  • The problem of vulnerability fatigue today
  • Difference between CVSS-specific vulnerability vs risk-based vulnerability
  • Evaluating vulnerabilities based on the business impact/risk
  • Automation to reduce alert fatigue and enhance security posture significantly

Related Articles