CIS Controls v8 CIS-17.8: Conduct Post-Incident Reviews

What else in your programme already covers this

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

ISO 22301:2019 · 4 controls

10.1 Nonconformity and corrective action
10.2 Continual improvement
8.6 Evaluation of business continuity documentation and capabilities
9.3.2 Management review input

HIPAA Security Rule · 3 controls

164.308(a)(6)(ii) Response and Reporting (Required)
164.308(a)(8) Evaluation (Standard)
164.316(b)(2)(iii) Updates (Documentation)

ISO 27701:2019 · 3 controls

5.7 Performance evaluation
5.8 Improvement
6.13.1 Management of information security incidents and improvements

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-GV.OV-03 Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed
NIST-CSF-ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities
NIST-CSF-RS.AN-08 An incident's magnitude is estimated and validated

NIST SP 800-53 Rev 5 · 3 controls

NIST800-IR-4 IR-4 Incident Handling
NIST800-IR-8 IR-8 Incident Response Plan
SP800-53-IR Incident Response Family

FedRAMP High · 2 controls

IR-4 Incident Handling
IR-8 Incident Response Plan

FedRAMP Moderate · 2 controls

IR-4 Incident Handling
IR-8 Incident Response Plan

ISO 27001:2022 · 2 controls

5.26 Response to information security incidents
5.27 Learning from information security incidents

ISO 27002:2022 · 2 controls

5.26 Response to information security incidents
5.27 Learning from information security incidents

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(6)(ii) Response and Reporting (Required)
164.308(a)(8) Evaluation (Standard)

PCI DSS 4.0 · 2 controls

10.7.3 10.7.3 Respond promptly to critical security control failures
12.10.6 12.10.6 Plan evolved from lessons learned and industry developments

SOC 2 · 2 controls

SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
SOC2-CC7.5 CC7.5 Recovering from security incidents

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

ANSSI-HYG-40 Define a Security Incident Management Procedure

APRA CPS 230 Operational Risk Management · 1 control

CPS230-27 Identification and Escalation of Incidents and Near Misses

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

Australian Information Security Manual · 1 control

ISM-1213 Traffic capture after intrusion remediation

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.1 Incident Handling

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

CCM-SEF-05 Incident Response Metrics

DORA · 1 control

DORA-Art.13 Learning and evolving

ISO/IEC 42001:2023 · 1 control

10.2 Nonconformity and corrective action

NIST SP 800-161 Rev 1 · 1 control

161R1-PM-6 Measures of Performance

NIST SP 800-171 Rev 3 · 1 control

03.06.01 Incident Handling

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 CIS Controls v8 have you already done?

CIS Controls v8 CIS-17.8 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

If you hold ISO 27001:202266.7% covered · 51 gaps If you hold FedRAMP Moderate62.7% covered · 57 gaps If you hold NIST SP 800-53 Rev 557.5% covered · 65 gaps If you hold NIST Cybersecurity Framework 2.050.3% covered · 76 gaps If you hold ISO 27002:202249.7% covered · 77 gaps If you hold Azure Security Benchmark49% covered · 78 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. 240 were rejected on the ISO 27001:2022 pair alone.

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