Cyber Insurance Guides

Practical guide · November 17, 2026

Who should complete a cyber insurance application?

Treat the application as a coordinated job: the business supplies business facts, IT or the MSP supplies scoped technical facts, and the agent helps route insurance questions and ambiguities. Then check the actual form's signing instructions. Helping assemble an answer is not the same as being authorized to sign it.

Give each participant a defined job

The following is a suggested working arrangement, not a statement of legal duties or a rule that every insurer follows.

Proposed application roles and responsibility boundaries
Participant Proposed contribution Boundary to preserve
Business owner or designated business lead Business description, relevant financial information, systems used outside IT and coordination Do not assume IT knows every business activity or purchase
IT lead or MSP Current controls, affected systems, verification dates and exceptions Describe the environment; do not decide insurance coverage from a technical setting
Insurance agent or broker Explain requested documents and obtain insurer clarification where needed Keep the clarification attached to the precise question and form version
Signer authorized under the form Read the representations and review the completed answers Determine authorization from the actual instructions and appropriate advice, not a generic job-title rule

For a concrete, carrier-specific example, the Travelers MFA supplement, CYB-14306 Rev. 03-23 expressly connects the signer with assistance from the person responsible for IT security. That supports collaboration for this form. It does not establish a universal prohibition on an MSP signing, or a rule that only the business owner may sign every application.

Agree on who coordinates the work and whether assistance is included in your IT service agreement before the deadline becomes urgent. That is a practical project-management step; this guide does not set an MSP's billing obligations.

Build an answer record instead of forwarding the form

Keep a short record for each technical question: exact question and version, proposed factual answer, systems and users checked, date, evidence location and known exceptions. Assign one person to chase unresolved points. This makes it possible to review the meaning of an answer without attaching an uncontrolled collection of screenshots to an email chain.

If the team cannot agree which devices or systems are in scope, first reconcile the records rather than guessing from a tool's device count. Our sister publication's guide to reconciling an IT asset inventory explains how to compare observations, investigate mismatches and assign owners. Use that work to identify known systems and unresolved scope; it does not establish every system's controls or replace a separate account-access review.

If supporting records live in a compliance platform, our sister publication's audit-evidence export guide explains how to check that files retain their dates, scope, relationships and exceptions outside the platform. Then compare each proposed record with the exact application question: does it concern the same systems, people and period, and what remains unknown? Treat an audit record as a candidate source, not automatic proof of an underwriting answer. Resolve suitability and the submission method with the agent; a successful export does not establish insurer acceptance.

For example, “MFA enabled” is not a useful record by itself. A more reviewable note identifies the application or access path, users checked and exception found. The MFA scope guide develops that distinction. Do not send passwords, recovery codes, secret keys or unnecessary personal records as evidence.

Handle a partly true answer

Hypothetical example: IT has confirmed MFA for staff email, but a service provider's remote access has not been checked. If the question concerns remote access as well as email, the email finding cannot settle the whole answer.

Record the verified email scope and the unresolved remote-access scope separately. Ask the agent how to present the uncertainty to the insurer and obtain clarification of an ambiguous question. Do not convert a planned control change into a claim that the control is already in place, or quietly drop an exception to fit a yes/no box. If the supplied form has no suitable place to explain, resolve the submission method with the agent rather than inventing one.

Close the handoff without losing the exceptions

Before submission, reconcile the final form with the answer record and the signing instructions. Keep the submitted version and accompanying explanations together. If facts change while the application is being considered, raise the change with the agent and check the actual form's instructions rather than assuming the earlier answer is still sufficient.

The goal is an accurate, explainable submission—not an “insurance-ready” certificate from the IT provider. No checklist can promise acceptance or determine the legal consequences of an inaccurate answer. At the next cycle, use the renewal guide to revisit changes rather than copying the record unchanged.

Research basis: a published carrier supplement inspected November 17, 2026, with an original workflow informed by practitioner discussion. No private application was completed, no signature authority was assessed and no legal review is claimed.