Azure Security Benchmark ASBv3-IR-7: Post-incident activity - conduct lesson learned and retain evidence

What else in your programme already covers this

This control maps to 43 controls across 25 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 · 4 controls

NIST-CSF-ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities
NIST-CSF-RS.AN-06 Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved
NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved
NIST-CSF-RS.AN-08 An incident's magnitude is estimated and validated

CIS Controls v8 · 3 controls

CIS-16.3 Perform Root Cause Analysis on Security Vulnerabilities
CIS-17.8 Conduct Post-Incident Reviews
CIS-8.10 Retain Audit Logs

APRA CPS 234 · 2 controls

CPS234-32 Annual Review and Testing of Response Plans
CPS234-P25 Response Plan Content and Escalation Mechanisms

AWS Well-Architected Security Pillar · 2 controls

SEC10-BP03 Prepare forensic capabilities
SEC10-BP08 Establish a framework for learning from incidents

C5 (Germany) · 2 controls

C5-SIM-03 Documentation and reporting of security incidents
C5-SIM-05 Evaluation and learning process

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

CCM-LOG-02 Audit Logs Protection
CCM-SEF-05 Incident Response Metrics

FedRAMP High · 2 controls

AU-11 Audit Record Retention
IR-4 Incident Handling

FedRAMP Moderate · 2 controls

AU-11 Audit Record Retention
IR-4 Incident Handling

HIPAA Security Rule · 2 controls

164.308(a)(6)(ii) Response and Reporting (Required)
164.316(b)(2)(i) Time Limit (Documentation Retention)

ISO 27001:2022 · 2 controls

5.27 Learning from information security incidents
5.28 Collection of evidence

ISO 27002:2022 · 2 controls

5.27 Learning from information security incidents
5.28 Collection of evidence

NIST SP 800-171 Rev 3 · 2 controls

03.06.01 Incident Handling
03.14.08 Information Management and Retention

NIST SP 800-218 · 2 controls

SP800-218-RV.3.1 Analyze Vulnerabilities to Identify Root Causes
SP800-218-RV.3.4 Document Lessons Learned

NIST SP 800-53 Rev 5 · 2 controls

NIST800-AU-11 AU-11 Audit Record Retention
NIST800-IR-8 IR-8 Incident Response Plan

PCI DSS 4.0 · 2 controls

12.10.2 12.10.2 Annual review and testing of the incident response plan
12.10.6 12.10.6 Plan evolved from lessons learned and industry developments

APRA CPS 230 Operational Risk Management · 1 control

CPS230-27 Identification and Escalation of Incidents and Near Misses

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-STEP5 Step 5 - Manage and report security incidents

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-21 Remediation of Vulnerabilities and Deficiencies

CMMC 2.0 · 1 control

IR.L2-3.6.1 Incident Handling

ISO 22301:2019 · 1 control

10.1 Nonconformity and corrective action

ISO 27701:2019 · 1 control

6.13.1 Management of information security incidents and improvements

NIST SP 800-161 Rev 1 · 1 control

161R1-AU-10 Non-repudiation

NIST SP 800-172 · 1 control

3.11.5e Assess Effectiveness of Security Solutions

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

SOC 2 · 1 control

SOC2-CC7.5 CC7.5 Recovering from security incidents

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 Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-IR-7 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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