HomeBlogCybersecurity

Cyber Insurance Evidence Workbook: Proof for Every Answer

Voxel robot filing glowing cubes into a cabinet beside a shield and umbrella, illustrating a cyber insurance evidence file

Download the Cyber Insurance Evidence Workbook (Excel, .xlsx). A shorter one-sheet evidence list (CSV) carries the same thirteen rows for a quick start.

The workbook is a record-keeping aid. It is not insurance advice or legal advice, it does not quote any insurer's form, and it does not say what any insurer requires. Your own application and your broker decide what you are asked. The public sources behind the control list are at the end of this page and were checked on November 22, 2026.

What is in the workbook?

TabWhat it holdsWhen you use it
Evidence registerOne row per control area: what the application usually asks, the evidence that answers it, where to pull it, owner, date collected, file location, gap and remediationFrom 90 days before renewal, and again whenever a control changes
Renewal timelineTasks at 120, 90, 60 and 30 days before renewal, with target dates worked out from the renewal date you enterFrom the day the renewal date is known
Answer logEach question as your application words it, the answer given, the evidence file, who prepared it and who approved it, with last year's answer beside itWhile drafting answers, and at next year's renewal
GapsEach missing or partial control with a decision, a remediation step, an owner and a due dateAs soon as the register shows a Partly or a No
SummaryCounts from the other tabs: evidence in hand, answers approved, gaps still open, days to renewalBefore each review with the signer or the broker

Which controls does the evidence register cover?

Thirteen control areas that applications commonly ask about. Each maps to an item in a broker's published list, 12 Security Controls Recommended by Cyber Insurers from Marsh McLennan Agency with Arete Advisors, and the workbook also cites the matching outcome in the NIST Cybersecurity Framework 2.0 where there is one. The wording below is ours. Applications differ, so reword each row to match yours.

Control areaWhat the application usually asksEvidence that answers itWhere to pull it
MFA: emailIs MFA enforced for everyone who reaches company email, and are any accounts exempt?Policy export, list of registered users, list of excluded accounts with reasonsIdentity provider policy page and MFA registration report
MFA: remote accessDoes every remote connection require MFA, and is remote desktop reachable from the internet?Screenshot of VPN or gateway sign-in settings, list of remote access methods, firewall rule exportFirewall or VPN admin console
MFA: administrator accountsIs MFA required for every administrator account, including backup, firewall and remote management consoles?Role assignment export, policy export for admin roles, screenshot from each separate consoleIdentity provider role list and each console's security settings
EDR on workstations and serversDoes an EDR tool run on all workstations and servers, and who responds to its alerts?Device list export compared with the asset inventory, devices without the agent, monitoring agreement or on-call scheduleEDR console device list and the asset inventory
Backups: offline or immutable copyAre critical systems backed up, is one copy offline or immutable, and is backup access separate from everyday admin credentials?Backup job report, screenshot of the immutability setting, list of protected systemsBackup console job history and repository settings
Backups: tested restoresAre restores tested, how often, and when was the last one?Dated restore test record: what was restored, from which copy, time against target, who verified itRestore drill run sheets and sign-off
Patching cadenceHow quickly are critical updates applied, and how is patch status tracked?Patch policy with timeframes, compliance report by device, firmware versions for internet-facing devicesRemote management or device management console
Privileged accessAre admin accounts separate, how many people hold them, and how fast do leavers lose access?Admin account list with owners, last access review, offboarding recordsRole assignment download, privileged group export, HR leaver list
Email filteringIs inbound mail filtered for phishing, links and attachments, and are SPF, DKIM and DMARC set up?Policy screenshots, a filtering summary report, the published DNS recordsEmail security console and a public DNS lookup
Security awareness trainingDo all staff get training, how often, and is completion tracked?Completion report by person and date, phishing simulation results, onboarding stepTraining platform export
Incident response planIs there a written plan, who owns it, and has it been tested?Plan with owner and revision date, contact sheet, record of the last tabletop exerciseDocument library and the tabletop report
Vendor managementWhich providers hold your data or reach your systems, and is their security reviewed?Vendor list with access and criticality, questionnaires or assurance reports, proof of MFA on vendor accessVendor risk register and contracts
End-of-life systemsDo any systems no longer receive security updates, and how are they being replaced or isolated?Inventory with versions and support end dates, list of unsupported systems with a planAsset inventory and vendor lifecycle pages

