International (payment card industry; enforced contractually by payment brands and acquirers)

PCI DSS 4.0

360 controls. 205 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

360 controls 205 frameworks share controls with it International (payment card industry; enforced contractually by payment brands and acquirers) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

PCI DSS 4.0 Evidence & Implementation Kit

360 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
1.1.11.1.1 Requirement 1 policies and procedures governed17
1.1.21.1.2 Requirement 1 roles and responsibilities assigned18
1.2.11.2.1 Ruleset configuration standards for NSCs18
1.2.21.2.2 Network connection and NSC changes under change control19
1.2.31.2.3 Accurate network diagram of CDE connections18
1.2.41.2.4 Accurate data-flow diagram for account data15
1.2.51.2.5 Allowed services, protocols and ports justified22
1.2.61.2.6 Security features for insecure services in use17
1.2.71.2.7 Six-monthly review of NSC configurations18
1.2.81.2.8 NSC configuration files secured and consistent15
1.3.11.3.1 Inbound CDE traffic restricted20
1.3.21.3.2 Outbound CDE traffic restricted19
1.3.31.3.3 NSCs between wireless networks and the CDE13
1.4.11.4.1 NSCs between trusted and untrusted networks24
1.4.21.4.2 Restricting traffic entering trusted networks from outside19
1.4.31.4.3 Anti-spoofing measures at trusted boundary8
1.4.41.4.4 Cardholder data stores not reachable from untrusted networks19
1.4.51.4.5 Internal IP and routing disclosure limited10
1.5.11.5.1 Security controls on dual-connected devices16
10.1.110.1.1 Requirement 10 policies and procedures maintained and in use17
10.1.210.1.2 Roles for logging and monitoring assigned and understood12
10.2.110.2.1 Audit logging enabled on all system components24
10.2.1.110.2.1.1 Logs capture individual user access to cardholder data17
10.2.1.210.2.1.2 Logs capture all administrative actions18
10.2.1.310.2.1.3 Access to the audit logs is itself logged16
10.2.1.410.2.1.4 Logs capture invalid logical access attempts17
10.2.1.510.2.1.5 Logs capture changes to identification and authentication credentials18
10.2.1.610.2.1.6 Logs capture initialization and stopping of audit logs13
10.2.1.710.2.1.7 Logs capture creation and deletion of system-level objects14
10.2.210.2.2 Required details recorded for each auditable event19
10.3.110.3.1 Audit log read access limited to job need15
10.3.210.3.2 Audit log files protected from modification21
10.3.310.3.3 Audit logs promptly backed up to central secure storage16
10.3.410.3.4 File integrity monitoring on audit logs14
10.4.110.4.1 Daily review of security-relevant logs26
10.4.1.110.4.1.1 Automated mechanisms used for audit log review17
10.4.210.4.2 Periodic review of all other system component logs17
10.4.2.110.4.2.1 Periodic log review frequency set by targeted risk analysis9
10.4.310.4.3 Exceptions and anomalies from log review addressed24
10.5.110.5.1 Keep logs 12 months, latest three months online21
10.6.110.6.1 System clocks synchronized with time-sync technology15
10.6.210.6.2 Systems configured to correct and consistent time13
10.6.310.6.3 Time sync configuration and time data protected15
10.7.110.7.1 Service providers detect critical control failures (superseded)16
10.7.210.7.2 Detect and alert on critical security control failures25
10.7.310.7.3 Respond promptly to critical security control failures21
11.1.111.1.1 Requirement 11 policies and procedures managed19
11.1.211.1.2 Roles for security testing assigned and understood12
11.2.111.2.1 Detect authorized and rogue wireless access points14
11.2.211.2.2 Inventory of authorized wireless access points12
11.3.111.3.1 Quarterly internal vulnerability scans29
11.3.1.111.3.1.1 Lower-risk vulnerabilities handled per risk analysis20
11.3.1.211.3.1.2 Authenticated internal vulnerability scanning15
11.3.1.311.3.1.3 Internal scans after significant change18
11.3.211.3.2 Quarterly ASV external vulnerability scans22
11.3.2.111.3.2.1 External scans after significant change14
11.4.111.4.1 Penetration testing methodology defined and implemented22
11.4.211.4.2 Internal penetration testing annually and after change22
11.4.311.4.3 External penetration testing annually and after change24
11.4.411.4.4 Correct exploitable findings from penetration tests28
11.4.511.4.5 Annual segmentation penetration testing18
11.4.611.4.6 Service provider segmentation testing every six months9
11.4.711.4.7 Multi-tenant providers support customer penetration testing7
11.5.111.5.1 IDS/IPS monitoring of CDE traffic22
11.5.1.111.5.1.1 Service providers detect covert malware channels15
11.5.211.5.2 Change detection on critical files21
11.6.111.6.1 Payment page tamper detection10
12.1.112.1.1 Overall information security policy established and disseminated26
12.1.212.1.2 Security policy reviewed annually and updated as needed22
12.1.312.1.3 Security roles defined and acknowledged by all personnel21
12.1.412.1.4 Executive ownership of information security formally assigned21
12.10.112.10.1 Incident response plan ready for activation29
12.10.212.10.2 Annual review and testing of the incident response plan27
12.10.312.10.3 Incident response personnel available 24/719
12.10.412.10.4 Periodic training for incident response personnel20
12.10.4.112.10.4.1 Responder training frequency set by targeted risk analysis12
12.10.512.10.5 Plan covers alerts from security monitoring systems25
12.10.612.10.6 Plan evolved from lessons learned and industry developments24
12.10.712.10.7 Response procedures for PAN found in unexpected locations16
12.2.112.2.1 Rules for acceptable use of end-user technology20
12.3.112.3.1 Targeted risk analysis for flexible-frequency requirements25
12.3.212.3.2 Targeted risk analysis for each customized-approach requirement18
12.3.312.3.3 Cryptographic cipher suite and protocol inventory reviewed annually19
12.3.412.3.4 Annual review of hardware and software technologies23
12.4.112.4.1 Executive responsibility for a PCI DSS compliance program17
12.4.212.4.2 Quarterly reviews that personnel follow security procedures24
12.4.2.112.4.2.1 Documentation of quarterly operational reviews19
12.5.112.5.1 Inventory of in-scope system components25
12.5.212.5.2 Annual and change-driven scope confirmation28
12.5.2.112.5.2.1 Six-monthly scope confirmation for service providers12
12.5.312.5.3 Scope review after significant organisational change17
12.6.112.6.1 Formal security awareness program26
12.6.212.6.2 Awareness program reviewed annually and updated18
12.6.312.6.3 Security awareness training on hire and annually with acknowledgment28
12.6.3.112.6.3.1 Awareness training covers phishing and social engineering19
12.6.3.212.6.3.2 Awareness training covers acceptable use of end-user technologies18
12.7.112.7.1 Pre-hire screening of personnel with CDE access23
12.8.112.8.1 List of third-party service providers22
12.8.212.8.2 TPSP contracts acknowledging account data responsibility26
12.8.312.8.3 Due diligence before engaging TPSPs26
12.8.412.8.4 Annual monitoring of TPSP compliance status26
12.8.512.8.5 Responsibility allocation between entity and TPSPs25
12.9.112.9.1 TPSP written acknowledgments to customers10
12.9.212.9.2 TPSP support for customer information requests14
2.1.12.1.1 Requirement 2 policies and procedures governed34
2.1.22.1.2 Requirement 2 roles and responsibilities assigned31
2.2.12.2.1 System configuration standards maintained25
2.2.22.2.2 Vendor default accounts managed184
2.2.32.2.3 Primary functions with different security levels managed17
2.2.42.2.4 Only necessary functionality enabled23
2.2.52.2.5 Insecure services, protocols or daemons secured15
2.2.62.2.6 System security parameters configured against misuse20
2.2.72.2.7 Non-console administrative access encrypted19
2.3.12.3.1 Wireless vendor defaults changed or confirmed secure13
2.3.22.3.2 Wireless encryption keys changed on triggers14
3.3.1.13.3.1.1 Full track data not retained after authorization8
3.3.1.23.3.1.2 Card verification code not retained after authorization3
3.3.1.33.3.1.3 PIN and PIN block not retained after authorization5
3.3.23.3.2 Pre-authorization SAD stored electronically is strongly encrypted12
3.3.33.3.3 Issuer SAD storage limited, justified and encrypted9
3.4.23.4.2 Remote access blocks copying or relocating PAN14
3.5.13.5.1 Stored PAN rendered unreadable20
3.5.1.13.5.1.1 PAN hashes are keyed cryptographic hashes8
3.5.1.23.5.1.2 Disk or partition encryption only on removable media15
3.5.1.33.5.1.3 Disk encryption access independent of OS authentication14
3.6.1.13.6.1.1 Service provider cryptographic architecture documented14
3.6.1.23.6.1.2 Permitted storage forms for secret and private keys14
3.6.1.33.6.1.3 Cleartext key component access limited to minimum custodians15
3.6.1.43.6.1.4 Cryptographic keys kept in fewest locations12
3.7.23.7.2 Secure distribution of cryptographic keys15
3.7.33.7.3 Secure storage of cryptographic keys15
3.7.43.7.4 Key changes at end of cryptoperiod14
3.7.53.7.5 Retirement, replacement or destruction of keys13
3.7.63.7.6 Split knowledge and dual control for manual key operations9
3.7.73.7.7 Prevent unauthorized substitution of keys11
3.7.83.7.8 Key custodians formally acknowledge responsibilities11
3.7.93.7.9 Key guidance for service provider customers8
4.1.14.1.1 Requirement 4 policies and procedures maintained and communicated16
4.1.24.1.2 Requirement 4 roles and responsibilities assigned15
4.2.14.2.1 Strong cryptography safeguards PAN over public networks22
4.2.1.14.2.1.1 Inventory of trusted transmission keys and certificates16
4.2.1.24.2.1.2 Wireless networks use strong cryptography15
4.2.24.2.2 PAN secured when sent by end-user messaging18
5.1.15.1.1 Requirement 5 policies and procedures maintained and communicated16
5.1.25.1.2 Requirement 5 roles and responsibilities assigned14
5.2.3.15.2.3.1 Targeted risk analysis sets evaluation frequency12
5.3.2.15.3.2.1 Targeted risk analysis sets malware scan frequency12
5.3.45.3.4 Anti-malware audit logs enabled and retained16
5.3.55.3.5 Users cannot disable or alter anti-malware17
5.4.15.4.1 Mechanisms detect and protect against phishing17
6.1.16.1.1 Requirement 6 policies and procedures maintained and communicated17
6.1.26.1.2 Requirement 6 roles and responsibilities assigned15
6.2.16.2.1 Secure development of bespoke and custom software23
6.2.26.2.2 Annual secure software training for developers22
6.2.36.2.3 Code review before release20
6.2.3.16.2.3.1 Manual code review independence and approval19
6.2.46.2.4 Engineering techniques against common software attacks18
6.4.16.4.1 Public web application review or automated protection20
6.4.26.4.2 Automated web attack detection and prevention15
6.5.56.5.5 No live PANs in pre-production11
6.5.66.5.6 Remove test data and accounts before production12
7.1.17.1.1 Requirement 7 policies and procedures maintained17
7.1.27.1.2 Requirement 7 roles and responsibilities assigned13
7.2.17.2.1 Access control model defined25
7.2.27.2.2 User access assigned by job function and least privilege27
7.2.37.2.3 Privileges approved by authorized personnel20
7.2.5.17.2.5.1 Application and system account access reviewed periodically15
7.3.27.3.2 Access control system enforces role-based permissions17
7.3.37.3.3 Access control default deny all18
8.2.18.2.1 Unique ID assigned to every user23
8.2.28.2.2 Shared and generic IDs only by exception21
8.2.38.2.3 Service provider unique factors per customer9
8.2.48.2.4 User ID lifecycle changes authorized19
8.2.58.2.5 Terminated users' access revoked immediately21
8.2.68.2.6 Inactive accounts removed within 90 days18
8.2.78.2.7 Third-party remote access accounts controlled19
8.2.88.2.8 Re-authentication after 15 minutes idle14
8.3.18.3.1 Access authenticated with at least one factor24
8.3.108.3.10 Service provider customer password guidance10
8.3.10.18.3.10.1 Service provider customer passwords 90 days or dynamic6
8.3.118.3.11 Tokens, smart cards and certificates individually assigned11
8.3.28.3.2 Authentication factors unreadable with strong cryptography21
8.3.38.3.3 Identity verified before factor changes12
8.3.48.3.4 Lockout after 10 attempts for 30 minutes17
8.3.58.3.5 Initial and reset passwords unique and changed14
8.3.68.3.6 Password minimum length 12 and complexity20
8.3.78.3.7 No reuse of last four passwords12
8.3.88.3.8 Authentication policies communicated to users18
8.3.98.3.9 Single-factor passwords changed every 90 days or dynamic analysis12
8.4.18.4.1 MFA for non-console administrative CDE access23
8.4.28.4.2 MFA for all non-console CDE access24
8.4.38.4.3 MFA for remote access that could reach CDE22
8.5.18.5.1 MFA system resistant to replay and bypass20
9.1.19.1.1 Requirement 9 policies and procedures maintained16
9.1.29.1.2 Requirement 9 roles and responsibilities assigned15
9.2.19.2.1 Facility entry controls for CDE systems19
9.2.1.19.2.1.1 Monitoring of entry to sensitive areas18
9.2.29.2.2 Controls on publicly accessible network jacks17
9.2.39.2.3 Physical protection of network hardware and lines20
9.2.49.2.4 Locking of consoles in sensitive areas10
9.3.19.3.1 Personnel physical access procedures for the CDE19
9.3.1.19.3.1.1 Personnel access to sensitive areas controlled16
9.3.29.3.2 Visitor access procedures for the CDE15
9.3.39.3.3 Visitor badges returned or deactivated12
9.3.49.3.4 Visitor logs for facility and sensitive areas12
9.4.19.4.1 Physical security of all media18
9.4.1.19.4.1.1 Secure storage location for offline backups19
9.4.1.29.4.1.2 Annual review of offline backup location security15
9.4.29.4.2 Classification of media by data sensitivity17
9.4.39.4.3 Securing media sent outside the facility16
9.4.49.4.4 Management approval for media leaving facility14
9.4.59.4.5 Inventory logs of electronic media16
9.4.5.19.4.5.1 Annual inventories of electronic media15
9.4.69.4.6 Destruction of hard-copy materials15
9.4.79.4.7 Destruction of electronic media19
9.5.19.5.1 Protection of POI devices from tampering11
9.5.1.19.5.1.1 Current register of POI devices12
9.5.1.29.5.1.2 Periodic inspection of POI device surfaces8
9.5.1.39.5.1.3 Training for personnel in POI environments14
1.11.1 Governance of network security control processes0
1.21.2 Configuration and maintenance of NSCs0
1.31.3 Restriction of CDE network access0
1.41.4 Control of trusted and untrusted network connections0
1.51.5 Risk from dual-connected computing devices0
10.110.1 Logging and monitoring governance defined0
10.210.2 Audit logs support anomaly detection and forensics0
10.310.3 Audit logs protected from destruction and tampering0
10.410.4 Audit logs reviewed for anomalies0
10.510.5 Audit log history retained0
10.610.6 Time synchronization across systems0
10.710.7 Critical security control failures handled promptly0
11.111.1 Governance of security testing activities0
11.211.2 Wireless access point detection0
11.311.3 Vulnerability scanning0
11.411.4 Penetration testing0
11.511.5 Intrusion and change detection0
11.611.6 Payment page change detection0
12.112.1 Overall information security policy0
12.1012.10 Security incident response0
12.212.2 Acceptable use of end-user technologies0
12.312.3 Risk identification and management for the CDE0
12.412.4 PCI DSS compliance management0
12.512.5 PCI DSS scope documentation and validation0
12.612.6 Security awareness education0
12.712.7 Personnel screening0
12.812.8 Third-party service provider risk management0
12.912.9 TPSP support for customer compliance0
2.12.1 Governance of secure configuration processes0
2.22.2 Secure configuration and management of system components0
2.32.3 Secure wireless configuration and management0
3.13.1 Governance of stored account data protection0
3.1.13.1.1 Requirement 3 policies and procedures maintained and in use17
3.1.23.1.2 Assigned duties for Requirement 3 activities16
3.23.2 Minimising account data storage0
3.2.13.2.1 Data retention and disposal minimise stored account data23
3.33.3 No SAD retained after authorization0
3.3.13.3.1 SAD not retained after authorization, even encrypted10
3.43.4 Restricting PAN display and copying0
3.4.13.4.1 PAN masked on display except for authorized roles11
3.53.5 PAN protected wherever stored0
3.63.6 Securing cryptographic keys0
3.6.13.6.1 Procedures protect keys against disclosure and misuse19
3.73.7 Key lifecycle management0
3.7.13.7.1 Generation of strong cryptographic keys18
4.14.1 Governance for encrypting PAN in transit0
4.24.2 PAN encrypted while in transit0
5.15.1 Governance for malware protection0
5.25.2 Malware prevented or detected and addressed0
5.2.15.2.1 Anti-malware deployed on all system components24
5.2.25.2.2 Anti-malware detects and handles all known malware22
5.2.35.2.3 Periodic evaluation of components not at risk from malware14
5.35.3 Anti-malware kept active, current and monitored0
5.3.15.3.1 Anti-malware kept current through automatic updates21
5.3.25.3.2 Periodic and real-time scans or continuous behavioural analysis18
5.3.35.3.3 Anti-malware covers removable electronic media18
5.45.4 Anti-phishing protection for personnel0
6.16.1 Governance of secure systems and software processes0
6.26.2 Secure development of bespoke and custom software0
6.36.3 Identifying and addressing security vulnerabilities0
6.3.16.3.1 Vulnerability identification and risk ranking26
6.3.26.3.2 Inventory of bespoke software and components21
6.3.36.3.3 Timely installation of security patches27
6.46.4 Protection of public-facing web applications0
6.4.36.4.3 Payment page script management15
6.56.5 Secure management of changes0
6.5.16.5.1 Change control procedure for production21
6.5.26.5.2 Confirm PCI DSS controls after significant change20
6.5.36.5.3 Separate pre-production from production21
6.5.46.5.4 Separate roles between production and pre-production19
7.17.1 Governance of need-to-know access restriction0
7.27.2 Access defined and assigned appropriately0
7.2.47.2.4 User accounts and privileges reviewed every six months24
7.2.57.2.5 Application and system accounts least privilege19
7.2.67.2.6 Query access to stored cardholder data restricted15
7.37.3 Access managed through access control systems0
7.3.17.3.1 Need-to-know access control system covers all components20
8.18.1 Governance of identification and authentication0
8.1.18.1.1 Requirement 8 policies and procedures maintained17
8.1.28.1.2 Requirement 8 roles and responsibilities assigned15
8.28.2 User identification and account lifecycle0
8.38.3 Strong user and administrator authentication0
8.48.4 MFA for access into the CDE0
8.58.5 MFA systems configured against misuse0
8.68.6 Application and system account management0
8.6.18.6.1 Interactive use of system accounts controlled15
8.6.28.6.2 No hard-coded passwords for interactive system accounts18
8.6.38.6.3 System account passwords protected against misuse18
9.19.1 Physical access governance defined and understood0
9.29.2 Physical entry controls for facilities and CDE systems0
9.39.3 Authorization and management of personnel and visitor access0
9.49.4 Secure storage, access, distribution and destruction of media0
9.59.5 POI devices protected from tampering and substitution0
9.5.1.2.19.5.1.2.1 Risk-based frequency and type of POI inspections0
A1.1A1.1 Separation and protection of customer environments0
A1.1.1A1.1.1 Logical separation between provider and customer environments0
A1.1.2A1.1.2 Customers limited to their own cardholder data and CDE0
A1.1.3A1.1.3 Customers restricted to their allocated resources0
A1.1.4A1.1.4 Penetration testing of tenant separation every six months0
A1.2A1.2 Per-customer logging and incident support0
A1.2.1A1.2.1 Per-customer audit logging consistent with Requirement 100
A1.2.2A1.2.2 Support for prompt forensic investigation of any customer0
A1.2.3A1.2.3 Customer reporting and remediation of incidents and vulnerabilities0
A2.1A2.1 SSL/early TLS POI terminals free of known exploits0
A2.1.1A2.1.1 Confirm SSL/early TLS POS POI devices resist known exploits0
A2.1.2A2.1.2 Risk Mitigation and Migration Plan for SSL/early TLS connections0
A2.1.3A2.1.3 Service providers offer a secure protocol option0
A3.1A3.1 PCI DSS compliance program0
A3.1.1A3.1.1 Executive management responsibility for the PCI DSS compliance program0
A3.1.2A3.1.2 Formal PCI DSS compliance program elements0
A3.1.3A3.1.3 Defined and assigned PCI DSS compliance roles0
A3.1.4A3.1.4 Annual PCI DSS training for compliance personnel0
A3.2A3.2 Scope documentation and validation0
A3.2.1A3.2.1 Quarterly and change-driven scope documentation and validation0
A3.2.2A3.2.2 Scope impact of every system or network change0
A3.2.2.1A3.2.2.1 Post-change confirmation that PCI DSS controls are in place0
A3.2.3A3.2.3 Scope review after organizational structure changes0
A3.2.4A3.2.4 Six-monthly penetration testing of segmentation controls0
A3.2.5A3.2.5 Data-discovery methodology for cleartext PAN0
A3.2.5.1A3.2.5.1 Annual confirmation of data-discovery effectiveness0
A3.2.5.2A3.2.5.2 Response procedures when cleartext PAN is found outside the CDE0
A3.2.6A3.2.6 Mechanisms to detect and block cleartext PAN leaving the CDE0
A3.2.6.1A3.2.6.1 Response procedures for attempted removal of cleartext PAN0
A3.3A3.3 PCI DSS in business-as-usual activities0
A3.3.1A3.3.1 Prompt detection and alerting of critical security control failures0
A3.3.1.1A3.3.1.1 Prompt response to critical security control failures0
A3.3.2A3.3.2 Annual review of hardware and software technologies0
A3.3.3A3.3.3 Quarterly review that BAU activities are followed0
A3.4A3.4 Control of logical access to the CDE0
A3.4.1A3.4.1 Six-monthly review of user accounts and access privileges0
A3.5A3.5 Identification and response to suspicious events0
A3.5.1A3.5.1 Methodology for prompt detection of attack patterns1
APPENDIX-A1Appendix A1 Extra requirements for multi-tenant service providers0
APPENDIX-A2Appendix A2 SSL and early TLS on card-present POS POI terminals0
APPENDIX-A3Appendix A3 DESV supplemental validation for designated entities0
APPLICABILITYWho PCI DSS applies to and which data it protects0
APPROACHESDefined approach, customized approach and compensating controls (Appendices B to E)0
ASSESSMENTHow PCI DSS is assessed: sampling, testing methods, reporting and protected artefacts0
SCOPEScope of the requirements: the cardholder data environment, segmentation and third-party service providers0
STANDARDPCI DSS v4.0.1: the standard and its edition0
TIMEFRAMESTimeframes, business-as-usual practice and missed activities0

Tell me when PCI DSS 4.0 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Annual review
  • Supplier inventory + classification
  • Risk assessments per supplier
  • Contractual cyber clauses
  • ENISA coordinated risk assessment alignment
  • DORA TPRM cross-walk
  • Annual review records
  • Approval record
  • KB articles
  • Documentation standards

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for PCI DSS 4.0, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition