DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

Three Numbers for One Board Slide

By Deepak Kumar, CISSP

The problem: The CISO builds the quarterly board report from numbers sent by three sub-teams. The slide says “critical vulnerabilities.” The vulnerability team counts anything scored 9 or more. The SOC counts those on systems open to the internet. Compliance counts those older than 30 days. The three numbers differ, and the CISO finds out in the board meeting.

Words used here: a vulnerability is a weakness in software that an attacker could use. Critical is a rating for the most serious ones. The vulnerability team finds and tracks weaknesses. The SOC watches alerts and deals with attacks. The board is the group of senior people who oversee the company.

Think of two rulers

A carpenter measures a table with his hands and says, “Ten hands wide.” The customer measures it in inches and says, “Forty inches.” Both are telling the truth. Put the two numbers side by side on a quote and the customer thinks the carpenter has made a mistake.

The table did not change. Only the ruler did. A single word like “critical” can be a different ruler in each team.

Two rulers, one table
One table: ten hands, or forty inches
Ten hands wide.
Carpenter
Forty inches. Which is it?
Customer
Both are true. The ruler is different.

What it looks like at work

The vulnerability lead writes “42 critical” because her scanner uses a score of 9 and above. The SOC lead writes “17 critical” because he counts only those on systems the internet can reach. The compliance lead writes “9 critical” because the policy says a weakness is serious once it is older than 30 days. These are example numbers.

The CISO puts the three side by side, hoping they will agree. They do not. He picks one and writes “critical vulnerabilities” on the slide. In the meeting, a board member who also sits on an audit committee says, “Last quarter you told us a different number. Which is right?”

How three meanings reach one slide
  1. 11. Vulnerability team“42 critical”: score of 9 or more
  2. 22. SOC“17 critical”: open to the internet
  3. 33. Compliance“9 critical”: older than 30 days
  4. 44. One slideThe CISO picks one and writes “critical”
  5. 55. Board asks“Last quarter it was different. Which?”
Three real answers to three different questions.

All three leads are right by their own rule. The vulnerability lead knows the technical score. The SOC lead knows which systems an attacker can reach. The compliance lead knows which weaknesses have broken a deadline. They are each answering a real question. The board simply asked a different one, and nobody noticed.

You will notice it when:

  • The same word appears in two reports with two different numbers.
  • A sub-team says “that is not how we count it.”
  • The CISO adds a footnote to every figure to explain it.
  • Last quarter’s figures cannot be reproduced the same way.
  • Board members ask “which number do we trust?”

What exactly needs fixing

The fix is not to choose the biggest or smallest number. It is to agree what “critical” means, once, and then count from one list. This card shows the whole problem on one page:

Three numbers for one word
WHAT IS BROKEN

The word “critical” means three different things, so the board report shows three different numbers.

MEDIUM
WHERE IT IS

The quarterly board report, and the three sub-teams’ tools.

WHAT COULD GO WRONG

The board makes a risk decision using a number nobody can reproduce.

WHAT IT COSTS US
  • Board loses trust
  • Days of rework
  • No stable baseline
  • CISO’s standing
THE FIX, IN THREE MOVES
  1. 1
    1. Define the wordsFive or six words, one line each, agreed in an hour
  2. 2
    2. One shared listEvery lead counts from the same list, not their own tool
  3. 3
    3. Check togetherLeads read each other’s numbers a week before the board
WHO FIXES IT

Who fixes it: the CISO with the three sub-team leads

BY WHEN

By when: before the next board report

A blank copy of this card is in the Tools section.

Why it happens

  • Each team defined the word for its own work. Nobody wrote a shared definition.
  • Each team uses its own tool. Their lists do not match.
  • The report is built in a hurry. Numbers are pasted in without being checked against each other.
  • Nobody owns the definitions. The CISO assumes they are the same.
  • A different number is easier to defend than a shared one. Each lead can explain their own.

What happens if you ignore it

The board stops trusting the numbers, and then the report.

  • The CISO has to explain a mismatch in front of the board, not before it.
  • Real progress cannot be shown, because the baseline keeps moving.
  • The team spends days reworking the report each quarter.
  • The sub-teams start defending their own number instead of the shared goal.

At a glance

QuestionAnswer
How likely is it to hurt us?Very likely, wherever several teams feed one report.
Worst case?The board makes a risk decision using a number nobody can reproduce.
What does it cost?Trust in the report, days of rework, and the CISO’s standing.
What if we wait?The next report has the same three numbers.
What does the fix cost?A one-page definition and a shared list.

How to fix it, step by step

Define the words, count from one list, then check together.

  1. Pick the five or six words that appear in every report. Critical, open, overdue, fixed, covered, in scope.
  2. Write one line for each. What it means, who counts it, and from which list.
  3. Meet for an hour with the sub-team leads. Agree the wording. Where teams disagree, the CISO decides.
  4. Build one shared list. One place that holds the data every number is counted from.
  5. Count once, from that list. Each lead takes their figure from it, not from their own tool.
  6. Review the draft together a week before the board. Leads read each other’s numbers.
  7. Keep the definitions page with the report. Anyone who reads the number can see what it means.
Define, one list, check together
1. DefineOne line for each word the report uses.
2. One listEvery number is counted from the same data.
3. Check togetherLeads read each other’s figures before the board.
The definition is the cheap part, and it fixes most of the problem.

The picture shows the order: define, count from one list, then check together. The definition is the cheap part, and it fixes most of the problem.

Who to bring in: The CISO (owns the definitions), the leads of the vulnerability team, the SOC, and compliance (agree and use them), and one analyst who builds the shared list.

Tools and templates

Definitions page

WordOur meaningCounted byFrom which list
CriticalScore 9 or more, on a system the internet can reachVulnerability leadShared vulnerability list
OverdueOpen longer than the fix time for its ratingCompliance leadShared vulnerability list
FixedPatch applied and re-scanned cleanVulnerability leadShared vulnerability list

Blank finding card

FieldWrite here
What is brokenOne line, in plain words
Where it isThe system, team, or process
What could go wrongIn one sentence
What it costs usMoney, time, a failed audit, lost trust
The fixThe exact action
Who fixes itOne name or one team
By whenA date, not “soon”

Email to start the talk

Subject: One meaning for “critical” in the board report

Hi all. In preparing the board report I found we each count “critical” differently, and I got three different numbers. I would like us to agree one meaning and count from one list. Can we meet for an hour this week? Please bring how your team counts it today. I am not looking for who is right. I am looking for one number we can all explain.

Field tip

Before you put a number on a slide, write one line under it: what it counts, and where it came from. If you cannot write the line, the number is not ready.

Words used in this chapter

  • Vulnerability: a weakness in software that an attacker could use.
  • Critical: the rating for the most serious weaknesses.
  • SOC: the security operations team that watches alerts and deals with attacks.
  • CISO: the chief information security officer, the head of security.
  • Board: the senior group that oversees the company.
  • Baseline: the starting figure that progress is measured from.