Cybersecurity
October 26, 2026
9 min read

Cyber Insurance Renewal: Technical Evidence Checklist

Prepare for cyber insurance renewal with answers your business can support. Gather dated technical evidence, identify gaps, assign owners, and bring clear questions to your broker.

Illustration of a technical evidence folder, checklist, magnifying glass and red security shield.

Before you sign a cyber insurance renewal application, you need to know whether its answers match the systems your business actually uses.

Get the exact renewal application before gathering evidence. Map each question to dated, scoped proof from the responsible owner. Record exceptions, planned remediation, and unresolved wording instead of guessing or treating a planned control as already implemented.

Applications vary by insurer, policy, industry, year, and applicant. This checklist is an internal evidence-preparation tool, not insurance, legal, compliance, underwriting, or coverage advice. Your authorized leadership, broker, insurer, and qualified advisers remain responsible for interpreting and answering the actual form.

Free for OC Businesses

Get a Free IT Assessment for Your OC Business

Not sure what your next move should be? C3 Tech offers a complimentary assessment for Orange County businesses with practical recommendations and no commitment required.

Schedule Free Assessment

Why this work matters before renewal

The person signing the renewal needs answers the business can support, not just reassurance that IT has things covered. For example, At-Bay’s June 2026 application asks an authorized representative to declare, after reasonable inquiry, that its statements are true and complete. That is a requirement of that form, not a universal statement about every policy.

Preparing the evidence early helps you:

  • Know what you can answer. Separate confirmed controls from missing information and exceptions before the form is signed.
  • Decide what needs attention. Give leadership a clear list of gaps, owners, and proposed work instead of an unexplained technical report.
  • Ask your broker specific questions. Bring the exact wording and known facts when an answer is unclear, rather than relying on assumptions.

The result is a clearer renewal-preparation process and a more useful picture of your current security controls. Completing this checklist does not guarantee renewal, coverage, or a lower premium.

Start with the exact application, not a generic checklist

Current and historical applications ask different questions. For example, the At-Bay Cyber Renewal Application edition dated June 2026 asks about specific identity, remote-access, backup, email, endpoint, provider, and business-change details. Other sampled applications use different terms, control categories, sectors, and dates.

Examples of insurer applications and their limits
Example source Questions observed Applicability boundary
At-Bay Cyber Renewal Application, ed. 06/2026 Multifactor authentication (MFA), remote access, managed service provider (MSP) use, backup design, email controls, endpoint detection and response (EDR), and known changes 2026 application-specific example; not a universal insurer requirement
AXIS Cyber Technology & MPL Renewal Application, 06/2023 MFA, EDR, patching, testing, inventory, monitoring, backups, business-continuity and incident-response testing Mixed Cyber Technology & MPL renewal application; example only
NYMIR Municipal Cyber Renewal Application, v. 2025-06-24 Control changes, backups, restore testing, MFA, email, funds verification, training, and incidents New York municipal example only
Tokio Marine HCC NetGuard Plus Renewal Application, 07/2020 Sensitive records, cloud access, EDR, backup segregation, expected recovery, funds controls, and incidents Older application-specific example, not a current market rule

Do not write “cyber insurers require” when the evidence comes from one named form. Ask the broker or insurer how to handle wording that is unclear, conditional, or outside your authority.

Build one question-by-question evidence register

Use one register to connect the submitted answer to its scope and source. If your Orange County business has multiple offices or remote staff, reconcile their accounts, devices, and access paths to the same inventory date. Evidence from the main office alone should not stand in for the full application scope.

Record these fields for every question:

  1. Exact application question
  2. Application or supplement name and version
  3. Business owner
  4. Technical evidence owner
  5. Evidence source or file
  6. Evidence date
  7. Scope and denominator
  8. Current status
  9. Exceptions and compensating controls
  10. Remediation owner and target date
  11. Proposed application answer
  12. Reviewer and review date

For each coverage answer, record the numerator and denominator from the same inventory date. Examples include accounts with enforced MFA divided by all in-scope accounts, or healthy monitored devices divided by all in-scope endpoints. Name excluded users, service accounts, devices, sites, tenants, and other categories rather than removing them silently. If the counts come from different dates or inventories, mark the answer needs confirmation.

