ISO 27001:2022 A.5.24: Information security incident management planning and preparation
Information security incident management planning and preparation is asked by 17 of the 48 carrier applications, through 23 questions. The evidence to have on file is An approved incident management plan and procedures covering evaluation, detection, classification, escalation, recovery, communication, evidence handling and post-incident review. This page maps the control to the questions that reach it; it never says whether an applicant will be offered cover.
ISO 27001:2022 is read as the publisher's combined inventory: 93 Annex A controls plus 30 management-system clauses. Every requirement here is our statement of its clause, cited to it, not the instrument verbatim.
Which carriers ask this control?
17 carrier applications reach this control: AIG, Aspen American Insurance Company, AXIS Insurance, Beazley, BOXX Insurance, The Cincinnati Insurance Company, Delta Insurance, Discovery Insure Ltd, Everest Insurance, Great American Insurance Group, Hiscox, The Hartford Steam Boiler Inspection and Insurance Company, Liberty Mutual Insurance Europe Limited, Markel, Munich Re, Trisura Guarantee Insurance Company, USLI. A carrier named here is a source document, never a customer or an endorsement.
What evidence should be on file for A.5.24?
Evidence guidance is our wording, not a statement of any standard and not binding on a carrier or an assessor.
- Statement of Applicability entry for control A.5.24, showing inclusion or justified exclusion, implementation status and the risks it treats
- An approved incident management plan and procedures covering evaluation, detection, classification, escalation, recovery, communication, evidence handling and post-incident review
- Incident management objectives and priorities agreed with management, including resolution time frames by severity
- A roles and responsibilities document for the incident team and its communication to internal and external parties
- Training, certification and exercise records for incident responders
Common gaps an assessor names
- The plan exists but has never been exercised against realistic scenarios
- Regulatory notification deadlines are not built into the procedures
- People reporting events never hear the outcome, discouraging future reporting
- Responders lack training or the procedures they are expected to follow
The one or two items a carrier would actually ask for
- An approved incident management plan and procedures covering evaluation, detection, classification, escalation, recovery, communication, evidence handling and post-incident review
- Incident management objectives and priorities agreed with management, including resolution time frames by severity
The application questions that reach A.5.24 (23)
Controls reached by the same questions
12.2 (CIS Controls v8), 12.4 (CIS Controls v8), 12.5 (CIS Controls v8), 8.11 (CIS Controls v8), 8.2 (CIS Controls v8), 8.9 (CIS Controls v8), A.5.25 (ISO 27001:2022), A.5.26 (ISO 27001:2022), CC7.3 (SOC 2), CC7.4 (SOC 2), RS.CO-02 (NIST CSF 2.0), RS.MA-01 (NIST CSF 2.0), Requirement 1 (PCI DSS 4.0), Requirement 10 (PCI DSS 4.0).
This control on the island, all controls on the controls index, the framework on the ISO 27001:2022 page, the carriers on sources. Map your own answers in the tool.