Cyber-insurance renewal should not begin when the application arrives.
Applications and underwriting requirements vary by carrier, policy, industry, and risk profile. However, many organizations are asked to provide specific information about identity protection, backups, endpoint security, employee awareness, patching, third-party access, and incident response.
The goal is not to search for the answer an insurer wants to hear. It is to document what the business actually has, identify gaps, and create a practical improvement plan before the renewal deadline.
Use the following checklist with your insurance advisor, legal counsel, internal leadership, and IT provider. Your insurance professional should interpret policy and application requirements; your technology team should validate the controls and evidence behind each answer.
1. Multifactor authentication
Document where multifactor authentication is required, which users and systems are covered, which methods are allowed, and whether exceptions exist. Start with email, remote access, cloud administration, financial systems, backups, and privileged accounts.
CISA advises businesses to require MFA wherever possible and to prioritize phishing-resistant methods when available. A simple yes-or-no answer is not enough if important accounts remain outside the policy.
2. Privileged and administrator access
List every account with elevated rights. Confirm that administrators use separate day-to-day and privileged accounts, access is limited to job responsibilities, old accounts are disabled promptly, and privileged activity can be reviewed.
3. Endpoint protection
Verify that supported computers and servers are enrolled in centrally managed endpoint protection. Document coverage, update status, alert handling, isolation capabilities, and who responds when the platform detects suspicious activity.
4. Email security
Review anti-phishing and malware protection, sender-authentication controls, suspicious-message reporting, external-sender labeling, administrator protections, and the process for investigating compromised mailboxes.
5. Backups and restoration
Identify which systems and data are protected, how frequently backups run, how long copies are retained, and whether at least one copy is protected from routine administrative access and ransomware.
Most importantly, keep evidence of successful restoration tests. A backup status report does not prove the organization can recover the business function.
6. Patch and vulnerability management
Document how the organization identifies missing updates and known vulnerabilities, how quickly different risk levels are addressed, and how unsupported hardware and software are replaced or isolated.
Include network devices, firewalls, wireless systems, applications, cloud services, and third-party appliances rather than limiting the review to employee computers.
7. Employee awareness and verification procedures
Record the training employees receive and the procedures they are expected to follow. Pay special attention to payment changes, payroll requests, password resets, unusual data requests, and unexpected multifactor prompts.
Employees should also have a fast, visible, and blame-free way to report suspicious messages or mistakes.
8. Vendor and remote access
List third parties with remote or administrative access. Confirm that every connection has a business owner, approved purpose, least-privilege permissions, strong authentication, review date, and removal process.
9. Network security and segmentation
Maintain a current inventory of internet-facing services and critical network devices. Review firewall rules, remote-management exposure, guest networks, administrative paths, and separation between sensitive systems and ordinary user or device traffic.
10. Logging and monitoring
Identify which security and administrative events are recorded, where logs are stored, how long they are retained, and what creates an alert. Assign responsibility for reviewing and responding to meaningful events.
11. Incident-response plan
The plan should name decision-makers, internal and external contacts, legal and insurance notification steps, evidence-preservation procedures, communication responsibilities, and authority for urgent containment actions.
Run a tabletop exercise that includes business leadership. CISA recommends that senior management participate in response-plan testing and focus continuity efforts on systems that support critical business functions.
12. Evidence and ownership
For every application response, record:
- The control owner
- The systems and users covered
- The policy or configuration that enforces it
- The evidence that supports the answer
- Any exceptions or open gaps
- The next review date
This turns an annual insurance question into an operating control the organization can maintain.
Start before the application arrives
Give the business time to compare last year’s responses with the current environment. People, applications, vendors, equipment, and policies change. A readiness review several months before renewal makes it possible to correct gaps thoughtfully instead of making rushed decisions during submission week.
T3 Technologies can help document technology controls, validate the current environment, and build a prioritized improvement plan for your team and insurance advisor.
Call to action: Contact T3 Technologies to schedule a cyber-insurance readiness review.