Use a controlled status instead of a vague yes or no:

  • Verified current: Evidence supports the answer for the stated scope and date.
  • Verified with exception: Evidence generally supports the answer, but named systems, users, sites, accounts, or conditions are excluded.
  • Needs confirmation: Evidence is missing, conflicting, stale, or the question is unclear.
  • Not applicable: The triggering technology or activity is absent, and the reason is documented.
  • Planned, not in force: Work is approved or underway but should not be represented as currently implemented.

Some forms may offer “unknown” for selected questions. Use needs confirmation internally, then get direction on how the actual form should be answered.

Confirm business and application scope

Owners: Executive sponsor, finance, HR, privacy or legal, and IT.

Gather:

  • legal entities, subsidiaries, locations, domains, websites, and email domains;
  • current employee and contractor counts;
  • revenue figures from the authorized financial owner;
  • mergers, acquisitions, new products, services, and major cloud changes;
  • sensitive-data types and the method used to estimate record counts;
  • the current application and every supplement; and
  • the previously submitted application for comparison.

Mark needs confirmation when entity lists differ, a new location or domain is absent, record counts lack a defensible method, or IT is being asked to certify financial or legal facts.

Verify MFA and identity coverage

Owners: Identity administrator, application owners, and any responsible provider.

Gather:

  • identity-provider policy export showing enforcement;
  • coverage evidence for email, VPN, remote access, cloud administration, and privileged accounts;
  • user and administrative-account inventory used as the denominator;
  • enrollment and enforcement evidence as separate facts;
  • break-glass, service, legacy, and other excluded accounts;
  • recent access-review record; and
  • remediation tickets for uncovered accounts or applications.

Enrollment does not prove enforcement. “All users” is not supportable until the covered count reconciles to the current directory and exceptions.

Inventory remote access and internet-facing systems

Owners: Network administrator, security owner, and any responsible provider.

Gather:

  • VPN, zero-trust access, firewall, remote monitoring, and remote-desktop inventory;
  • vendor, model, version, hosting location, and support status;
  • MFA policy tied to each access path;
  • current external-exposure scan or firewall-rule review;
  • exposed administrative services and approved exceptions; and
  • patching and configuration evidence for perimeter appliances.

Mark a gap when a management service is publicly reachable without a documented decision, a VPN device is missing from inventory, or different offices use undocumented access methods.

Reconcile EDR and monitoring to the device inventory

Owners: Security team or monitoring provider.

Gather:

  • console export showing active, healthy, inactive, and excluded devices;
  • reconciliation against the current endpoint and server inventory;
  • agent version and policy assignment;
  • monitoring hours and named alert owner;
  • agreement or statement of work assigning monitoring and response duties;
  • a recent alert or ticket showing the escalation path; and
  • exceptions for unsupported or intermittently connected devices.

“Installed” is not the same as active, healthy, and monitored. A provider agreement can establish assigned scope, but it does not by itself prove that the agent or policy is operating on every device.

Separate backup jobs from recovery evidence

Owners: Backup administrator, application owners, and business-continuity owner.

Gather:

  • protected-system and protected-data inventory;
  • backup schedule, retention, storage location, and vendor;
  • recent job-history report;
  • offline, segregated, or immutable configuration evidence when the application asks;
  • backup-console MFA and privileged-access evidence;
  • encryption configuration when requested;
  • most recent restore-test record, including system, recovery point, date, result, actual duration, exceptions, and remediation; and
  • approved recovery targets or expected recovery time when the form asks.

Successful backup jobs do not prove recoverability. A test of one system does not support an answer covering every critical system. Do not call storage immutable or offline without configuration and scope evidence.

Document email, payment, and human controls

Owners: Email administrator, finance, HR, and training owner.

Gather:

  • email-protection configuration;
  • SPF, DKIM, and DMARC records for every sending domain;
  • enabled attachment, link, impersonation, and sandboxing policies;
  • training completion records and phishing-test results when testing is performed;
  • written payment-change and electronic-funds verification procedure; and
  • evidence that relevant finance personnel received the procedure and training.

A written policy does not prove that the control is enabled or consistently followed. Preserve domain-by-domain and team-by-team exceptions.

Gather vulnerability, patch, and configuration evidence

Owners: IT operations, security, and any responsible provider.

