22 mapped controls · identifier-only informative references · Protect function · one implementation can answer several obligations at once.
| ISO/IEC 27001:2022 | Relationship | Source tier |
|---|---|---|
| A.5.1 | related | Tier A2 |
| A.5.10 | related | Tier A2 |
| A.5.13 | related | Tier A2 |
| A.5.14 | related | Tier A2 |
| A.5.15 | related | Tier A2 |
| A.5.3 | related | Tier A2 |
| A.6.1 | related | Tier A2 |
| A.6.2 | related | Tier A2 |
| A.6.5 | related | Tier A2 |
| A.7.10 | related | Tier A2 |
| A.7.7 | related | Tier A2 |
| A.8.17 | related | Tier A2 |
| A.8.19 | related | Tier A2 |
| A.8.2 | related | Tier A2 |
| A.8.22 | related | Tier A2 |
| A.8.26 | related | Tier A2 |
| A.8.3 | related | Tier A2 |
| A.8.4 | related | Tier A2 |
| A.8.7 | related | Tier A2 |
| A.8.8 | related | Tier A2 |
| Clause 4.2(b) | related | Tier A2 |
| Clause 5.2 | 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. An ISO/IEC 27001 auditor works outward from your Statement of Applicability, so the artifact has to be traceable to the Annex A control you claimed - the mapping tells you which claim your evidence already serves. Keeping one dated evidence register per control means a single artifact answers both frameworks instead of being produced twice.
