ISO 27001:2022 A.5.25: Assessment and decision on information security events
Assessment and decision on information security events is asked by 17 of the 48 carrier applications, through 23 questions. The evidence to have on file is The agreed incident categorization and prioritization scheme with criteria for declaring an incident and consequence levels. 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.25?
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.25, showing inclusion or justified exclusion, implementation status and the risks it treats
- The agreed incident categorization and prioritization scheme with criteria for declaring an incident and consequence levels
- Triage records showing each reported event assessed against the scheme
- Detailed decision records identifying who assessed the event, the categorization and the rationale
- Evidence that assessors are the designated incident coordination and response personnel
Common gaps an assessor names
- No written criteria for when an event becomes an incident, so decisions are inconsistent
- Events closed as non-incidents without any recorded rationale
- Triage is done by whoever receives the alert rather than designated personnel
- Priority is set by gut feel rather than a consequence-based scheme
The one or two items a carrier would actually ask for
- The agreed incident categorization and prioritization scheme with criteria for declaring an incident and consequence levels
- Triage records showing each reported event assessed against the scheme
The application questions that reach A.5.25 (23)
Application question Do you have an incident response plan for network intrusions and malware incidents?
Application question Do you have a written incident response plan in the event that Personally Identifiable Information is/may be compromised?
Application question Does the insured implement any of the following response plans?
Application question Does the Applicant have a written incident response plan?
Application question Does the firm have a documented Incident Response Plan?
Application question If "Yes", have any table top exercises for the Incident Response Plan been conducted in the last 24 months?
Application question Do you have an information security incident response plan?
Application question Do you have an incident response or digital forensic outsourcing retainer agreement in place?
Application question A document incident response plan is in place.
Application question There is an incident response plan documented with specific focus on Cyber incident management.
Application question There is an endpoint threat detection and response (ETDR or EDR) tool in place, which does the following: monitors for threat indicators; identifies patterns which match known threats; automatically responds by removing or containing threats; alerts security personnel of incidents; provides forensic and analysis capabilities to allow analysts to perform threat hunting activities.
Application question Does the Applicant currently have an incident response plan in place?
Application question Does the Applicant have an incident response plan dealing with network unauthorized access or computer viruses?
Application question Do you have a written procedure that you rehearse at least yearly to ensure that you are proficient in responding to and recovering from network disruptions, intrusions, data loss and breaches of network attacks & incidents (including malicious code, hacking, spy-ware)?
Application question Do you have a written procedure that you rehearse at least yearly to ensure that you are proficient in responding to and recovering from privacy/confidentiality breaches?
Application question Have you had any incidents, unplanned business interruption, claims or suits involving unauthorized access or misuse of your network, including embezzlement, fraud, theft of proprietary information, breach of personal information, theft or loss of laptops, denial of service, electronic vandalism or sabotage, computer virus, cyber extortion attempt or demand or other incident?
Application question Do you have an incident response plan or other processes for responding to a cyber security incident?
Application question Do you have an incident response plan (for cyber attacks and data breaches) that identifies an incident response team?
Application question Does the Applicant have an incident response plan for data breaches, network intrusions and virus incidents?
Application question Does the applicant have a written data breach response plan in place?
Application question Does the Applicant have a data breach response plan in place in the event of a security breach or system failure?
Application question Does the Applicant have a written incident management response plan?
Application question Does the Proposer have an incident response plan for network intrusions and virus incidents?
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.24 (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.