Gather:

  • current internal and external vulnerability reports with scan scope;
  • asset inventory used to calculate coverage;
  • patch-compliance reports for workstations, servers, and network appliances;
  • remediation tickets for important findings;
  • unsupported-system inventory and retirement plan;
  • documented exceptions, risk owner, compensating controls, and target date; and
  • penetration-test summary only when a relevant test actually occurred.

A clean scan does not establish security beyond its date, assets, credentials, scanner, and test method. A missed office, tenant, cloud environment, or device changes the denominator.

Review privileged and third-party access

Owners: IT, procurement or vendor owner, and any responsible provider.

Gather:

  • privileged-account and group-membership inventory;
  • evidence of separate administrative accounts;
  • MFA and access-review evidence for administrators;
  • vendor and provider account inventory;
  • named versus shared account status;
  • least-privilege, expiration, and offboarding records; and
  • current agreement or statement of work assigning control and monitoring responsibilities.

A contract or vendor security sheet may document responsibility or claimed scope. It does not prove that the technical control is enabled in your environment.

Prepare training, incident-planning, and exercise records

Owners: HR, security, executive sponsor, and communications.

Gather:

  • training roster, assignment dates, completion results, and exceptions;
  • current incident-response plan with approval and review date;
  • named roles and current contacts;
  • an approved offline-accessible copy of the plan;
  • tabletop or exercise record with participants, findings, owners, and open actions; and
  • evidence that relevant vendors are included in planning.

This is readiness evidence. The actual containment, notification, and first-hour response sequence belongs in a separate incident plan and companion article.

Reconcile events, changes, and remediation history

Owners: Risk or legal, executive sponsor, IT, privacy, and broker.

Gather:

  • incident, outage, demand, complaint, and regulatory-event register;
  • dates, affected systems, known factual scope, and current status;
  • completed investigation or root-cause records when available;
  • corrective actions and closure evidence;
  • control changes since the prior application; and
  • unresolved facts escalated to authorized decision-makers.

IT can provide technical facts. It should not independently decide whether an event is a claim, reportable circumstance, covered loss, or policy issue. Those determinations belong with authorized leadership, the broker, insurer, and qualified counsel as appropriate.

Finish with a controlled submission record

Before submission:

  • reconcile every answer to evidence or a documented clarification;
  • keep planned remediation separate from current state;
  • resolve conflicting exports, screenshots, contracts, and verbal statements;
  • have the authorized representative complete the inquiry required by the actual form;
  • save the submitted application, supplements, attachments, and submission date;
  • recheck for material changes when the form requires it; and
  • send sensitive evidence only through an approved channel.

Do not include credentials, recovery keys, unnecessary personal data, or broad administrative exports when a narrower proof will answer the question.

Use control frameworks as support, not underwriting rules

NIST Cybersecurity Framework 2.0 is a voluntary, cross-sector risk-management framework. It is not one-size-fits-all and is not an insurer application. It can help organize inventories, roles, supplier responsibilities, exceptions, vulnerability management, access control, monitoring, tested backups, and response plans.

The CISA StopRansomware Guide provides federal ransomware-preparation and response guidance. It supports measures such as offline encrypted backups and testing, incident-plan exercises, MFA, endpoint detection, vulnerability scanning, asset inventories, remote-access hardening, and provider oversight. It is not a policy, coverage interpretation, or underwriting guarantee.

Tie every application answer to the actual wording, evidence, scope, and date.

Inventory the technology before renewal

C3 Tech’s managed IT team can help an Orange County business inventory its current technology, backups, cybersecurity basics, assigned support responsibilities, and known gaps before renewal. The business, broker, insurer, and qualified advisers remain responsible for interpreting and answering the application.

Start the conversation with C3’s Santa Ana team.

C3 Tech Team
C3 Tech Team
IT Services Specialist, C3 Tech

C3 Tech has served Orange County businesses since 1994 with managed IT, cybersecurity, copier, and managed print support. Our team writes practical guidance from real service experience with small and mid-sized local organizations.

Get a free 30-minute
consultation.

Start with the issue you want fixed first. We’ll come back within one business day with a plain-English answer, no hard sell, no contract pressure.



What can we help with?






Or call (714) 689-1700 Mon-Fri 8a-5p PT

4-hour response
Local OC team
30 years in business
Women-owned