The problem: The CISO (head of security) reports to the CIO (head of IT). A penetration test finds that a group of old servers, owned by the CIO’s own team, are not patched. The CISO rates this High in the draft board report. The CIO asks, kindly, “Can we make that Medium this time? My budget is already stretched.” The CISO has to decide between a boss and an honest report.
Words used here: the CISO is the head of security. The CIO is the head of IT. A penetration (pen) test is a planned attempt to break in, done by an expert. The board is the senior group that oversees the company. Rating means how serious a risk is judged to be.
Think of an inspector paid by the builder
A building inspector finds a beam that is not safe. The builder, who pays the inspector’s fee, says, “Could you write ‘fine’ for now? I will fix it next month.” The builder is not a bad person. He has a deadline and a tight budget. But if the inspector writes ‘fine’, the next person to walk under the beam has no idea.
The CISO is the inspector. The CIO is the builder. The report is only useful if the writer is free to say what they see.
What it looks like at work
The pen test report says 14 old servers run software that no longer gets updates. These are example numbers. The CISO scores the risk High, using the rule in the security policy. The CIO reads the draft and sees that High means a loud conversation at the board and a request for money he does not have this year.
He asks for Medium. The CISO changes the word, not because the facts changed, but because the CIO writes his review. Six months later one of those servers is used in an attack. A board member says, “You told us Medium.”
- 11. Pen test14 old servers no longer updated
- 22. Rated HighBy the rule in the policy
- 33. CIO asks“Can we make it Medium this time?”
- 44. Word changedThe facts did not change, the boss did
- 55. Attack“You told us Medium.”
Both people have a fair point. The CIO is balancing many demands with limited money, and he has a plan to replace the servers next year. The CISO is paid to give an honest picture, and a softened report is not honest. Neither of them wants the company hurt. The structure puts them in a corner.
You will notice it when:
- A rating changes between drafts and the facts have not.
- The CISO “checks with” the owner of the system before sending a report.
- Risks pointing at the CIO’s own area are always rated lower.
- The CISO has no direct contact with the board or the audit committee.
- The report uses words like “managed” and “in hand” with no dates.
What exactly needs fixing
The fix is not a quarrel with the CIO. It is a rule, agreed in advance, that decides ratings by criteria and not by who owns the system. This card shows the whole problem on one page:
A High risk on the CIO’s own old servers was softened to Medium at the CIO’s request.
The board report, and the CISO’s reporting line to the CIO.
A known risk is rated low, then used in an attack.
- Wrong board picture
- CISO’s name on a bad report
- Awkward post-incident review
- Good people leave
- 11. Write the ruleOne page: ratings follow the facts, not the owner
- 22. Add the owner’s planA fix date, an owner and the money needed, beside the rating
- 33. Open a direct lineThe CISO meets the audit committee chair twice a year
Who fixes it: CISO and CIO, signed by the CEO
By when: rule agreed before the next report
A blank copy of this card is in the Tools section.
Why it happens
- The reporting line creates the pressure. The CISO’s boss owns many of the risks.
- Ratings are a judgement, not a number. Judgement can be nudged.
- There is no written rule for how ratings are set. So each one is a fresh debate.
- The owner has no place to show his plan. A High with no plan looks like blame.
- The CISO has no other route to the board. The only path goes through the CIO.
What happens if you ignore it
The board plans from a picture that is quietly too soft.
- Money goes to risks that look big and not to the ones that are.
- The CISO’s name is on a report that later proves wrong.
- After an incident, the report becomes evidence that the risk was known.
- Good security people leave a place where they cannot say what they see.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Likely, wherever the CISO reports to someone who owns risks. |
| Worst case? | A known risk is rated low, then used in an attack. |
| What does it cost? | A wrong board picture, a damaged CISO, and an awkward post-incident review. |
| What if we wait? | The next report is softened too. |
| What does the fix cost? | One page of rules and two meetings a year. |
How to fix it, step by step
Write the rule, show the owner’s plan beside the rating, then open a direct line.
- Write the rating rule. For example: High means a known weakness that an attacker can use, on a system that matters. Put it in one page.
- Agree it with the CIO first. Do this when no report is at stake, so it is a rule and not a ruling.
- Rate by the rule, not by the owner. Ask only: do the facts match the criteria?
- Add the owner’s plan beside the rating. A fix date, who does it, and what money is needed.
- Let the CIO comment, not edit. His note goes in the report in his own words.
- Open a direct line. The CISO meets the audit committee chair twice a year, with the CIO welcome to attend.
- Ask the CEO to sign the rule. So both the CISO and the CIO are protected by it.
The picture shows the order: write the rule, show the owner’s plan beside the rating, then open a direct line. Step two is what makes the High acceptable to the owner, because it shows he has a plan.
Who to bring in: The CISO (writes the rule), the CIO (agrees it and adds his plans), the CEO (signs it), and the audit committee chair (receives the report).
Tools and templates
Rating rule
| Rating | Meaning | Who may change it |
|---|---|---|
| High | Known weakness, attacker can use it, system matters | Only by new facts, agreed in writing |
| Medium | Weakness exists, attacker needs more steps or access | Only by new facts |
| Low | Weakness exists, little harm if used | Only by new facts |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a failed audit, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to start the talk
Subject: Agreeing how we rate risks in the board report
Hi. I know the old servers item is awkward for your team, and I want to find a way that is fair to you. I would like us to agree a one-page rule for how risks are rated, so the rating depends on the facts and not on who owns the system. Your plan and dates would go right beside it. Can we meet for 30 minutes this week? I am not looking to blame anyone. I am looking for a report we can both stand behind.
Field tip
When someone asks you to change a rating, ask one question: “What new fact has changed?” If there is none, the rating stays, and their plan goes beside it.
Words used in this chapter
- CISO: the chief information security officer, the head of security.
- CIO: the chief information officer, the head of IT.
- Pen test: a planned attempt to break in, done by an expert.
- Board: the senior group that oversees the company.
- Rating: how serious a risk is judged to be.
- Audit committee: the board group that checks reports are honest.