Which plants carry the risk
Share of company expected annual loss. Seven more plants: $5.7M (31%).
Rank every facility by its own expected annual loss and see where the loss sits, so staff and budget go to the plants that matter most.
Start with a DeRISK™ CRQ estimate for your company, built from public data. Facility-by-facility results begin at Level 3 Board-Grade, which takes about 50 questions and no OT network data.
Share of company expected annual loss. Seven more plants: $5.7M (31%).
Every plant has findings. Few teams can say which plant’s loss matters most.
DeRISK quantifies each facility on its own, then puts the facilities side by side. The same example company runs through the last two steps.
Each facility gets its own expected annual loss, with a bad-year (1-in-20) and a severe-year (1-in-100) figure. The facility expected annual losses add up to the company figure. The range around each result narrows as better inputs replace assumptions.
Expected annual loss by plant. Plant-by-plant results start at Level 3 Board-Grade.
Example company. Each plant has its own expected annual loss, and together they make up the company figure.
Put every plant side by side, ranked by expected annual loss. In the example company, Houston carries $4.4M (24%) of the $18.4M total, and five plants carry about 70% of it. Each plant’s control strengths and gaps sit in the same view.
| Plant | Firewalls | Malware prevention | Vulnerabilities | Access controls | Detection | Incident response | Backups | Average |
|---|---|---|---|---|---|---|---|---|
| Houston | 1.0 | 2.0 | 1.5 | 1.5 | 2.0 | 2.0 | 1.5 | 1.6 |
| Baton Rouge | 2.0 | 2.5 | 1.5 | 2.0 | 1.5 | 2.0 | 1.5 | 1.9 |
| Chicago | 2.5 | 2.5 | 2.0 | 2.5 | 2.0 | 2.0 | 2.5 | 2.3 |
| Pittsburgh | 2.5 | 2.0 | 2.0 | 2.0 | 2.0 | 1.5 | 2.5 | 2.1 |
| Tulsa | 1.5 | 1.5 | 1.0 | 1.5 | 1.0 | 1.0 | 1.5 | 1.3 |
Scale 0 to 4; lighter is weaker. Tulsa scores weakest, but Houston carries more loss: rank by loss, not by score. Also available in IEC 62443, NIST SP 800-82r3 or the DeRISK Control Model.
Example company. Control scores by plant, so you can see where the gaps sit.
Open the top plant to see why it ranks first. In the example, Houston’s weakest control is firewalls, its top attack method is ransomware with data exfiltration, and its top loss type is business interruption. On its own, a 1-in-100 year there could cost up to $46M.
Two figures, both labeled: Houston’s share of company loss, and its loss on its own.
Example company. Houston’s share of company loss and its loss on its own, both labeled.
The risk trajectory, with the forecast as planned fixes land, plus exhibits from the COO and Chief Risk Officer sample reports, built facility by facility.
Expected annual loss. The forecast follows the order of the planned projects.
Worst facility, 1-in-100
8.18Days of facility revenue · Example Facility 1, VaR 99thExample Facility 1 has the highest standalone facility Annual Expected Loss. Its 1-in-100-year modeled loss equals 8.18 days of facility revenue.
| Metric | Loss | Days of rev. | % of revenue |
|---|---|---|---|
| Annual Expected Loss | $1,630,000 | 0.5 | 0.14% |
| VaR 95th (1-in-20) — attachment anchor | $6,120,000 | 1.86 | 0.51% |
| VaR 99th (1-in-100) — limit-sizing anchor | $10,650,000 | 3.24 | 0.89% |
The probability of a loss (frequency) and its severity (magnitude), over thousands of simulated years.
A typical year, a bad year and a severe year, each with its own figure.
The report lists its assumptions and limitations.
See the inputs behind the number, and overrule the ones you know better.
Level 1 and Level 2 are free and need no OT data. Level 3 Board-Grade gives each facility its own result from about 50 questions. Level 4 Evidence-Grade adds OT network data for each facility.
Add-ons start here
Create a free account. The Level 1 Estimate and Level 2 Baseline are free. They give a company-level expected annual loss and a company report, with no OT network data needed. Level 3 Board-Grade adds facility-by-facility results and the five executive reports.
No credit card. No OT network data needed to start.