10 mapped controls · identifier-only informative references · Protect function · one implementation can answer several obligations at once.
| PCI DSS v4.0 | Relationship | Source tier |
|---|---|---|
| 3.3.1 | related | Tier A2 |
| 3.5.1 | related | Tier A2 |
| 3.5.1.3 | related | Tier A2 |
| 3.6.1 | related | Tier A2 |
| 3.6.1.1 | related | Tier A2 |
| 3.6.1.2 | related | Tier A2 |
| 3.6.1.3 | related | Tier A2 |
| 3.6.1.4 | related | Tier A2 |
| 9.4.6 | related | Tier A2 |
| 9.4.7 | related | Tier A2 |
Assessors working from either framework ask for the same thing against PR.DS-01: implementation artifacts - configuration exports or baseline snapshots, access-control records showing who approved which grant, change tickets tied to the control, and training completion records. 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.
