Cyber insurance requirements can change by insurer, policy, industry, revenue, claims history, and the systems your business uses. This readiness guide helps you prepare for applications and renewals by tracking the controls insurers commonly ask about, assigning ownership, preserving evidence, and scheduling reviews before deadlines create pressure.
Overview
Small business cybersecurity insurance is not a substitute for security controls, and an insurance application is not a complete security assessment. It is best treated as a structured review of how your company prevents, detects, and responds to cyber incidents. The application may ask about identity protection, backups, endpoint security, email security, employee training, vendors, and incident response. Your policy may also include conditions, exclusions, sublimits, or representations that require careful review.
Requirements vary, so use your insurer’s questionnaire and policy wording as the authoritative reference. The checklist below is a practical preparation tool rather than a guarantee of eligibility or coverage. Before signing an application, answer each question accurately, document assumptions, and ask your broker or insurer to clarify wording you do not understand. Avoid describing a planned control as active until it has been implemented and verified.
A useful process has four parts:
- Inventory: Identify systems, accounts, data, devices, vendors, and business processes that affect cyber risk.
- Control: Confirm that safeguards are configured, used consistently, and appropriate to the risk.
- Evidence: Keep dated records that demonstrate what is in place and who reviewed it.
- Review: Recheck controls on a schedule and after meaningful changes.
This approach also strengthens general cybersecurity for small business, whether or not you purchase a policy.
What to track
1. Multifactor authentication and access
Track which important systems require MFA, including email, remote access, administrator accounts, financial platforms, cloud storage, and other business-critical SaaS accounts. Record the system, enforcement status, excluded users or applications, date checked, and control owner. Pay particular attention to administrator and remote-access accounts. A password manager can help reduce reused credentials; see our guide to password managers for small business for selection and setup considerations.
Maintain a current user list and review access when employees join, change roles, or leave. Keep evidence of offboarding, privileged-account reviews, and the removal of inactive accounts. If an application cannot support MFA, document the limitation and the compensating safeguards rather than leaving the exception unexplained.
2. Backups and recovery testing
Track the systems and data covered by backups, backup frequency, retention, storage location, access restrictions, and the last restoration test. A backup that has never been restored should be treated as unverified. Record what was tested, whether recovery met the business need, and what corrective action remains open.
Include critical cloud services in the review. A SaaS provider’s availability features do not necessarily replace your responsibility to preserve important records or configurations. Our SaaS security guide can help organize account and administrative controls.
3. Endpoint, email, and ransomware defenses
Maintain an inventory of laptops, desktops, servers, and mobile devices used for work. Track operating-system updates, supported endpoint protection, disk encryption where appropriate, screen-lock settings, and devices that fall outside management. Note exceptions and their owners.
For email, record spam and malware filtering, domain-protection settings if used, administrator access, and the process for reporting suspicious messages. Technical controls should be paired with a reporting workflow. Use the small business phishing prevention program as a practical reference for training, testing, and escalation.
4. Incident response and reporting
Keep an incident response plan with named roles, contact details, decision points, evidence-preservation steps, and instructions for contacting your insurer or approved response providers. Know whether the policy requires prompt notice, uses a specific reporting channel, or requires consent before engaging certain experts. Do not wait for an incident to discover these details.
Test the plan with a short tabletop exercise. Record the scenario, participants, decisions, gaps, and follow-up owner. The incident response plan template provides a starting point for organizing this information.
5. Training, vendors, and sensitive data
Track employee cybersecurity training, completion dates, topics covered, and the process for reporting suspected fraud or account compromise. Training should address phishing, payment-change requests, password handling, lost devices, and escalation.
For vendors, record which providers handle sensitive data, connect to business systems, or support critical operations. Track due diligence, contract security terms, MFA availability, breach-notification language, and review dates. A vendor risk assessment template can help standardize the review.
Finally, document the types of personal, financial, health, confidential, or regulated information your business holds, where it is stored, who can access it, and how long it is retained. This inventory supports both cyber insurance preparation and privacy compliance for small business.
Cadence and checkpoints
Use a renewal calendar that begins well before the application deadline. A practical schedule is:
- Monthly: Review new users, departures, privileged accounts, security alerts, backup failures, unresolved incidents, and major software changes.
- Quarterly: Test a backup restoration, review MFA coverage, sample endpoint update status, examine vendor changes, and run a short access review. The quarterly security review can serve as a recurring checklist.
- About 90 days before renewal: Obtain the current questionnaire and policy documents, compare them with the prior application, identify changed questions, and assign control owners.
- About 60 days before renewal: Close high-priority gaps, gather evidence, confirm claims and incident history, and request clarification on exclusions or conditions.
- About 30 days before renewal: Perform a management review, verify that answers match actual configurations, and retain the submitted application and supporting records.
- After renewal: Record new requirements, deadlines, endorsements, and any controls that must remain continuously active.
Use a simple evidence matrix with columns for control, system, owner, status, evidence location, last review, next review, and open action. Evidence might include an access-review export, backup test record, training log, endpoint inventory, policy acknowledgment, or incident exercise notes. Store records in a restricted location and avoid placing unnecessary personal or confidential information in the matrix.
How to interpret changes
Not every questionnaire change means your business has become less secure, and not every unchanged question means your risk is unchanged. Interpret changes in context.
A new system, acquisition, remote-work arrangement, payment process, or data type may expand your exposure even if your existing controls remain configured. A new vendor may introduce a dependency that needs review. A staffing change may leave an access or control-ownership gap. A security incident, near miss, or failed backup test should trigger a focused review rather than waiting for renewal.
Separate issues into three categories:
- Implemented: The control is active, tested where appropriate, and supported by current evidence.
- Planned: Work has been approved but is not yet complete. Do not represent it as implemented.
- Exception: The control is not feasible or not applicable. Document the reason, risk, compensating measure, owner, and review date.
Prioritize gaps that could affect business-critical accounts, privileged access, backups, payment processes, sensitive data, or incident reporting. If a requirement cannot be met before renewal, discuss the situation with the broker or insurer and ask how it affects eligibility, terms, or coverage. Keep written clarification with your records.
When to revisit
Revisit this checklist at least quarterly and whenever your insurer provides a new questionnaire or policy endorsement. Also begin an early review after a cyber incident, suspected fraud, ransomware event, lost device, major vendor change, migration to a new cloud platform, office expansion, acquisition, or significant change in the data your company collects.
For the next review, create a one-page action list:
- Download the current insurance questionnaire and policy wording.
- List every required control and assign one accountable owner.
- Verify MFA, backups, endpoint protection, access reviews, training, vendors, and incident-response contacts.
- Attach dated evidence and mark each item implemented, planned, or excepted.
- Test at least one recovery or response procedure.
- Escalate unclear answers and coverage questions before submitting the application.
- Schedule the next monthly and quarterly checkpoints.
For a broader baseline, compare your results with the 30-day small business cybersecurity plan and the cybersecurity budget checklist. Keeping the evidence current makes renewal less disruptive and gives your team a clearer picture of its actual security readiness.