5 mapped controls · identifier-only informative references · Identify function · one implementation can answer several obligations at once.
| PCI DSS v4.0 | Relationship | Source tier |
|---|---|---|
| 11.3.1 | related | Tier A2 |
| 11.3.2 | related | Tier A2 |
| 11.4.4 | related | Tier A2 |
| 6.3.1 | related | Tier A2 |
| 6.3.2 | related | Tier A2 |
Assessors working from either framework ask for the same thing against ID.RA-01: inventory and assessment artifacts - asset and data registers with owners and dates, risk assessment output, vendor and dependency lists, and the criticality ratings that justify scope decisions. 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.
