Critical, High and Low only help when everyone agrees what they cost. Most board packs use the labels and never define them, so every number starts an argument.
A scoring tool will happily give you a 9.8 for something on a test server nobody uses. A board cannot act on that. It needs to know what breaks, for whom, and by when, and it needs that answer in the same words every quarter.
Define them in business terms
Replace technical scoring with one line about impact. A board should be able to read the label and know what it means for the week ahead.
- Critical: stops the business or exposes client data today.
- High: could do that within a month if left alone.
- Low: worth fixing, nothing breaks if it waits.
If the board asks what Critical means, the label has failed.
Three levels are enough
We stopped at three on purpose. Add a fourth and every debate moves to the line between Medium and High. With three, the question stays simple: does this hurt us today, soon, or not really?
Write each label down once, put it on the first page of the report, and agree it with the people who will read it. When someone wants to change a finding’s severity, the definition settles it.
Keep the count honest
Report the same three counts every quarter, with the same definitions. A falling Critical count means something only if the label has not quietly changed.
- Show opened, closed and still open, not just the total.
- Give each Critical and High a named owner and a date.
- Say when a finding moved between levels, and why.
Some of the best board conversations come from a number that went up. If you looked harder this quarter, say so. A board that trusts the count will fund the fix.




