Wednesday, January 22, 2025
HomeComputer SecurityPCI DSS Version 3.2.1 Released - Changes that You Need to Know...

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

Published on

SIEM as a Service

Follow Us on Google News

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.

Gurubaran
Gurubaran
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.

Latest articles

SQL Injection Vulnerability in Microsoft’s DevBlogs Lets Hackers Injecting Malicious SQL

In a recent discovery, a security researcher uncovered a critical SQL injection vulnerability on...

Three New ICS Advisories Released by CISA Detailing Vulnerabilities & Mitigations

The Cybersecurity and Infrastructure Security Agency (CISA) announced three new Industrial Control Systems (ICS)...

Security Researchers Discover Critical RCE Vulnerability, Earned $40,000 Bounty

Cybersecurity researchers Abdullah Nawaf and Orwa Atyat, successfully escalated a limited path traversal vulnerability...

IBM i Access Client Solutions Might Be Leaking Your Passwords

A potential security flaw in IBM i Access Client Solutions (ACS) has raised serious...

API Security Webinar

Free Webinar - DevSecOps Hacks

By embedding security into your CI/CD workflows, you can shift left, streamline your DevSecOps processes, and release secure applications faster—all while saving time and resources.

In this webinar, join Phani Deepak Akella ( VP of Marketing ) and Karthik Krishnamoorthy (CTO), Indusface as they explores best practices for integrating application security into your CI/CD workflows using tools like Jenkins and Jira.

Discussion points

Automate security scans as part of the CI/CD pipeline.
Get real-time, actionable insights into vulnerabilities.
Prioritize and track fixes directly in Jira, enhancing collaboration.
Reduce risks and costs by addressing vulnerabilities pre-production.

More like this

Is this Website Safe: How to Check Website Safety – 2025

is this website safe? In this digital world, Check a website is safe is...

LegionLoader Abusing Chrome Extensions To Deliver Infostealer Malware

LegionLoader, a C/C++ downloader malware, first seen in 2019, delivers payloads like malicious Chrome...

North Korean Hackers Stolen $2.2 Billion From Crypto Platforms In 2024

Cryptocurrency hacking incidents in 2024 surged 21.07% YoY to $2.2 billion, with 303 breaches...