NIST Cybersecurity Framework ↔ PCI DSS
15 canonical controls in Keel's library satisfy clauses of both NIST Cybersecurity Framework and PCI DSS. Implement each once, attach the evidence once, and it counts toward each standard. The overlap is the work you don't repeat.
Controls that satisfy both
| Canonical control | NIST Cybersecurity Framework clauses | PCI DSS clauses |
|---|---|---|
| Information security policy A board-approved information security policy set, reviewed at least annually and communicated to the workforce. | GV.PO-01 | 12.1 |
| Risk assessment & treatment A documented process to identify, analyze, evaluate, and treat information security risks on a defined cadence. | ID.RA-01 | 12.3 |
| Access control policy Rules for granting, reviewing, and revoking access to systems and data based on business need and least privilege. | PR.AA-05 | 7.1, 7.2 |
| User provisioning & deprovisioning Joiner/mover/leaver process to grant, change, and promptly remove access across systems. | PR.AA-01 | 8.2 |
| Multi-factor authentication MFA enforced for remote access, administrative access, and access to sensitive systems and data. | PR.AA-03 | 8.4, 8.5 |
| Encryption in transit & at rest Strong cryptography protects sensitive data in transit over public networks and at rest in storage. | PR.DS-01, PR.DS-02 | 3.5, 4.2 |
| Logging & monitoring Security-relevant events are logged, protected, retained, and reviewed for anomalies. | DE.CM-09 | 10.2, 10.3, 10.4 |
| Vulnerability management Regular scanning, prioritization, and remediation of vulnerabilities across systems and applications. | ID.RA-01 | 6.3, 11.3 |
| Malware protection Anti-malware controls prevent, detect, and respond to malicious software on endpoints and servers. | PR.PS-05 | 5.2, 5.3 |
| Incident response A documented, tested plan to detect, triage, contain, remediate, and communicate security incidents. | RS.MA-01 | 12.10 |
| Change management Changes to systems and software are requested, reviewed, tested, approved, and tracked. | PR.PS-01 | 6.5 |
| Third-party / vendor risk management Due diligence, contractual safeguards, and ongoing monitoring of vendors that handle your data. | GV.SC-01 | 12.8 |
| Security awareness training Ongoing security awareness training for all personnel, with completion tracking. | PR.AT-01 | 12.6 |
| Asset inventory An inventory of hardware, software, and information assets with assigned owners. | ID.AM-01, ID.AM-02 | 12.5 |
| Network security controls Firewalls/segmentation and network controls restrict traffic to and from sensitive environments. | PR.IR-01 | 1.2, 1.3 |
Clause identifiers (NIST Cybersecurity Framework and PCI DSS) are referenced factually for mapping. Keel is not affiliated with or endorsed by the bodies that publish these standards. Control descriptions are Keel's own; a framework's full authored control count is on its framework page.
Why this is one project, not two
On a crosswalk-native model, PCI DSS mostly lights up controls you already built for NIST Cybersecurity Framework. You're not re-uploading the same screenshot for a second audit. You apply the framework and see the genuine delta worth working. That's the whole idea behind collect once, comply everywhere.