4 mapped controls · identifier-only informative references · Detect function · one implementation can answer several obligations at once.
| PCI DSS v4.0 | Relationship | Source tier |
|---|---|---|
| 10.3.1 | related | Tier A2 |
| 10.3.3 | related | Tier A2 |
| 12.10.1 | related | Tier A2 |
| 12.10.3 | related | Tier A2 |
Assessors working from either framework ask for the same thing against DE.AE-06: operational artifacts - alert and monitoring configuration exports, dated tuning records, sample detections with their triage outcome, and log-retention settings that prove coverage across the audit window. 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.
