A cyber insurance application is also a practical test of your small business cybersecurity program. This checklist helps you prepare for insurer questions, monitor the controls that commonly affect underwriting discussions, and assemble evidence before an application or renewal. Requirements vary by insurer, industry, business size, and policy wording, so treat this as a readiness framework—not a guarantee of coverage or acceptance.
Overview
Cyber insurers typically want to understand how your business prevents common incidents, limits unauthorized access, responds to an attack, and recovers operations. An application may ask whether you use multifactor authentication (MFA), endpoint protection, tested backups, email security, employee training, access reviews, and an incident response plan. It may also ask about technology providers, sensitive data, remote access, payment processes, and prior incidents.
The most important readiness principle is accuracy. Do not answer that a control is “in place” simply because a tool has been purchased. Confirm that it covers the relevant systems, is configured correctly, and is used consistently. A mismatch between an application answer and your actual environment can create problems during underwriting, renewal, or a claim review.
Build a small, organized evidence file rather than searching for documents at the last minute. It can be a restricted folder or a physical binder, provided access is limited and the contents are protected. Keep the current insurance application, policy documents, system inventory, security policies, reports, test records, and remediation plans together.
For context on the underlying controls, see Safely’s guides to MFA and password policies, endpoint protection, and backup and restore testing.
What to track
Use the following crosswalk to turn broad cyber insurance requirements into recurring management tasks. The precise questions and thresholds will differ, so compare this list with your broker’s or insurer’s current questionnaire before submitting information.
1. MFA and privileged access
Track where MFA is enabled, especially for email, remote access, administrator accounts, cloud services, financial systems, and other externally accessible tools. Maintain a list of exceptions and document the reason, owner, compensating control, and target date for closure.
Also track administrator accounts, dormant accounts, shared accounts, and former employees whose access has been removed. A password policy alone does not show that access is being managed. Preserve an access review record showing who reviewed the accounts, when the review occurred, and what changes were made.
2. Endpoint protection and device inventory
Maintain an inventory of company laptops, desktops, servers, and other managed endpoints. Record the assigned user, operating system, security software, encryption status where applicable, and last check-in. Review devices that have stopped reporting or are outside the normal management system.
Track whether endpoint protection is active and whether alerts are reviewed. Keep deployment reports, alert summaries, remediation records, and evidence that unsupported or unauthorized devices are addressed. Antivirus alone may not answer every insurer’s question; the relevant issue is whether your control set is appropriate for the devices and risks you have declared.
3. Backups and recovery testing
Document what business data is backed up, how often backups run, where copies are stored, and who can change or delete them. Identify whether backup access is separated from ordinary user accounts and whether a compromised administrator account could affect all copies.
Record restore tests, including the date, data or system tested, result, problems found, corrective action, and person responsible. A backup dashboard showing that a job completed is useful, but it does not replace evidence that important files or systems can actually be restored.
4. Email security and phishing prevention
Track the security settings used to protect business email, such as spam and malware filtering, suspicious-link controls, and protections for accounts that can approve payments or access sensitive information. Keep configuration summaries and records of significant changes.
Maintain an employee training log with the audience, date, topic, completion status, and follow-up for overdue employees. Pair training with a simple reporting workflow: employees should know how to report a suspicious message, and someone should be responsible for reviewing reports and escalating genuine incidents. Safely’s phishing prevention checklist can help structure this process.
5. Incident response
Keep a current incident response plan with named roles, contact details, decision points, and steps for preserving evidence and containing damage. Include contacts for your insurer, broker, legal adviser, technology providers, and relevant internal decision-makers, but verify the policy’s notification process rather than assuming any contact method is acceptable.
Record tabletop exercises and real incidents separately. For each exercise, document what scenario was used, who participated, where delays occurred, and which improvements were assigned. A plan that has never been reviewed may be difficult to use under pressure. See the small business incident response plan guide for a practical exercise format.
6. Vendor, cloud, and SaaS oversight
Keep an inventory of cloud applications and technology providers that store, process, transmit, or can access business data. Record the service owner, data handled, administrator accounts, security features, contract location, and whether the provider supports your recovery and incident processes.
Track vendor reviews, including security questionnaires, relevant contract terms, notification procedures, and unresolved concerns. Review the inventory when a new application is adopted—not only at renewal. The SaaS security checklist provides a useful starting point for identifying shadow IT and excessive permissions.
7. Data protection and document handling
Identify the information that would create the greatest operational, financial, legal, or reputational impact if exposed or unavailable. Track where it is stored, who can access it, how it is shared, and when it should be deleted or archived.
Document controls for sensitive documents, including sharing permissions, external recipients, e-signature workflows, and retention. Link this work to your privacy compliance obligations rather than treating insurance preparation as a separate exercise. Safely’s guides to secure document sharing and data retention can help organize the evidence.
8. Policies, training, and insurance details
Maintain dated versions of your information security, acceptable use, remote work, access control, incident response, and data retention policies. Record employee acknowledgment or training where relevant. Policies should describe practices your business can actually follow; avoid copying controls that are not implemented.
Keep the current policy declarations, endorsements, exclusions, sublimits, deductibles, waiting periods, notification requirements, and definitions in the evidence file. Coverage terminology varies, and a security control does not automatically mean a particular loss is covered. Ask the broker or insurer to explain unclear terms before renewal.
Cadence and checkpoints
A recurring schedule makes cyber insurance readiness part of ordinary operations instead of an annual scramble.
Monthly checks
- Review backup completion and record at least one meaningful restore check according to your recovery plan.
- Review endpoint and email security alerts, unresolved high-risk issues, and devices that are no longer reporting.
- Update the asset and SaaS inventory for new systems, changed owners, and retired tools.
- Record security incidents, suspicious activity, and corrective actions, even when no claim is made.
Quarterly checks
- Review administrator, remote-access, financial, and other sensitive accounts; remove unnecessary access.
- Check MFA coverage and document exceptions.
- Review critical vendors and cloud applications, including changes to data access or contracts.
- Confirm employee training completion and test the phishing-reporting workflow.
- Review open remediation items and assign owners and due dates.
Before renewal or a new application
Start at least several weeks before the requested submission date, allowing time to clarify questions and close evidence gaps. Compare the new questionnaire with the prior application line by line. Reconcile declared locations, users, revenue-related information, data types, remote access, technology providers, and security controls with your current environment.
Then ask a responsible technical or operations lead to validate every “yes” answer. Prepare a short explanation for controls that are partially implemented, temporarily unavailable, or scheduled for improvement. Transparent documentation is more useful than an unsupported assurance.
Evidence binder index
A practical index may include:
- Current application, policy documents, endorsements, and broker correspondence.
- System, endpoint, user, administrator, and SaaS inventories.
- MFA coverage report, access reviews, and terminated-user records.
- Endpoint, email, and vulnerability-management summaries.
- Backup schedules, restore-test results, and recovery procedures.
- Incident response plan, tabletop records, and incident log.
- Vendor reviews, contracts, security questionnaires, and notification contacts.
- Security policies, employee training records, and acknowledgment records.
- Open risk register with owners, deadlines, and status updates.
Do not store passwords, recovery codes, or other secrets in the binder. Protect the folder with appropriate access controls and retain only the information needed for the business purpose.
How to interpret changes
Not every change requires a new insurance application, but every material change deserves review. A new remote-access method, acquisition, cloud migration, payment workflow, major vendor, office location, or sensitive-data process can change the answers you previously gave.
Use a simple status system for each control:
- Implemented: The control is deployed across the stated scope, monitored, and supported by recent evidence.
- Partially implemented: Coverage exists but has exceptions, gaps, or inconsistent use. Record the scope and remediation date.
- Planned: The control is not currently in place. Do not represent it as implemented; document the plan and interim safeguards.
- Not applicable: Explain why it does not apply, rather than leaving the answer unexplained.
Pay particular attention to recurring exceptions. An MFA exception that remains open for months, repeated failed restore tests, inactive endpoint agents, or unresolved high-risk vendor findings may indicate that a control exists on paper but not in practice. Prioritize issues that affect privileged access, internet-facing systems, backups, payment processes, or large amounts of sensitive data.
Also distinguish security readiness from coverage interpretation. A control can reduce risk without eliminating it, and a policy can contain exclusions or conditions that require separate attention. Ask qualified insurance and legal professionals about the policy language, notification obligations, and business-specific compliance questions.
When to revisit
Review this checklist monthly for evidence collection and quarterly for a broader control review. Revisit it immediately after a security incident, significant technology change, merger or acquisition, major vendor change, change in data handled, or change in remote-work arrangements.
Before each application or renewal, obtain the current questionnaire and policy wording rather than relying on last year’s answers. Insurer expectations, forms, exclusions, and requested evidence can change. This article should likewise be refreshed when those questionnaire patterns or your business environment change.
To act now, assign one owner and complete these five steps:
- Create a restricted evidence folder using the binder index above.
- Export current MFA, endpoint, backup, email, user, and SaaS reports.
- Run a short access review and record unresolved exceptions.
- Test one important restore and document the result.
- Compare your actual controls with the answers on the last insurance application, then schedule remediation for every mismatch.
Repeating those steps on a defined schedule gives a small business a clearer view of its cyber risk, a more reliable renewal process, and evidence that reflects how security actually operates.