๐Ÿ’ณ PCI DSS v4.0.1 โ€” Current Mandatory Version ๐Ÿ’ฐ $5,000โ€“$100,000/Month Non-Compliance Fines ๐Ÿ” 12 Requirements โ€” 300+ Controls ๐ŸŒ Applies to All Organisations Accepting Card Payments ๐Ÿ’ณ PCI DSS v4.0.1 โ€” Current Mandatory Version ๐Ÿ’ฐ $5,000โ€“$100,000/Month Non-Compliance Fines ๐Ÿ” 12 Requirements โ€” 300+ Controls ๐ŸŒ Applies to All Organisations Accepting Card Payments
๐Ÿ’ณ PCI SECURITY STANDARDS COUNCIL

What is PCI DSS?

The Payment Card Industry Data Security Standard (PCI DSS) is the global security standard for all organisations that store, process or transmit cardholder data. Version 4.0.1 is now the current mandatory standard.

๐Ÿ“‹ OVERVIEW

PCI DSS in Plain Language

PCI DSS was created by the PCI Security Standards Council โ€” a body founded by American Express, Discover, JCB, Mastercard and Visa. It applies to any organisation โ€” merchant, service provider, or processor โ€” that handles payment card data.

The standard defines 12 requirements organised around 6 goals: build and maintain a secure network, protect cardholder data, maintain a vulnerability management programme, implement strong access control measures, regularly monitor and test networks, and maintain an information security policy.

Version 4.0.1 โ€” released in 2024 โ€” is the current mandatory standard. It introduced a customised approach allowing organisations to demonstrate security objectives through alternative controls, and strengthened requirements around authentication, encryption and third-party management.

Who Must Comply?
๐Ÿช Merchants
Any business accepting card payments in-store, online or by phone โ€” from SMEs to global retailers.
๐Ÿฆ Service Providers
Third parties that store, process or transmit cardholder data on behalf of merchants โ€” payment gateways, cloud providers, hosting companies.
๐Ÿ’ณ Payment Processors
Organisations processing card transactions between merchants and issuing banks โ€” acquirers, processors and payment facilitators.
๐ŸŒ E-Commerce Platforms
Online retailers and platforms with any cardholder data in scope โ€” even if using a third-party payment page.
๐Ÿ” THE STANDARD

PCI DSS v4.0.1 โ€” 12 Requirements

Every organisation in scope must demonstrate compliance with all 12 requirements. Our engine maps all 300+ sub-controls automatically.

Req 1

Install & Maintain Network Security Controls

Firewalls and other network security controls to protect the cardholder data environment from untrusted networks.

Req 2

Apply Secure Configurations

Secure configuration standards for all system components. No vendor default passwords or unnecessary services.

Req 3

Protect Stored Account Data

Minimise storage of cardholder data. Protect stored PAN, SAD and sensitive authentication data with encryption.

Req 4

Protect Data in Transit

Strong cryptography for all cardholder data transmitted over open, public networks. TLS 1.2+ mandatory.

Req 5

Protect Against Malicious Software

Deploy and maintain anti-malware solutions on all systems susceptible to malware. Automated scanning and log retention.

Req 6

Develop & Maintain Secure Systems

Security patches, vulnerability management, secure development lifecycle (SDL) and web application firewall (WAF) for public-facing applications.

Req 7

Restrict Access to System Components

Least-privilege access controls. Only authorised individuals can access cardholder data and system components on a need-to-know basis.

Req 8

Identify Users & Authenticate Access

Unique IDs for all users. Multi-factor authentication (MFA) mandatory for all access to the CDE, especially remote access.

Req 9

Restrict Physical Access

Physical security controls for all systems containing cardholder data. Entry logs, badge access, camera systems, visitor management.

Req 10

Log & Monitor All Access

Audit logs for all access to system components and cardholder data. Log retention minimum 12 months, 3 months immediately available.

Req 11

Test Security Systems Regularly

Internal and external vulnerability scanning (quarterly), penetration testing (annual), intrusion detection and file integrity monitoring.

Req 12

Support Information Security with Policies

Comprehensive information security policy covering all personnel. Annual risk assessments, security awareness training, and third-party management programme.

๐Ÿ’ฐ FINES & PENALTIES

The Real Cost of PCI DSS Non-Compliance

Non-compliance fines are charged by acquiring banks, not by a regulator โ€” but the financial and reputational damage is very real.

$5Kโ€“$100K

Monthly Non-Compliance Fees

Acquiring banks charge merchants monthly non-compliance fees ranging from $5,000 to $100,000 depending on merchant level, transaction volume, and severity of non-compliance gaps. These escalate the longer non-compliance persists.

$4.5M+

Average Card Data Breach Cost

A cardholder data breach triggers PFI forensic investigation costs ($10Kโ€“$100K), card replacement fees charged back to the merchant ($3โ€“$5 per card), regulatory fines from card brands, legal liability, and potential permanent loss of card acceptance rights.

$1M+

Card Brand Assessment Fines

Visa and Mastercard levy additional assessments directly on acquirers following a data breach โ€” which are then passed to the responsible merchant. These can exceed $1 million for significant breaches affecting large volumes of cards.

โš ๏ธ Loss of Card Acceptance Rights

Beyond financial fines, the most severe consequence of persistent non-compliance or a major data breach is permanent revocation of the right to accept card payments. For most businesses, this is effectively a terminal event.

๐Ÿ†• PCI DSS v4.0.1

What Changed in PCI DSS v4.0.1?

Version 4.0.1 was released in June 2024 as a minor revision to v4.0, correcting errors and clarifying requirements. All organisations must now comply with v4.0.1.

๐Ÿ”‘ Stronger Authentication Requirements

MFA is now mandatory for all access to the CDE โ€” not just remote access. Phishing-resistant MFA strongly encouraged. Password complexity and rotation requirements updated.

๐ŸŽฏ Customised Approach Option

New option allowing organisations to demonstrate they meet the security objective of each requirement through alternative controls โ€” providing greater flexibility for mature security programmes.

๐Ÿ”— Third-Party & Supply Chain Focus

Strengthened requirements around third-party service provider management. Formal agreements, annual compliance confirmation, and monitoring of third-party PCI DSS status now required.

๐Ÿ›ก๏ธ Web Application & API Security

New requirements for managing web application security โ€” WAF or automated technical solution now required for all public-facing web applications. API security explicitly addressed.

๐Ÿ“‹ Targeted Risk Analysis

Many requirements previously prescriptive now allow a targeted risk analysis approach โ€” letting organisations define frequency and method based on their specific risk environment.

๐Ÿ“Š Enhanced Logging & Monitoring

Expanded requirements for automated detection of suspicious activity, log review tools, and detection of failures in security controls. IDS/IPS and network monitoring strengthened.

๐Ÿ“„ ASSESSMENT TYPES

SAQ vs ROC โ€” Which Applies to You?

The type of PCI DSS assessment depends on your merchant level and how you handle card data.

SAQ A

Card-Not-Present Merchants

For e-commerce merchants that have outsourced all cardholder data functions. Simplest assessment โ€” applies where you use a fully outsourced payment page and store no card data.

SAQ B / B-IP

Imprint or Standalone Terminal

Merchants using only imprint machines or standalone, dial-out terminals. No electronic storage of cardholder data. Common for small retail businesses.

SAQ C / C-VT

Payment Applications โ€” No Electronic Storage

Merchants with payment application systems connected to the internet. No electronic storage of cardholder data beyond transaction authorisation.

SAQ D

All Other Merchants & Service Providers

The most comprehensive SAQ โ€” applies to all service providers and merchants that do not qualify for simpler SAQ types. Covers all 12 requirements in full.

Level 1 Merchants โ€” ROC Required

Merchants processing over 6 million card transactions per year (or any merchant that has suffered a data breach) must complete a full Report on Compliance (ROC) assessed by a Qualified Security Assessor (QSA). The Cognisec PCI DSS Engine generates ROC-aligned evidence packs.

Ready to Achieve PCI DSS v4.0.1 Compliance?

Start your free 30-day trial. All 12 requirements. All 3 panels. No complexity.

Start Free 30-Day Trial Explore the Platform
WhatsApp Us