Key Points
- Document MFA, endpoint protection (EDR), backups, patching and vulnerability management, incident response, access control, and email security and training.
- Prove MFA enforcement by pairing a Microsoft Entra ID MFA registration export with Conditional Access policy exports.
- Test backups regularly and keep immutable or offline copies, encryption settings, and dated restore logs as proof.
- Map controls to NIST CSF 2.0, CIS Controls v8.1, or ISO/IEC 27001:2022 and summarize the results in a compliance scorecard.
- Automate evidence collection with scheduled scripts and store versioned, dated files in one cyber insurance readiness folder.
- Refresh your evidence every quarter and before each application or renewal and confirm current carrier requirements with your broker.
Cyber insurers want current, dated proof that your controls work. For most applications, that means evidence of enforced multi-factor authentication (MFA), endpoint protection coverage, tested and protected backups, patching and vulnerability management, a written incident response plan, and managed access.
Cybersecurity Ventures projected that cybercrime would cost the world $10.5 trillion in 2025 and expects the annual figure to reach about $12.2 trillion by 2031 or roughly $1 trillion per month. As a result, more companies are looking for higher insurance coverage, and insurers are asking for more detailed documentation.
This guide covers two situations. In the first, you apply for your own MSP cyber and technology errors and omissions coverage. In the second, you help clients assemble evidence for their policies. The evidence is similar, but insurers may ask MSPs extra questions about remote management tools, privileged access, and tenant separation, so confirm the details with your broker.
Automate software updates and demonstrate timely vulnerability remediation for insurance audits.
What do cyber insurers ask MSPs to document?
Most cyber insurance applications ask for evidence in the seven areas below:
| Control | What to show | Evidence examples |
| Multi-factor authentication | MFA required for email, remote access, cloud apps, and privileged accounts | Conditional Access policy export, MFA registration report, privileged account list |
| Endpoint protection | EDR on every endpoint and server | Coverage report with device counts and percentages |
| Backups | Encrypted, immutable, or offline copies with tested restores | Backup configuration export, dated restore test log |
| Patching and vulnerability management | Patch timelines met and findings tracked to closure | Patch compliance report, vulnerability summary |
| Incident response | Written plan that’s reviewed and tested | Plan with version history, tabletop exercise notes |
| Access control | Privileged access limited and reviewed | Access review logs, inactive account reports |
| Email security and training | Email authentication and completed training | SPF, DKIM, and DMARC settings, training completion logs |
Security posture reports
These reports demonstrate how well protected your MSP is from common cyberthreats. They should include:
| Component | Purpose/value |
| Recent vulnerability assessments and patching logs | Demonstrates that your systems are regularly scanned for vulnerabilities and patches are applied on time |
| Endpoint protection coverage report showing the percentage of endpoints and servers with an active EDR agent (plus alert monitoring evidence) | Confirms that endpoint protection is active and monitored on every device since many underwriters distinguish EDR from traditional antivirus |
| Multi-factor authentication (MFA) enforcement and access logs across all privileged accounts | Ensures that MFA is enforced for all critical accounts |
Backup and disaster recovery (BDR) verification
This reassures insurers that your organization can recover from data loss or system failure.
| Component | Purpose/value |
| Documented backup schedules, retention policies, and encryption standards | Shows that your backups are regular, secure, and compliant with industry data protection standards |
| Logs of successful restore tests and failover drills | Highlights that your backup strategies have been tested and are working in practice |
Tip: Keep a dated log of restore tests and store it with your backup configuration exports. NinjaOne Device Backup boot verification captures a screenshot as evidence that a Windows image backup can boot.
Policy frameworks and governance
These documents establish that your organization implements a structured approach to cybersecurity.
| Component | Purpose/value |
| Incident response plan and evidence of testing | Proves readiness in case of a breach |
| Acceptable use, breach notification, and data retention policies | Ensures that your employees know and understand their responsibilities |
| A map of controls to NIST CSF 2.0 (including the Govern function), CIS Controls v8.1, or ISO/IEC 27001:2022, summarized in a compliance scorecard | Demonstrates that your security practices align with industry standards |
Access control and privilege management
This section demonstrates that you don’t grant access to systems and data without proper oversight.
| Component | Purpose/value |
| Logs of inactive or orphaned account reviews | Shows that your organization is actively managing user accounts |
| Privilege escalation policies and audit trails | Illustrates how your organization grants and monitors escalated access |
| Logs from recent access reviews | Establishes that you regularly review and update access rights |
Automating documentation processes for cybersecurity risk assessment
Since compiling security documentation can be time-consuming, you can use scripting to automate the process. This sample PowerShell script exports the MFA registration status of every user in Microsoft Entra ID (formerly Azure AD). A registration export shows who has enrolled an authentication method. Pair it with an export of your Conditional Access policies or security defaults settings to show that MFA is required for email, remote access, and privileged accounts.
Connect-MgGraph -Scopes “AuditLog.Read.All”
$stamp = Get-Date -Format “yyyy-MM-dd”
$folder = “C:\ComplianceEvidence”
New-Item -ItemType Directory -Path $folder -Force | Out-Null
Get-MgReportAuthenticationMethodUserRegistrationDetail -All |
Select-Object UserPrincipalName, UserDisplayName, IsAdmin,
IsMfaRegistered, IsMfaCapable, IsPasswordlessCapable,
DefaultMfaMethod,
@{ Name = “MethodsRegistered”; Expression = { $_.MethodsRegistered -join “; ” } } |
Export-Csv “$folder\MFA_Registration_$stamp.csv” -NoTypeInformation
Disconnect-MgGraph
Best practices for effective cybersecurity documentation
Here are some additional best documentation practices to make preparing for a cybersecurity readiness assessment easier:
Create a “cyber insurance readiness” folder
Set up a centralized folder where you can put all the key documentation that insurers typically ask for during a security readiness assessment, including:
- Backup logs
- Vulnerability scan summaries
- Policy templates
- MFA snapshots
Organizing all your files in one place will make filing for new insurance applications easier.
Use version control and timestamping
To ensure that you don’t accidentally submit outdated documentation to insurers, all your files should have:
- A clear version number (e.g., v1.2, v2.0)
- A last updated date
- A change log, if applicable
This will help you maintain a clear audit trail.
Leverage simple compliance mapping
Map your documents and controls to a recognized cybersecurity framework, like:
- NIST Cybersecurity Framework (CSF) 2.0
- CIS Controls v8.1
- ISO/IEC 27001:2022
A mapping table or checklist demonstrates that your organization’s cybersecurity strategies align with the industry’s best practices.
Train clients on their role
In addition, you must train your clients on their role in maintaining a secure infrastructure:
- Enforcing strong password policies
- Using only approved software
- Reporting suspicious activity promptly
Documenting these shared responsibilities prevents misunderstandings and helps strengthen your client’s overall security posture.
Review and refresh your documentation quarterly
Cyber insurance requirements can change quickly, so you should review and update your documentation at least every quarter. Set recurring reminders to re-run automation scripts for exporting data and incorporate insurer feedback into your existing documentation.
Coordinate with brokers beforehand
Finally, talk to your insurance brokers before the cybersecurity readiness assessment. Ask them about the documentation they typically request, their preferred formats, and any frameworks they follow.
Eliminate manual audit prep and generate proof of efficient vulnerability remediation.
What is cyber insurance, and why is it important?
Cyber insurance, or cyber liability insurance, helps businesses cover financial losses from data breaches and cyberattacks. It works just like any insurance policy: providers will pay for covered damages and costs, including data recovery, legal fees, and even lost revenue. With the cost of cybercrimes increasing alarmingly, organizations need safeguards to help them recover the financial and reputational damage they may incur from an attack.
However, it’s important to note that cyber insurance can never replace an effective cybersecurity program. Instead, think of it as your safety net and robust security posture as the foundation of your defense mechanism. Without a strong cybersecurity program in place, most insurers will offer you limited protection for a steep price. Worse yet, they’ll refuse to issue you coverage.
How does NinjaOne help you collect evidence?
NinjaOne includes capabilities that help you gather and organize the evidence that insurers ask for.
| Evidence needed | NinjaOne capability | What it does |
| Policies and runbooks | NinjaOne Documentation | Stores policies, checklists, and runbooks inside the NinjaOne platform, where your team already manages endpoints |
| Encryption status | NinjaOne Endpoint Management | Monitors BitLocker encryption on Windows and FileVault encryption on macOS from the console |
| Scheduled evidence collection | NinjaOne Automation | Runs automation scripts on a schedule or through policy conditions |
| Backup restore evidence | NinjaOne Backup | Boot verification tests Windows image backups and captures a screenshot as evidence |
| Vulnerability and patch evidence | NinjaOne Autonomous Patch Management and Vulnerability Management | Tracks patch status and groups vulnerability data by CVE on system, organization, and device dashboards |
| Third-party scan data | NinjaOne Vulnerability Importer | Ingests vulnerability scan data from supported third-party scanners |
A walkthrough of this guide is available on How to Document MSP Security Readiness for Cyber Insurance Applications.
Quick-Start Guide
NinjaOne’s Security Documentation Capabilities
1. Vulnerability Management
NinjaOne offers a Vulnerability Importer that allows MSPs to:
- Import vulnerability data from multiple scanning tools
- Centralize vulnerability tracking across devices
- Generate comprehensive vulnerability reports
2. Security Frameworks and Tracking
Track cybersecurity Key Performance Indicators (KPIs):
- Framework coverage
- Risk reduction speed
- Evidence readiness
- Align with cybersecurity frameworks like NIST
3. Key Documentation Tools
- Centralized visibility
- Compliance tracking
- Automated reporting
- Device health status monitoring
Recommended Approach for Cyber Insurance Documentation
1. Comprehensive Vulnerability Tracking
Use NinjaOne’s Vulnerability Importer to document:
- Identified vulnerabilities
- Remediation status
- Patch management efforts
2. Security Incident Response
- Develop and document a clear incident response playbook
- Track and log security incidents
- Demonstrate proactive security management
3. Continuous Monitoring and Reporting
Implement quarterly security reviews
Generate reports showing:
- Security controls
- Risk mitigation efforts
- Continuous improvement
4. Integration of Security Tools
Utilize integrated security solutions like:
- SentinelOne for endpoint protection
- Vulnerability scanning tools
- Patch management
Strategic documentation: The key to a successful cybersecurity readiness assessment
As cybercrimes continue to escalate, insurance providers are becoming increasingly selective about the organizations to which they grant coverage. They don’t just want to hear that you have the right security measures in place; they want you to prove it by submitting clear, verifiable evidence.
This is where strategic documentation comes in. Well-organized reports and policies that align with industry standards make it easier for underwriters to evaluate your application and for you to answer their follow-up questions. More importantly, strategic documentation reinforces your MSP’s reputation as a proactive cyber-risk mitigator.
Related topics:

