Cnorm_v7 = [20×(C_raw/C_max)] × √(Unpatched/Total) · Rdata = 20×(Unpatched/Total)×(MTTR_org/MTTR_bench) · IRMterm = (6−IRM)/5×20
Fc_weighted = [∑(Faili×Ci) / ∑Ci] / Benchmark × 2.0 · ln() prevents saturation at extreme A×C×D values
v7 weights failures by the criticality of affected systems. Add up to 3 asset groups. Each group needs a failure rate (%) and criticality score. Industry benchmark is the sector-average failure rate.
CVE-Based Risk Score Tiers
| Score | Risk Level | Description | Recommended Action |
|---|---|---|---|
| 0 – 10 | Minimal | Negligible exposure; current practices effective | Continue monitoring; no immediate action |
| 11 – 25 | Low | Low-level vulnerabilities; limited impact potential | Regular monitoring; optimize existing controls |
| 26 – 40 | Moderate | Moderate vulnerabilities; early action prevents escalation | Schedule remediation; proactive mitigation |
| 41 – 60 | Elevated | Significant vulnerabilities requiring prompt attention | Address within sprint cycle; focused action |
| 61 – 75 | High | High-priority with active exploitation potential | Immediate remediation; patch within 72 hours |
| 76 – 100 | Severe | Critical with confirmed exploitation vectors | Comprehensive response; executive notification |
| 100+ | Grave | Extreme exposure with active exploitation | Emergency response; escalate immediately |
Non-CVE Infrastructure Risk Score Tiers
v7 uses ln(1 + A×C×D) compression — scores are significantly lower than prior versions.
| Score | Risk Level | Description | Recommended Action |
|---|---|---|---|
| 0 – 2 | Minimal | Low infrastructure risk; no significant issues | Continue monitoring |
| 2 – 5 | Moderate | Minor issues or isolated outdated systems | Plan minor upgrades; monitor trends |
| 5 – 8 | Elevated | Outdated systems or control weaknesses present | Proactive upgrades; prioritize key systems |
| 8 – 12 | High | Significant infrastructure vulnerabilities | Immediate improvement plan; resource allocation |
| 12 – 18 | Severe | Severe issues; high operational and security risk | Comprehensive overhaul; executive visibility |
| 18+ | Grave | Critical dependencies or failing controls; continuity at risk | Emergency action; complete remediation program |
| 0 | None — no evidence of exploitation |
| 5 | Targeted — isolated cases |
| 10 | Moderate — limited regional or industry |
| 15 | Widespread — global, multi-industry |
| 20 | Critical — pervasive, automated, ransomware |
| 0–10 | P(breach) ≈ 0.02–0.04 (Minimal) |
| 11–25 | P(breach) ≈ 0.04–0.09 (Low) |
| 26–40 | P(breach) ≈ 0.09–0.15 (Moderate) |
| 41–60 | P(breach) ≈ 0.15–0.27 (Elevated) |
| 61–75 | P(breach) ≈ 0.27–0.45 (High) |
| 76–100 | P(breach) ≈ 0.45–0.65 (Severe) |
| 100+ | P(breach) ≈ 0.65–0.85 (Grave) |
| Weight | Risk Level | Sectors |
|---|---|---|
| 1.0 | Low | Agriculture, Education, Non-digital Retail |
| 1.2 | Medium | Legal, Real Estate, Construction, Utilities, Nonprofit |
| 1.4 | High | Finance, Technology, Telecommunications |
| 1.5 | Critical | Healthcare, Government, Energy |
This calculator implements Version 7 of the quantitative risk framework developed by Aubrey Perin in A Quantitative Framework for Holistic Cybersecurity Risk Evaluation Using Actuarial Principles. Version 7 introduces a vendor-neutral Data Integration Layer (Layer 0), replaces analyst-rated R with the Exposure Coverage Ratio (ECR), upgrades the Non-CVE Control Failure Factor to a criticality-weighted formulation, scales C_norm by deployment breadth (unpatched host ratio), and adds Layers 2–3 P(breach) and Expected Loss outputs.
The canonical proof in Section 9 of the white paper re-evaluates CVE-2023-21716 end-to-end: the v3 score of 182.79 (Grave) becomes 8.46 (Minimal) under v7 — correctly reflecting that only 15% of the fleet was exposed and remediation lag was moderate. Full derivations, calibration guidance, limitations, and Python Monte Carlo reference implementation are in the white paper PDF. This framework underpins the ALE Standard in Ethical Business: Restoring Philosophical Integrity.