The workbook's own rows are longer and name the report. For Microsoft 365, Microsoft's documentation places MFA registration under Entra ID, Authentication methods, Activity, the effect of each policy under Conditional Access, Insights and reporting (which needs a Log Analytics workspace), individual sign-ins under Monitoring & health, Sign-in logs, and a CSV of every admin role holder under Roles & admins, Download assignments. For Google Workspace, Google's admin help puts 2-Step Verification enrollment and enforcement under Reporting, User Reports, Security. All were checked on November 22, 2026, and vendors move these pages.

Two rows lean on records from other NetSys templates. The restore testing row is answered by the run sheets in our restore test checklist and Quarterly Restore Drill Kit, and the vendor row by the vendor security questionnaire and risk register.

When should you start collecting evidence before a renewal?

Enter the renewal date once and the timeline tab works out each target date. The four marks are a working schedule from NetSys, not a rule from any insurer. Move a task earlier when a control needs calendar time to produce a record, such as a training round or a restore drill.

Days before renewalWhat happensWhat you have at the end
120Ask the broker for this year's application, pull last year's answers, name an owner for every register row, and start anything that needs calendar timeThe application, last year's log and a named owner for each control area
90Collect fresh evidence for each row, list every gap and choose a decision for it, and tell the broker what has changed since last yearA dated evidence file for each control area and a gap list with owners
60Draft each answer in the application's own wording with its evidence file beside it, and collect evidence again for anything that was fixedA draft answer log and fewer open gaps
30The authorized signer reviews each answer against its evidence, exceptions are recorded, and the application goes in through the brokerA signed application and an evidence pack filed in a restricted folder

How does the answer log keep next year's answers consistent?

A year after signing, few people remember which accounts were exempt from MFA or which server had not been restored yet. The answer log records, for each question, the wording on the application, the answer given, any scope or exception disclosed, the evidence file, who prepared the answer and who approved it. At the next renewal you copy those answers into the Last year's answer column of a new log, and the sheet marks each answer Same or Changed. A changed answer then gets a written reason, whether a control improved or one slipped.

What goes on the gaps tab?

Every control marked Partly or No in the register. Each gap gets one of three decisions before anyone signs:

  • Fix before signing. The control is put in place and evidenced before the answer is given.
  • Disclose as an exception. The answer names the accounts, devices or sites left out, in the form your broker asks for.
  • Answer no. The control is not in place and the application says so.

The tab also flags any fix whose due date falls after the 30-day review, so nobody is asked to sign on the strength of work that is not finished. Wording an answer around a gap is not one of the choices.

What does the workbook not do?

It does not decide coverage, predict a premium, interpret policy wording or replace your insurer's application. It is not insurance advice or legal advice, and NetSys is an IT provider, not an insurer or a broker. Questions about application wording and coverage go to your broker or insurer, legal questions go to your attorney, and the person who signs the application is responsible for its answers. Keep the workbook in a restricted folder: it lists your open gaps and your admin accounts.

Frequently asked questions

Does the workbook list what cyber insurers require?

No. It lists control areas that applications commonly ask about, drawn from public broker, insurer, regulator and framework guidance. Each insurer writes its own application, so match the rows to the questions in front of you and delete the ones yours does not ask.

How far ahead of a renewal should we start?

The timeline starts 120 days out with the application, last year's answers and owners, and evidence collection starts at 90 days. Later starts still work if the controls are already in place, because most of the time goes on fixes and on records that take weeks to build.

Who should fill in the workbook?

Whoever runs the systems, usually an IT lead or your IT provider, fills in the evidence register. The person who signs the application, often an owner or controller, reviews the answer log and approves each answer against its evidence.

How is this different from the evidence checklist in the self-assessment?

The cyber insurance evidence checklist is a seven-control check you answer in the browser in a few minutes. The workbook is where the records live afterward: thirteen control areas, file locations, dates, approvals and gaps.

What counts as evidence for an application answer?

A dated record from the system itself: an export, a report, a screenshot showing the setting and the date, a signed plan or a test record. A statement that a control exists is not evidence. If a record covers only part of the scope, file it and write down the exception.

Is the workbook insurance or legal advice?

No. It is a way to organize your own records. It does not tell you whether an insurer will offer or renew a policy, what it will cost or what it covers. Your broker, your insurer and your attorney answer those questions.

Sources

All checked on November 22, 2026.

Have an engineer check the answers before you sign

Our cyber insurance readiness assessment does this work with you: an engineer checks each application answer against what is deployed, closes the gaps you approve and builds the evidence pack. Send us the application and the renewal date, and ask for a renewal readiness review.

Cyber Insurance Readiness

Discuss cyber insurance readiness for your business.

Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.

Explore Cyber Insurance Readiness 845-203-3914