PCI DSS 4.0 12.10.6: 12.10.6 Plan evolved from lessons learned and industry developments

What else in your programme already covers this

This control maps to 42 controls across 24 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST Cybersecurity Framework 2.0 · 5 controls

NIST-CSF-GV.OV-03 Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed
NIST-CSF-ID.IM-01 Improvements are identified from evaluations
NIST-CSF-ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities
NIST-CSF-RC.RP-06 The end of incident recovery is declared based on criteria, and incident-related documentation is completed
NIST-CSF-RS.AN-08 An incident's magnitude is estimated and validated

NIST SP 800-53 Rev 5 · 5 controls

NIST800-CP-4 CP-4 Contingency Plan Testing
NIST800-IR-3 IR-3 Incident Response Testing
NIST800-IR-4 IR-4 Incident Handling
NIST800-IR-8 IR-8 Incident Response Plan
NIST800-PM-12 PM-12 Insider Threat Program

SOC 2 · 5 controls

SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
SOC2-CC7.4 CC7.4 Responding to security incidents
SOC2-CC7.5 CC7.5 Recovering from security incidents

ISO 22301:2019 · 4 controls

10.1 Nonconformity and corrective action
10.2 Continual improvement
8.5 Exercise programme
9.3.2 Management review input

ISO 27701:2019 · 3 controls

5.8.2 Continual improvement
6.13 Information security incident management
6.13.1 Management of information security incidents and improvements

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

CFTC-SS-16 Security Incident Response Plan and Testing
CFTC-SS-21 Remediation of Vulnerabilities and Deficiencies

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-40 Define a Security Incident Management Procedure

APRA CPS 234 · 1 control

CPS234-P25 Response Plan Content and Escalation Mechanisms

AWS Well-Architected Security Pillar · 1 control

SEC10-BP08 Establish a framework for learning from incidents

Azure Security Benchmark · 1 control

ASBv3-IR-7 Post-incident activity - conduct lesson learned and retain evidence

C5 (Germany) · 1 control

C5-SIM-05 Evaluation and learning process

CMMC 2.0 · 1 control

IR.L2-3.6.3 Incident Response Testing

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-SEF-05 Incident Response Metrics

FedRAMP High · 1 control

IR-4 Incident Handling

ISO 27001:2022 · 1 control

5.27 Learning from information security incidents

ISO 27002:2022 · 1 control

5.27 Learning from information security incidents

ISO/IEC 42001:2023 · 1 control

10.1 Continual improvement

NIST SP 800-161 Rev 1 · 1 control

161R1-IR-8 Incident Response Plan

NIST SP 800-171 Rev 3 · 1 control

03.06.05 Incident Response Plan

NIST SP 800-172 · 1 control

3.11.5e Assess Effectiveness of Security Solutions

NIST SP 800-218 · 1 control

SP800-218-RV.3.4 Document Lessons Learned

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 12.10.6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202249.6% covered · 141 gaps If you hold FedRAMP Moderate49.3% covered · 142 gaps If you hold NIST SP 800-53 Rev 547.5% covered · 147 gaps If you hold ISO 27002:202243.2% covered · 159 gaps If you hold CIS Controls v838.2% covered · 173 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 each Browse the graph free