
网络保险定价已降温。Marsh的全球保险市场指数显示,全球网络保险费率已连续13个季度下降,美国费率在经历2020年和2021年勒索软件驱动的飙升后近期趋于稳定。费率下降的部分原因在于,承保人正在施加更严格的要求,决定你是否甚至有资格投保。一家主要全球承保人最近因理赔量大,已完全停止为律师事务所承保,经纪人预计医疗保健和托管服务提供商(MSP)将是下一个。
Cyber insurance pricing has cooled. Marsh’s Global Insurance Market Index shows global cyber rates falling for a 13th consecutive quarter, with US rates recently stabilizing after the ransomware-driven spikes of 2020 and 2021. Part of the reason rates are lowering is because carriers are imposing stricter requirements that determine if you will qualify at all. A major global carrier recently stopped writing law firms altogether because of claims volume, and brokers expect healthcare and managed service providers (MSPs) to be next.
最新的要求正是许多MSP最不准备的:证明你确实能够恢复。这就是保险公司真正想看到的,而达到这一标准比听起来更难。保险公司为何不再轻信备份 在与网络保险提供商Beltex最近举办的网络研讨会上,熟悉的要求清单首先被提及:外部访问和特权账户的多因素身份验证(MFA)每个终端的端点检测与响应(EDR)需要托管检测与响应(MDR)的24/7值班团队,以及及时打补丁。
The newest requirement is the one many MSPs are least ready for: proof that you can actually recover. This is what insurers really want to see, and meeting the bar is harder than it sounds. Why insurers stopped taking backups on faith In a recent webinar with cyber insurance provider Beltex, the familiar list of requirements came up first: Multifactor authentication (MFA) on external access and privileged accounts Endpoint detection and response (EDR) on every endpoint A staffed 24/7 team where managed detection and response (MDR) is required, and timely patching.
备份现在也加入了这一清单,而且有充分理由。多年来,人们一直认为只要有备份和绿色的作业状态就足够了。理赔情况表明并非如此。现在,攻击者瞄准备份基础设施,以使勒索软件更有效,而未经测试的恢复可能会重新感染生产网络。Beltex描述了一个MSP的案例,该MSP直接从备份恢复了客户,没有让保险公司参与。
Backup is now joining that list, and for good reason. For years it was assumed that having backups and a green job status was good enough. Claims have shown otherwise. Now, attackers go after backup infrastructure to make their ransomware more effective, and an untested restore can re-infect the production network. Beltex described an MSP that restored a client directly from backup without involving the insurer.
攻击者仍在环境中,勒索金额据称翻了一倍。因此,承保人要求提供证明。有些要求提供过去六个月内成功恢复的证据,有些保险申请必须由高层管理人员而非IT总监签署,以明确责任归属。恢复速度的证明与恢复能力的证明同样重要 能够恢复只是问题的一半,因为时间是理赔成本激增的关键。
The attackers were still in the environment, and the ransom reportedly doubled. So, carriers are asking for proof. Some want evidence of a successful restore within the last six months, and some insurance applications must be signed by a C-level executive rather than the IT director to put ownership behind it. Proof of speed matters as much as proof of recovery Being able to recover is only half the question, because time is where claim costs balloon.
事实上,保险公司并不反对支付索赔,它们反对的是支付巨额索赔。Beltex 举的一个典型例子涉及一家 85 人的公司,该公司通过一个零日防火墙漏洞遭到攻击。其托管检测与响应(MDR)解决方案在大约 20 分钟内遏制了入侵,取证确认有两台服务器受到影响,而干净的备份使该公司在 36 小时内完全恢复正常运作。索赔金额约为 8.5 万美元。
Insurers, it turns out, don’t object to paying claims. They object to paying big ones. Beltex’s favorite example involved an 85-person firm hit through a zero-day firewall flaw. Their MDR solution contained the intrusion in about 20 minutes, forensics confirmed two servers were touched, and clean backups had the firm fully functional within 36 hours. The claim came in at around $85,000.
将其与停机和业务中断相对比:一家每天开账单 1 万美元、停机一周的公司,在恢复成本和索赔提交之前,就已经损失了 7 万美元的收入。然而,大型服务器可能需要 4 到 24 小时才能恢复。这就是为什么保险人关心你能多快、多成功地恢复过来。
Compare that with downtime and business interruption: a firm billing $10,000 a day that is offline for a week loses $70,000 in income before recovery costs and claim submission. Yet large servers can take four to 24 hours to restore. That is why underwriters care how fast you can come back and how successfully.
恢复到哪里是另一半问题。速度带来第二个问题:你恢复到哪里?违规咨询律师将最初的 72 小时视为最关键的窗口期,而事件响应(IR)团队在此期间需要隔离和调查受感染的系统。过早恢复到生产环境有重新引入威胁并干扰调查人员所需证据的风险。等待一个安全的地方,时间在流逝。既快又不安全的恢复无法让任何人满意。
Where you recover is the other half Speed raises a second problem: where do you restore to? Breach counsel treats the first 72 hours as the most critical window, and incident response (IR) teams need to isolate and investigate infected systems during it. Restoring into production too early risks reintroducing the threat and disturbing the evidence investigators need. Waiting for a safe place has the clock running. Recovery that is fast but not safe doesn’t satisfy anyone.
要做到这一切比看上去更难。把各个部分放在一起,标准很高:你实际测试过的备份;你能够陈述并达到的恢复时间;以及一个干净、独立的恢复场所。保险人想知道你是否采取了合理的注意义务,所以一排绿色对勾是不够的。运行一次测试恢复。确认你正在保护所有重要的东西,包括有人标记为“不在生产环境”的服务器。
Meeting all of this is harder than it looks Put the pieces together and the bar is high: Backups you have actually tested Recovery times you can state and meet And a clean, separate place to recover to Underwriters want to know whether you exercised reasonable care, so a row of green checkmarks won’t do. Run a test restore. Confirm you’re protecting everything that matters, including the server someone labeled “not in production.”
让业务负责人,而不仅仅是 IT 人员,确认正确的系统在商定的恢复时间目标(RTO)和恢复点目标(RPO)内恢复过来,并将日志、截图和签字留在工单系统中。这不需要像政府审计那样;Beltex 指出,仅此一点就能让你领先于大多数组织。
Have the business owner, not just IT, confirm the right systems came back within agreed recovery time objectives (RTO) and recovery point objectives (RPO), and keep the logs, screenshots and sign-off in your ticketing system. It doesn’t need to resemble a government audit; Beltex noted that this alone puts you ahead of most organizations.
云端灾难恢复的适用场景 云原生灾难恢复改变了计算方式。Cove 的 DRaaS 解决方案让团队能够在 N-able 云中部署一个预先恢复的虚拟机,大约 15 分钟内即可在生产网络之外进行故障切换。这同时解决了速度问题和位置问题。法医调查人员可以在沙箱中验证和搜寻威胁,同时业务保持运行,并可回滚到更早的时间点。
Where cloud disaster recovery fits Cloud-native disaster recovery changes the equation. Cove’s DRaaS solution lets teams stage a pre-recovered VM in the N-able cloud that can be failed over to in about 15 minutes, off the production network. That answers the speed question and the location question together. Forensic investigators can validate and hunt in the sandbox while the business keeps moving, with rollback to earlier points in time.
一旦所有人都认定恢复点是干净的,工作负载就可以通过 VPN 从云端运行,而故障回切则使用恢复代理将更改带回本地。从何处开始 保险是财务上的最后保障,而非糟糕的数据保护态势的替代品。首先列出业务 72 小时内不能丢失的内容,设定恢复目标,对其进行测试并记录结果。检查保单本身:应为独立的网络保单,而非附加在一般保单上的小额条款,保额至少为 100 万美元,随着业务规模扩大应达到 200 万美元。
Once everyone agrees the recovery point is clean, workloads can run from the cloud over VPN, and failback uses recovery agents to bring changes home. Where to start Insurance is a financial failsafe, not a substitute for a bad data protection posture. Start by listing what the business couldn’t lose for 72 hours, set recovery targets, test them and document the results. Check the policy itself: a standalone cyber policy rather than a small add-on to a general one, with a limit of at least $1 million, and $2 million as the business scales.
如果确实发生事件,应将受影响的机器从网络断开,而不是关闭电源,以便法医数据得以保留。N-able Cove Data Protection 被 Infotech 2026 企业备份数据象限评为“冠军”,为组织提供云原生数据保护。
And if an incident does hit, disconnect affected machines from the network rather than powering them off, so forensic data survives. N-able Cove Data Protection, recognized as a Champion in the Infotech 2026 Enterprise Backup Data Quadrant, provides cloud-native data protection for organizations.