Layer 1 · Formula 1
CVE-Based Risk Calculator v7
RCVE = [ w1(F×T×M) + w2(IRMterm) + w3(Cnorm_v7) + w4(E) + w5(Ea) + w6(Rdata) ] × S
Cnorm_v7 = [20×(C_raw/C_max)] × √(Unpatched/Total)  ·  Rdata = 20×(Unpatched/Total)×(MTTR_org/MTTR_bench)  ·  IRMterm = (6−IRM)/5×20
Judgment-Derived Inputs
Years since last major framework revision
Years since last comprehensive security audit · F = 0.3×(Framework+Audit age)
T = 1 − (presence × 0.2)
0=Expert · 1=Adequate · 2=Limited · 3=None
M = Capability + (0.5 × years)
1=No plan · 2=Informal · 3=Defined (annual tabletop, basic playbooks) · 4=Managed · 5=Optimized · IRMterm = (6−IRM)/5×20
From threat intelligence and CISA KEV catalog
1.0=Low · 1.2=Medium · 1.4=Finance/Tech/Telecom · 1.5=Healthcare/Gov/Energy
Instrument-Derived Inputs · DC-1 DC-2 DC-5
∑(CVSS Exploit × Impact × CVE Weight) · Weight: 1.0=Moderate, 1.1=High, 1.2=Critical
Highest possible C_raw for your inventory (e.g. 10×10×1.2 × critical CVE count)
DC-1: hosts currently unpatched for this specific CVE
DC-1: total host count in scope · Host_Exposure_Factor = √(Unpatched/Total)
DC-2: mean time to remediate, rolling 90-day window
DC-2: sector average · Qualys TruRisk 2023: 30 days · Rdata = 20×(Unpatched/Total)×(MTTR_org/MTTR_bench)
DC-5: days from CVE disclosure to first observed exploitation
DC-5: industry baseline · Ea = min(20, Avg_TTE/Obs_TTE × 1.5)
Term Weights — w1 through w6 must sum to 1.0 Sum: 1.00
Default: 0.15
Default: 0.10 (raised from v4's 0.05)
Default: 0.30 (reduced from v4's 0.35)
Default: 0.20
Default: 0.10
Default: 0.15
⚠ Weights do not sum to 1.0 — score will reflect actual sum
Layer 2 & 3 — P(breach) and Expected Loss (optional)
Dollar value of affected assets
Time horizon — typically 1.0 for annual EL

Component Breakdown
Layer 1 · Formula 2
Non-CVE Infrastructure Risk Calculator v7
RNon-CVE = [ ln(1 + A×C×D) + I + Fc_weighted ] × S
Fc_weighted = [∑(Faili×Ci) / ∑Ci] / Benchmark × 2.0  ·  ln() prevents saturation at extreme A×C×D values
System Characteristics · DC-4
Architectural revision, OS replacement, or vendor-supported migration — not a routine patch · A = 1.2 × years
1=Non-essential · 3=Important, workarounds exist · 5=Mission-critical, halts operations
1=Isolated · 3=Several systems depend on it · 5=Foundational, cascading failure
Segmentation, access controls, redundancy, anomaly monitoring · I = 2.0 × (1 − presence)
1.0=Low · 1.2=Medium · 1.4=Finance/Tech/Telecom · 1.5=Healthcare/Gov/Energy
Control Failure Factor (Fc_weighted) · DC-3 — Asset Groups

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.

Sector-average control failure rate for comparison (Control Weight: 2.0)
Layer 2 & 3 — P(breach) and Expected Loss (optional)
Dollar value of the infrastructure system
Time horizon — typically 1.0 for annual EL

Component Breakdown
Reference

CVE-Based Risk Score Tiers

ScoreRisk LevelDescriptionRecommended Action
0 – 10MinimalNegligible exposure; current practices effectiveContinue monitoring; no immediate action
11 – 25LowLow-level vulnerabilities; limited impact potentialRegular monitoring; optimize existing controls
26 – 40ModerateModerate vulnerabilities; early action prevents escalationSchedule remediation; proactive mitigation
41 – 60ElevatedSignificant vulnerabilities requiring prompt attentionAddress within sprint cycle; focused action
61 – 75HighHigh-priority with active exploitation potentialImmediate remediation; patch within 72 hours
76 – 100SevereCritical with confirmed exploitation vectorsComprehensive response; executive notification
100+GraveExtreme exposure with active exploitationEmergency response; escalate immediately
Reference

Non-CVE Infrastructure Risk Score Tiers

v7 uses ln(1 + A×C×D) compression — scores are significantly lower than prior versions.

ScoreRisk LevelDescriptionRecommended Action
0 – 2MinimalLow infrastructure risk; no significant issuesContinue monitoring
2 – 5ModerateMinor issues or isolated outdated systemsPlan minor upgrades; monitor trends
5 – 8ElevatedOutdated systems or control weaknesses presentProactive upgrades; prioritize key systems
8 – 12HighSignificant infrastructure vulnerabilitiesImmediate improvement plan; resource allocation
12 – 18SevereSevere issues; high operational and security riskComprehensive overhaul; executive visibility
18+GraveCritical dependencies or failing controls; continuity at riskEmergency action; complete remediation program
Exploitation Factor (E) Scale
DC-5: threat intelligence and CISA KEV catalog
0None — no evidence of exploitation
5Targeted — isolated cases
10Moderate — limited regional or industry
15Widespread — global, multi-industry
20Critical — pervasive, automated, ransomware
Layer 2 · P(breach) Lookup
Interim values — calibrate with org incident data (20+ events)
0–10P(breach) ≈ 0.02–0.04 (Minimal)
11–25P(breach) ≈ 0.04–0.09 (Low)
26–40P(breach) ≈ 0.09–0.15 (Moderate)
41–60P(breach) ≈ 0.15–0.27 (Elevated)
61–75P(breach) ≈ 0.27–0.45 (High)
76–100P(breach) ≈ 0.45–0.65 (Severe)
100+P(breach) ≈ 0.65–0.85 (Grave)
Sector-Specific Adjustment (S) Weights
Applied to both CVE and Non-CVE formulas
WeightRisk LevelSectors
1.0LowAgriculture, Education, Non-digital Retail
1.2MediumLegal, Real Estate, Construction, Utilities, Nonprofit
1.4HighFinance, Technology, Telecommunications
1.5CriticalHealthcare, Government, Energy
About this framework — Version 7.0

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.