Skip to content
Kandaro
Start free trial
← Blog

How to explain a breach to your board

· 4 min read

Security briefings to boards go wrong in one of two ways: too technical (a slide full of CVE numbers and MITRE techniques nobody in the room knows) or too vague (a slide that says "we had an incident and we handled it"). Neither builds the trust you need for the security budget conversation that follows.

What a board actually wants to know

Three questions, in order: What happened? What was the impact? What have you done so it doesn't happen again? Everything else — the CVE number, the specific technique, the forensic timeline — belongs in the appendix, not the deck.

A good answer to "what happened" is one sentence in plain English: "An attacker gained access to a contractor's laptop and spent 40 minutes looking for financial data before our backup server decoy triggered an alert." That is what Kandaro produces automatically. The AI explanation is written for a human who doesn't know what SMB means.

How decoys make the story cleaner

One of the hardest parts of breach disclosure is scope: what did the attacker actually touch? With conventional tools, the answer involves weeks of forensic investigation and is often incomplete. With decoys, you know exactly what was touched (the decoy), what was not touched (because the decoy was found first), and what the attacker was looking for (based on which services they probed).

"They found our decoy backup server before they found our real one" is a better story than "we are still investigating the scope of the breach." It is also a story that explains the value of the investment.

The metric your board will remember

Mean time to detect (MTTD) is the metric security teams use. Boards respond better to a concrete number: "We detected this intrusion 23 minutes after the attacker entered our network." A 23-minute detection time is remarkable. The industry average is measured in weeks. That gap is a story the board will remember when the budget discussion comes around.

Read about Kandaro Deception and how every incident comes with a plain-English explanation, or why honeypots don't cry wolf.