Cyber insurance renewal checklist for brokers
When a carrier cyber application lands just before renewal season, a broker works through the same set of questions across several carriers, each with its own form. This checklist is that work on one page: the client, the carrier and the form edition, the policy expiry, the as-at reference date and the days to renewal (counted from that date), the carrier question, the control it tests, the evidence to have on file, the owner, the status, any exception and the date it was reviewed.
It is for a cyber broker or account handler placing or renewing cover across more than one carrier, and secondarily for the risk manager answering the form. The questions, the controls and the evidence come from the same carrier documents the scanner reads, so what is on the checklist is what the tool returns. The client and owner fields are a worked example, plainly labelled, and name no real client.
Download insurance-renewal-checklist.csv (13 columns, a worked example of 20 rows; the as-at date is the reference date the days to renewal are counted from).
The checklist, as the file reads
| client | carrier | form_edition | policy_expiry | as_at_date | days_to_renewal | question | control_tested | evidence_to_have_on_file | owner | status | exception | reviewed_date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Acme Managed Services (example) | Coalition | Coalition cyber application, undated summary | 15 Dec | 11 Nov | 34 | Does Named Insured have procedures to back up, archive, and restore sensitive data and critical business systems? | ISO 27001:2022 A.8.13 Information backup | the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill; the rule on backup retention and how copies are kept | IT Operations Manager | Evidence held | 12 Oct | |
| Acme Managed Services (example) | Coalition | Coalition cyber application, undated summary | 15 Dec | 11 Nov | 34 | Does Named Insured require dual control when transferring funds in excess of $25,000? | ISO 27001:2022 A.5.3 Segregation of duties | the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold; the payment approval log, with a dated example above the threshold; the callback or out-of-band verification for a change to payee bank details, with a dated example | Finance Controller | Evidence held | 12 Oct | |
| Acme Managed Services (example) | Chubb | Chubb cyber short form, undated | 30 Nov | 11 Nov | 19 | Does the Applicant verify all vendor and supplier bank accounts by a direct call to the receiving bank, prior to accounts being established in the accounts payable system? | ISO 27001:2022 A.5.3 Segregation of duties | the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change; a dated record of the verification for the specific change, with the person who checked and the source used | Risk and Compliance Lead | Awaiting the dated example | The callback log for the last supplier change is being pulled. | 10 Oct |
| Acme Managed Services (example) | CFC Underwriting | CFC Underwriting proposal form, undated | 31 Jan | 11 Nov | 81 | How often do you conduct vulnerability scanning of your network perimeter? | ISO 27001:2022 A.8.8 Management of technical vulnerabilities | the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised; the remediation or exception record for each finding, with the date it was closed | Risk and Compliance Lead | Evidence held | 11 Oct | |
| Acme Managed Services (example) | Hiscox | Hiscox cyber application, undated | 28 Feb | 11 Nov | 109 | Multi-factor authentication in place for remote access by employees? | ISO 27001:2022 A.8.5 Secure authentication | the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group; the written rule stating where the second factor is required and where it is not | Head of Security | Evidence held | 12 Oct | |
| Acme Managed Services (example) | Hiscox | Hiscox cyber application, undated | 28 Feb | 11 Nov | 109 | If you have a back-up of all of your critical data and systems, does that include an offline copy? | ISO 27001:2022 A.8.13 Information backup | the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline; the rule on how often the offline copy is made and how it is kept separate from production | IT Operations Manager | Exception logged | The offline copy is a rotating disk held off site, and its rotation schedule is on file. | 11 Oct |
| Acme Managed Services (example) | Hiscox | Hiscox cyber application, undated | 28 Feb | 11 Nov | 109 | Do you have procedures in place to vet the security and privacy controls of your vendors and outsourcers? | ISO 27001:2022 A.5.19 Information security in supplier relationships | the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review; the rule on which suppliers need a security assessment and how often | Risk and Compliance Lead | In progress | Two new suppliers are still being assessed. | 9 Oct |
| Acme Managed Services (example) | Great American Insurance Group | Great American cyber application, revision 11/23 | 30 Nov | 11 Nov | 19 | Is multifactor authentication (MFA) required to remotely connect to the network, all critical internet facing systems and privilege accounts? | ISO 27001:2022 A.8.5 Secure authentication | the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group; the written rule stating where the second factor is required and where it is not | Head of Security | Evidence held | 12 Oct | |
| Acme Managed Services (example) | Great American Insurance Group | Great American cyber application, revision 11/23 | 15 Dec | 11 Nov | 34 | Are back-up restoration plans tested? | ISO 27001:2022 A.8.13 Information backup | the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill; the rule on backup retention and how copies are kept | IT Operations Manager | Evidence held | 12 Oct | |
| Acme Managed Services (example) | Great American Insurance Group | Great American cyber application, revision 11/23 | 15 Dec | 11 Nov | 34 | Are Sender Policy Framework (SPF), Domain-based Message Authentication Reporting and Compliance (DMARC) or Domain Keys Identified Mail (DKIM) in place? | ISO 27001:2022 A.8.23 Web filtering | the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling; the rule on external-message tagging and user reporting | Security Operations Lead | Evidence held | 10 Oct | |
| Acme Managed Services (example) | Tokio Marine HCC | Tokio Marine HCC cyber application, revision 10.20 | 31 Jan | 11 Nov | 81 | Do you use Endpoint Detection and Response (EDR) or a Next-Generation Antivirus (NGAV) software (e.g., CrowdStrike, Cylance, Carbon Black) to secure all system endpoints? | ISO 27001:2022 A.8.7 Protection against malware | the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling; the anti-malware or EDR policy, including any exclusions | IT Operations Manager | Evidence held | 11 Oct | |
| Acme Managed Services (example) | Tokio Marine HCC | Tokio Marine HCC cyber application, revision 10.20 | 31 Jan | 11 Nov | 81 | If "Yes": (1) Do you use 2-factor authentication to secure all remote access to your network? | ISO 27001:2022 A.8.5 Secure authentication | the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group; the written rule stating where the second factor is required and where it is not | Head of Security | Evidence held | 12 Oct | |
| Acme Managed Services (example) | AmTrust | AmTrust cyber application, undated | 30 Nov | 11 Nov | 19 | Does the Applicant encrypt data stored on laptop computers and portable media? | ISO 27001:2022 A.8.24 Use of cryptography | the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed; the exception report for any endpoint not yet encrypted, with the date it was raised | Head of Infrastructure | Evidence held | 10 Oct | |
| Acme Managed Services (example) | Munich Re | Munich Re cyber application, undated | 15 Dec | 11 Nov | 34 | Is multi-factor authentication (MFA) in place for web-based email logins? | ISO 27001:2022 A.8.5 Secure authentication | the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group; the written rule stating where the second factor is required and where it is not | Head of Security | Evidence held | 12 Oct | |
| Acme Managed Services (example) | CNA | CNA cyber self-assessment, publisher form | 15 Dec | 11 Nov | 34 | Do you require multi-factor authorization when your network is accessed remotely and/or when cloud resources are utilized? | ISO 27001:2022 A.8.5 Secure authentication | the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group; the written rule stating where the second factor is required and where it is not | Head of Security | Evidence held | 11 Oct | |
| Acme Managed Services (example) | Everest Insurance | Everest Insurance cyber application, undated | 31 Jan | 11 Nov | 81 | Does the Applicant use multi-factor authentication for access to critical applications or databases (including those that contain personally identifiable information, private health information or payment card information? | ISO 27001:2022 A.8.5 Secure authentication | the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group; the written rule stating where the second factor is required and where it is not | Head of Security | Exception logged | A legacy reporting database does not support single sign-on; it sits on an isolated segment. | 11 Oct |
| Acme Managed Services (example) | Beazley | Beazley cyber application, form number only | 28 Feb | 11 Nov | 109 | When a vendor or supplier requests any change to its account details (including routing numbers and account numbers), do you confirm requested changes via an out-of-band authentication (a method other than the original means of request? | ISO 27001:2022 A.5.3 Segregation of duties | the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change; a dated record of the verification for the specific change, with the person who checked and the source used | Risk and Compliance Lead | Evidence held | 12 Oct | |
| Acme Managed Services (example) | DUAL Corporate Risks | DUAL Corporate Risks proposal form, ref 4965 | 30 Nov | 11 Nov | 19 | Permit remote access to its corporate network? | ISO 27001:2022 A.6.7 Remote working | the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely; the written rule stating how remote access is granted, logged and restricted | Head of Security | Evidence held | 12 Oct | |
| Acme Managed Services (example) | Arch Insurance | Arch NetSafe 2.0 short form, form 00 NPL0154 | 28 Feb | 11 Nov | 109 | Do you ensure that all private information is encrypted at rest? In transit? | ISO 27001:2022 A.8.24 Use of cryptography | the disk-encryption configuration record, naming the algorithm and key length in use; the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered | Head of Infrastructure | Evidence held | 11 Oct | |
| Acme Managed Services (example) | Hiscox | Hiscox cyber application, undated | 15 Dec | 11 Nov | 34 | Do you have a written incident response plan in the event that Personally Identifiable Information is/may be compromised? | ISO 27001:2022 A.5.24 Information security incident management planning and preparation | the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date; the forensic retainer, or the named handler for a confirmed incident | Risk and Compliance Lead | Evidence held | 12 Oct |
Map a carrier application for free on the scanner. Two held applications to try it on: Coalition and Hiscox. The two worked answers: the funds-transfer verification question and what counts as MFA on an application. See what a saved submission keeps on the example of a saved submission.
Frequently asked
How many carrier questions does the checklist cover?
Twenty rows across ten carriers, each row the carrier question, the control it tests and the evidence to have on file. The CSV download carries the same rows.
What is the as-at date for?
It is the reference date the days-to-renewal figures are counted from, so the gap is calculable from the file alone. The expiries are the worked example.
Is the client a real one?
No. The client and owner fields are a worked example, plainly labelled, and name no real client.