NIST CSF 2.0 to PCI DSS 4.0 crosswalk

29 control objectives in NIST Cybersecurity Framework are mapped here to PCI DSS. 1 of them has no direct PCI DSS 4.0 requirement, which is marked in the table. Each row is one shared objective, with the requirement ids on both sides.

Control objective	NIST CSF 2.0	PCI DSS 4.0
Security governance and policies	`GV.PO`Policy `GV.OV`Oversight	`12.1`A comprehensive information security policy is established, published, maintained and disseminated `12.4`PCI DSS compliance is managed
Security roles and accountability	`GV.RR`Roles, responsibilities and authorities	`12.1.3`Security policy defines information security roles and responsibilities `12.4.1`Executive management responsibility for protection of cardholder data (service providers)
Risk assessment and treatment	`GV.RM`Risk management strategy `ID.RA`Risk assessment	`12.3`Risks to the cardholder data environment are formally identified, evaluated and managed `12.3.1`Targeted risk analysis for requirements with flexible frequency
Asset and system inventory	`ID.AM`Asset management	`12.5.1`Inventory of system components in scope for PCI DSS is maintained `12.5.2`PCI DSS scope is documented and confirmed at least every 12 months
Data classification and handling	`ID.AM-07`Inventories of data and corresponding metadata are maintained `PR.DS`Data security	`12.5.2`PCI DSS scope is documented and confirmed (includes identifying all data flows)
Access provisioning, review and removal	`PR.AA-05`Access permissions, entitlements and authorizations are defined and managed (least privilege, separation of duties)	`7.2`Access to system components and data is appropriately defined and assigned (incl. 7.2.4 six-month review) `7.3`Access is managed via an access control system `8.2.5`Access for terminated users is immediately revoked
Least privilege and privileged access	`PR.AA-05`Access permissions managed incorporating least privilege	`7.2.1`An access control model is defined `7.2.2`Access assigned based on job classification and least privileges
Authentication, unique IDs and multi-factor authentication	`PR.AA-03`Users, services and hardware are authenticated	`8.2`User identification and related accounts are strictly managed `8.3`Strong authentication for users and administrators is established and managed `8.4`Multi-factor authentication is implemented `8.5`MFA systems are configured to prevent misuse
Encryption at rest and key management	`PR.DS-01`The confidentiality, integrity and availability of data-at-rest are protected	`3.5`Primary account number is secured wherever it is stored `3.6`Cryptographic keys used to protect stored account data are secured `3.7`Key management processes and procedures are defined and implemented
Encryption in transit	`PR.DS-02`The confidentiality, integrity and availability of data-in-transit are protected	`4.2`PAN is protected with strong cryptography during transmission `2.2.7`All non-console administrative access is encrypted
Network security and segmentation	`PR.IR-01`Networks and environments are protected from unauthorized logical access and usage	`1.2`Network security controls are configured and maintained `1.3`Network access to and from the cardholder data environment is restricted `1.4`Network connections between trusted and untrusted networks are controlled
Secure configuration and hardening	`PR.PS-01`Configuration management practices are established and applied	`2.2`System components are configured and managed securely
Vulnerability scanning and patching	`ID.RA`Risk assessment (vulnerability identification, ID.RA-01) `PR.PS-02`Software is maintained, replaced and removed commensurate with risk	`6.3`Security vulnerabilities are identified and addressed `11.3`External and internal vulnerabilities are regularly identified, prioritized and addressed
Penetration testing and independent assessment	`ID.IM`Improvement (incl. ID.IM-02, improvements from tests and exercises)	`11.4`External and internal penetration testing is regularly performed
Logging, log review and monitoring	`DE.CM`Continuous monitoring `PR.PS-04`Log records are generated and made available for continuous monitoring	`10.2`Audit logs are implemented to support detection of anomalies and suspicious activity `10.3`Audit logs are protected from destruction and unauthorized modification `10.4`Audit logs are reviewed to identify anomalies or suspicious activity `10.5`Audit log history is retained and available for analysis `10.6`Time-synchronization mechanisms support consistent time settings
Intrusion detection and integrity monitoring	`DE.CM`Continuous monitoring `DE.AE`Adverse event analysis	`11.5`Network intrusions and unexpected file changes are detected and responded to `11.6`Unauthorized changes on payment pages are detected and responded to
Malware protection	`PR.PS-05`Installation and execution of unauthorized software are prevented `DE.CM`Continuous monitoring	`5.2`Malicious software is prevented, or detected and addressed `5.3`Anti-malware mechanisms and processes are active, maintained and monitored `5.4`Anti-phishing mechanisms protect users against phishing attacks
Incident response and breach notification	`RS.MA`Incident management `RS.AN`Incident analysis `RS.CO`Incident response reporting and communication `RS.MI`Incident mitigation `DE.AE`Adverse event analysis	`12.10`Suspected and confirmed security incidents that could impact the CDE are responded to immediately (12.10.1 IR plan, 12.10.2 annual review and test)
Change management	`PR.PS-01`Configuration management practices are established and applied	`6.5`Changes to all system components are managed securely (6.5.1 change control procedures)
Secure software development	`PR.PS-06`Secure software development practices are integrated and their performance monitored	`6.2`Bespoke and custom software is developed securely `6.4`Public-facing web applications are protected against attacks
Third-party and vendor risk management	`GV.SC`Cybersecurity supply chain risk management	`12.8`Risk to information assets associated with third-party service provider relationships is managed `12.9`Third-party service providers support their customers' PCI DSS compliance
Business continuity and disaster recovery	`PR.IR-03`Mechanisms are implemented to achieve resilience requirements `RC.RP`Incident recovery plan execution	`12.10.1`Incident response plan includes business recovery and continuity procedures
Backup and redundancy	`PR.DS-11`Backups of data are created, protected, maintained and tested	`12.10.1`Incident response plan includes data backup processes `9.4.1.1`Offline media backups with cardholder data are stored in a secure location
Capacity and availability management	`PR.IR-04`Adequate resource capacity to ensure availability is maintained	no direct requirement
Security awareness and training	`PR.AT`Awareness and training	`12.6`Security awareness education is an ongoing activity (12.6.1 program, 12.6.2 annual review, 12.6.3 training at hire and annually)
Personnel screening, terms and sanctions	`GV.RR-04`Cybersecurity is included in human resources practices	`12.7`Personnel are screened to reduce risks from insider threats
Physical access and facility security	`PR.AA-06`Physical access to assets is managed, monitored and enforced commensurate with risk	`9.2`Physical access controls manage entry into facilities and systems containing cardholder data `9.3`Physical access for personnel and visitors is authorized and managed
Data retention, media handling and secure disposal	`ID.AM-08`Systems, hardware, software, services and data are managed throughout their life cycles	`3.2`Storage of account data is kept to a minimum (3.2.1 retention and disposal) `9.4`Media with cardholder data is securely stored, accessed, distributed and destroyed
Ongoing control monitoring and internal audit	`ID.IM`Improvement `GV.OV`Oversight	`12.4.2`Reviews confirm personnel perform tasks per policy (service providers)

Open a control objective for the evidence checklist.PCI DSS 4.0 to NIST CSF 2.0 →

Scope: Mapped at category level (e.g. PR.AA) or subcategory where one is clearly the match (e.g. PR.AA-05). Mapped at requirement / sub-requirement level. Many PCI requirements only apply to the cardholder data environment (CDE) or to service providers. A mapping means the requirements address the same objective. It does not mean satisfying one satisfies the other, because scope, frequency and evidence rules differ.

More from NIST CSF 2.0

NIST CSF 2.0 to SOC 2 NIST CSF 2.0 to ISO 27001:2022 NIST CSF 2.0 to HIPAA Security Rule NIST CSF 2.0 to NIST 800-53 r5