Skip to main content
> PCI-DSS

Payment Card Industry Data Security Standard

Protecting cardholder data through comprehensive security controls

Established: 2004 (current version 4.0 released 2022) Last Updated: March 2024 (v4.0.1) Scope: Global
12 Core
Requirements

// What is PCI-DSS?

PCI-DSS is a global security standard for organizations that store, process, or transmit payment card data. Created by major card brands (Visa, Mastercard, American Express, Discover, JCB), the standard aims to reduce payment card fraud by establishing baseline security requirements for all entities in the payment ecosystem.

Version 4.0, released in March 2022, represents the most significant update in the standard's history, introducing customized approaches for meeting requirements and emphasizing security as a continuous process. Organizations have until March 2025 for full v4.0 compliance, with some requirements extended to March 2025.

Compliance validation varies by merchant and service provider level, ranging from annual self-assessment questionnaires (SAQs) for smaller merchants to on-site assessments by Qualified Security Assessors (QSAs) for the largest organizations.

// Inside the Regulation

PCI-DSS v4.0 organizes its requirements into six control objectives containing 12 requirement families. Each requirement includes defined testing procedures and guidance for implementation.

1

Build and Maintain a Secure Network and Systems

The foundation of cardholder data protection starts with network architecture and system configuration.

Requirement 1: Network Security Controls

Install and maintain network security controls (firewalls, security groups) restricting traffic between trusted and untrusted networks, including the cardholder data environment.

Requirement 2: Secure Configurations

Apply secure configurations to all system components, eliminating vendor defaults and unnecessary services.

2

Protect Account Data

Direct controls safeguarding cardholder data and sensitive authentication data.

Requirement 3: Protect Stored Account Data

Keep cardholder data storage to a minimum, render PAN unreadable anywhere it's stored, and protect encryption keys.

Requirement 4: Protect Data in Transit

Encrypt cardholder data transmitted across open, public networks using strong cryptography.

3

Maintain a Vulnerability Management Program

Continuous identification and remediation of vulnerabilities in the cardholder data environment.

Requirement 5: Anti-Malware

Protect all systems against malware with regularly updated anti-malware solutions and periodic scans.

Requirement 6: Secure Development

Develop and maintain secure systems and software through secure coding practices, change control, and vulnerability management.

4

Implement Strong Access Control Measures

Restricting access to cardholder data to only those with legitimate business need.

Requirement 7: Restrict Access

Limit access to system components and cardholder data to individuals whose job requires such access.

Requirement 8: Identify Users

Identify users and authenticate access to system components using unique IDs and multi-factor authentication.

Requirement 9: Physical Access

Restrict physical access to cardholder data and systems processing that data.

5

Regularly Monitor and Test Networks

Ongoing monitoring and testing to ensure controls remain effective.

Requirement 10: Logging and Monitoring

Log and monitor all access to network resources and cardholder data, reviewing logs daily.

Requirement 11: Security Testing

Test security systems and processes regularly through vulnerability scanning, penetration testing, and file integrity monitoring.

6

Maintain an Information Security Policy

Establishing security as organizational culture through policy and awareness.

Requirement 12: Security Policies

Support information security with organizational policies and programs including risk assessment, acceptable use, and vendor management.

Note: PCI-DSS v4.0 introduces the 'customized approach' allowing organizations to meet requirement objectives through alternative controls, provided they demonstrate equivalent or greater security through rigorous testing. This flexibility acknowledges that prescriptive controls may not fit every environment.

// Who Must Comply

  • 1 Merchants accepting payment cards (retail, e-commerce, hospitality, any business taking card payments)
  • 2 Service providers storing, processing, or transmitting cardholder data on behalf of merchants
  • 3 Payment processors and gateways
  • 4 Issuing and acquiring banks
  • 5 Third-party vendors with access to cardholder data environments

// Key Requirements

Network Segmentation

Isolate the cardholder data environment from other networks to reduce scope and risk

Encryption

Encrypt stored cardholder data and protect cryptographic keys; encrypt transmission over public networks

Multi-Factor Authentication

Implement MFA for all access to the cardholder data environment and remote network access

Penetration Testing

Conduct internal and external penetration tests at least annually and after significant changes

Continuous Monitoring

Maintain logging of all access and security events with daily log reviews

Documentation

Maintain comprehensive security policies, procedures, and evidence of compliance activities

// Enforcement & Penalties

PCI-DSS itself doesn't impose fines—penalties come from card brands and acquiring banks through contractual agreements. Non-compliant organizations face escalating consequences including fines, increased transaction fees, and potential loss of card acceptance privileges.

Maximum Penalty

$100,000+ per month for non-compliance

Examples:

  • Monthly fines ranging from $5,000 to $100,000 until compliance is achieved
  • Increased transaction fees (higher interchange rates)
  • Liability for fraud losses occurring due to non-compliance
  • Termination of card acceptance privileges in severe cases

// Cyber Insurance Impact

Cyber insurers require PCI-DSS compliance attestation for any organization processing payment cards. Claims involving payment card breaches invariably examine compliance status. Non-compliant organizations may face coverage exclusions for card-related incidents. Insurers increasingly require evidence of Requirement 11 testing (vulnerability scans and penetration tests) as policy conditions.

// How Breach Craft Helps

We help organizations achieve PCI-DSS compliance through genuine security improvements—not checkbox exercises. Our services address the specific requirements and challenges of PCI-DSS.

// Related Frameworks

Ready to Strengthen Your Defenses?

Schedule a free consultation with our security experts to discuss your organization's needs.

Or call us directly at (445) 273-2873