DivisionCero
PCI DSS and Kudo

PCI DSS Controls with ISMS

Control-by-control mapping between PCI DSS and the Kudo ISMS, with the complete structure ready for audits and evidence.

Table of the 63 PCI DSS v4.0 sub-requirements organized by requirement and mapped to the Kudo ISMS policies.

Req. 1 — Install and Maintain Network Security Controls

CodeISMS Policy
1.1Communications Security Policy
1.2Communications Security Policy
1.3Communications Security Policy
1.4Communications Security Policy
1.5Communications Security Policy

Req. 2 — Apply Secure Configurations to All System Components

CodeISMS Policy
2.1Hardening Policy
2.2Hardening Policy
2.3Change and Configuration Management Policy

Req. 3 — Protect Stored Account Data

CodeISMS Policy
3.1Privacy Policy
3.2Privacy Policy
3.3Privacy Policy
3.4Privacy Policy
3.5Communications Security Policy
3.6Communications Security Policy
3.7Asset Management Policy

Req. 4 — Protect Cardholder Data with Strong Cryptography During Transmission

CodeISMS Policy
4.1Communications Security Policy
4.2Communications Security Policy

Req. 5 — Protect All Systems and Networks from Malicious Software

CodeISMS Policy
5.1Hardening Policy
5.2Hardening Policy
5.3Hardening Policy
5.4Awareness Management Policy

Req. 6 — Develop and Maintain Secure Systems and Software

CodeISMS Policy
6.1Secure Development Policy
6.2Secure Development Policy
6.3Hardening Policy
6.4Secure Development Policy
6.5Change and Configuration Management Policy

Req. 7 — Restrict Access to System Components and Cardholder Data

CodeISMS Policy
7.1Access Management Policy
7.2Access Management Policy
7.3Access Management Policy

Req. 8 — Identify Users and Authenticate Access to System Components

CodeISMS Policy
8.1Access Management Policy
8.2Access Management Policy
8.3Access Management Policy
8.4Access Management Policy
8.5Access Management Policy
8.6Access Management Policy

Req. 9 — Restrict Physical Access to Cardholder Data

CodeISMS Policy
9.1Physical Security Policy
9.2Physical Security Policy
9.3Physical Security Policy
9.4Physical Security Policy
9.5Physical Security Policy

Req. 10 — Log and Monitor All Access to System Components and Cardholder Data

CodeISMS Policy
10.1Logging and Monitoring Policy
10.2Logging and Monitoring Policy
10.3Logging and Monitoring Policy
10.4Logging and Monitoring Policy
10.5Documents and Records Policy
10.6Logging and Monitoring Policy
10.7Incident Management Policy

Req. 11 — Test Security of Systems and Networks Regularly

CodeISMS Policy
11.1Hardening Policy
11.2Hardening Policy
11.3Hardening Policy
11.4Incident Management Policy
11.5Logging and Monitoring Policy
11.6Logging and Monitoring Policy

Req. 12 — Support Information Security with Organizational Policies and Programs

CodeISMS Policy
12.1Information Security Policy
12.2Risk Management Policy
12.3Risk Management Policy
12.4Compliance Management Policy
12.5Compliance Management Policy
12.6Awareness Management Policy
12.7Human Resources Security Policy
12.8Vendor Management Policy
12.9Vendor Management Policy
12.10Incident Management Policy

PCI DSS with ISMS

Overview of PCI DSS mapped to the Kudo ISMS: domains, scope and equivalences between both cybersecurity frameworks.

Domain Mapping

Graphical mapping between PCI DSS and Kudo domains

On this page

Req. 1 — Install and Maintain Network Security ControlsReq. 2 — Apply Secure Configurations to All System ComponentsReq. 3 — Protect Stored Account DataReq. 4 — Protect Cardholder Data with Strong Cryptography During TransmissionReq. 5 — Protect All Systems and Networks from Malicious SoftwareReq. 6 — Develop and Maintain Secure Systems and SoftwareReq. 7 — Restrict Access to System Components and Cardholder DataReq. 8 — Identify Users and Authenticate Access to System ComponentsReq. 9 — Restrict Physical Access to Cardholder DataReq. 10 — Log and Monitor All Access to System Components and Cardholder DataReq. 11 — Test Security of Systems and Networks RegularlyReq. 12 — Support Information Security with Organizational Policies and Programs