Not every CVE carries the same consequence.

In short
CVSS scores measure technical severity, not plant consequence. Effective CDA vulnerability prioritization combines exploitability, the asset’s safety and security function, existing compensating controls, and network exposure. Ranking on those factors focuses engineering time on the small set of issues that genuinely change risk.
A single nuclear site can map thousands of published vulnerabilities to its critical digital assets. Treating each one as urgent is impossible; treating them by CVSS alone sends teams after issues that cannot be reached while real exposures wait.
Why isn’t CVSS enough?
CVSS assumes a generic environment. A critical score on a device that sits behind a one-way diode with no removable media access is very different from a moderate score on an engineering workstation used daily.
- CVSS ignores the asset’s role in safety, security and emergency preparedness
- It does not account for existing compensating controls
- It assumes network reachability that may not exist
- It treats every asset of the same model identically
A practical prioritization model
| Factor | Question | Weight |
|---|---|---|
| Consequence | What happens to plant functions if this asset is compromised? | High |
| Exploitability | Is there a known exploit, and how complex is it? | High |
| Exposure | Can an attacker actually reach the vulnerable interface? | Medium |
| Controls | Which compensating controls already mitigate it? | Medium |
Four principles for defensible prioritization
Consequence first
Rank by what the asset does for the plant, not by the score alone.
Document controls
Record compensating controls alongside each risk decision.
Re-rank on change
Configuration or architecture changes should trigger a fresh look.
Explain the order
Every ranking should be explainable to an inspector in one sentence.
What does this look like in practice?
Cyberwiz-Pro correlates offline vulnerability intelligence with each asset’s configuration and role, then proposes a ranked list. Engineers adjust weights, record compensating controls, and approve the final order, all inside the plant boundary.
Five questions to test your prioritization
- Can you explain why your top ten vulnerabilities are in that order?
- Are compensating controls recorded next to each decision?
- Does a configuration change automatically flag affected rankings?
- Do identical devices in different roles get different priorities?
- How long does it take to re-rank after a new advisory?
Spend effort where it changes risk
Good prioritization is not about doing less; it is about making sure the work that gets done is the work that matters most to plant safety and security.
Frequently asked questions
What is a critical digital asset?
A digital system or component that performs or supports safety, security or emergency preparedness functions at a nuclear plant.
How often should vulnerabilities be re-prioritized?
Whenever new vulnerability data is imported or an asset’s configuration changes.
Can prioritization be automated?
It can be proposed automatically, but a qualified engineer should approve the final ranking and rationale.


