# Cyber Insurance Coverage Limit Estimator > Source: https://netray.co/tools/cyber-insurance-coverage-limit-estimator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Estimate a defensible cyber insurance limit from annual revenue, outage length, contribution margin, response costs and restoration costs. ## Category cost-finance ## Industry Discrete Manufacturing ## Audience - CFO - IT security lead - Risk manager ## Tool **Kind:** calculator **Currency:** $ **Inputs:** #### Annual revenue **Key:** revenue **Type:** number **Default:** 60000000 **Min:** 0 **Step:** 1000000 **Unit:** $ **Help:** Revenue of the insured entity for the year. #### Operating days per year **Key:** op_days **Type:** number **Default:** 300 **Min:** 1 **Max:** 365 **Step:** 1 **Unit:** days #### Production outage length **Key:** outage_days **Type:** slider **Default:** 14 **Min:** 1 **Max:** 60 **Step:** 1 **Unit:** days **Help:** Realistic days of full or equivalent lost production. #### Contribution margin **Key:** margin **Type:** number **Default:** 32 **Min:** 0 **Max:** 100 **Step:** 1 **Unit:** % **Help:** Revenue minus variable costs, as a percent. Use net income plus continuing fixed costs if that matches your policy wording. #### Share of lost sales recovered later **Key:** recovered **Type:** number **Default:** 25 **Min:** 0 **Max:** 100 **Step:** 5 **Unit:** % **Help:** Overtime and catch-up that makes up part of the loss. #### Extra expense per outage day **Key:** extra_day **Type:** number **Default:** 12000 **Min:** 0 **Step:** 500 **Unit:** $ **Help:** Manual workarounds, temporary labor, expediting, air freight. #### Forensics, legal and notification **Key:** response **Type:** number **Default:** 350000 **Min:** 0 **Step:** 10000 **Unit:** $ #### System restoration and rebuild **Key:** restore **Type:** number **Default:** 400000 **Min:** 0 **Step:** 10000 **Unit:** $ **Help:** Servers, ERP and MES rebuild, consultants, replacement hardware. #### Ransom demand considered **Key:** ransom **Type:** number **Default:** 1500000 **Min:** 0 **Step:** 50000 **Unit:** $ #### Include ransom in the limit? **Key:** include_ransom **Type:** select **Default:** 0 **Options:** ##### No (policy excludes or you will not pay) **Value:** 0 ##### Yes **Value:** 1 #### Safety buffer **Key:** buffer **Type:** slider **Default:** 20 **Min:** 0 **Max:** 100 **Step:** 5 **Unit:** % **Help:** Allow for estimates being wrong. **Outputs:** #### Revenue per operating day **Key:** daily_rev **Expr:** revenue / op_days **Format:** currency #### Lost sales during outage **Key:** lost_sales **Expr:** daily_rev * outage_days * (1 - recovered / 100) **Format:** currency #### Lost contribution margin **Key:** lost_margin **Expr:** lost_sales * margin / 100 **Format:** currency **Description:** The business interruption loss that policies typically aim to cover. #### Extra expense **Key:** extra_cost **Expr:** extra_day * outage_days **Format:** currency #### Ransom included **Key:** ransom_in **Expr:** ransom * include_ransom **Format:** currency #### Estimated gross loss **Key:** gross **Expr:** lost_margin + extra_cost + response + restore + ransom_in **Format:** currency **Primary:** true #### Suggested coverage limit **Key:** limit **Expr:** gross * (1 + buffer / 100) **Format:** currency **Primary:** true **Description:** Gross loss plus the safety buffer, before retentions and sub-limits. #### Limit as percent of revenue **Key:** pct_rev **Expr:** if(gt(revenue,0), limit / revenue * 100, 0) **Format:** percent **Chart:** #### Estimated gross loss vs outage length **Type:** line **X:** outage_days **From:** 1 **To:** 60 **Steps:** 30 **Series:** - gross - limit **Disclaimer:** A simple planning estimate, not an actuarial or underwriting model. Real policies have retentions, waiting periods, sub-limits for business interruption, ransom, restoration and regulatory costs, and exclusions. Discuss the result with your broker and finance team. ## Content **Intro:** How much cyber insurance is enough? For a manufacturer, the biggest part of the loss is usually the margin lost while the plant is not shipping, followed by response and rebuild costs. This estimator builds a clear, adjustable number to bring to your broker. **Sections:** #### How to use the estimator **Body:** Enter annual revenue and operating days to get a revenue per day. Choose a realistic outage length, not the best case: restoring an ERP, MES and plant servers after encryption can take many days, and customers may not accept late deliveries. Enter your contribution margin, extra expense, response and restoration costs. Decide whether you would consider paying a ransom, and whether the policy would cover it. The chart shows how the loss grows as the outage lengthens, which helps you see the value of faster recovery. **Bullets:** - Use finance's contribution margin, not gross margin by guess - Run three outage lengths: short, likely, severe - Check each cost against policy sub-limits #### The method **Body:** Lost sales equal revenue per operating day times outage days, reduced by the share you can recover later through overtime and catch-up. Lost margin is lost sales times contribution margin. The gross loss adds extra expense per day, forensics, legal and notification costs, system restoration and optionally a ransom. A buffer then covers estimation error. The result is a planning figure; underwriters will also consider retentions, waiting periods and sub-limits for each cost type, which often cap parts of the loss below the headline limit. #### Reading the result and common mistakes **Body:** Compare the suggested limit with quotes and with what you can afford to self-insure. A common mistake is ignoring customer penalties, lost contracts and reputational effects that policies may not cover. Another is forgetting contingent business interruption, where a key supplier or IT provider is the one attacked. If the estimate is far above available limits, that is a signal to invest in recovery speed, which cuts the largest cost directly. **Bullets:** - Include dependency on key suppliers and service providers - Check waiting periods before the cover starts - Faster recovery lowers the biggest loss component - Revisit after major changes to revenue or systems **Cta:** If you want to model the loss using your actual ERP order and margin data on your own servers, Netray can help set that up. The calculator needs no data from you. **Faq:** #### How long should I assume the outage lasts? **Answer:** Use more than one scenario. Many ransomware events with ERP and plant impact take one to several weeks to fully restore. Use your tested recovery times as the base and add margin for surprises, then compare the three scenarios. #### Should I include a ransom payment? **Answer:** That depends on your policy, legal advice and company stance. Many policies limit or exclude ransom, and payments may raise legal and sanctions issues. The estimator lets you view the number with and without it. #### Why use contribution margin instead of profit? **Answer:** Fixed costs continue during an outage, so the loss is closer to revenue minus the variable costs you save. Policies often define covered loss as net income plus continuing expenses. Confirm the exact wording with your broker. #### Is this enough to set my policy limit? **Answer:** It is a good starting point. Final limits also depend on price, retention, sub-limits, exclusions and your risk appetite. Use the numbers to have a specific conversation with your broker and finance team. ## Search terms cyber insurance coverage calculator, how much cyber insurance do I need, cyber insurance limit calculator, ransomware loss estimate manufacturing, business interruption cyber estimate, cyber risk quantification simple, cyber insurance limit manufacturer --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json