15 mapped controls · identifier-only informative references · Govern function · one implementation can answer several obligations at once.
| PCI DSS v4.0 | Relationship | Source tier |
|---|---|---|
| 10.4.2.1 | related | Tier A2 |
| 11.3.1.1 | related | Tier A2 |
| 11.6.1 | related | Tier A2 |
| 12.10.4.1 | related | Tier A2 |
| 12.3.3 | related | Tier A2 |
| 12.3.4 | related | Tier A2 |
| 12.5.3 | related | Tier A2 |
| 12.8.3 | related | Tier A2 |
| 5.2.3.1 | related | Tier A2 |
| 5.3.2.1 | related | Tier A2 |
| 6.3.1 | related | Tier A2 |
| 6.3.3 | related | Tier A2 |
| 7.2.5.1 | related | Tier A2 |
| 8.6.3 | related | Tier A2 |
| 9.5.1.2.1 | related | Tier A2 |
Assessors working from either framework ask for the same thing against GV.RM-03: governance artifacts - approved policy documents with named owners, dated management review minutes, delegation-of-authority records, and evidence that the policy was communicated to the people it binds. A PCI DSS assessor scopes to the cardholder data environment first, so the same artifact can satisfy a requirement inside scope and be irrelevant outside it - the mapping tells you where to look, not whether you are in scope. Keeping one dated evidence register per control means a single artifact answers both frameworks instead of being produced twice.
