Every security leader gets asked it, usually near the end of a meeting, usually by the director who has read the least of the pack. "So, are we secure?"

Yes is wrong, because it is a guarantee nobody can give and it will be quoted back after the next incident. No is wrong, because it invites the follow-up "then what have we been paying for?" and it is not true in any useful sense either. Hedging with "security is a journey" is worse than both, because it sounds like you do not know.

What the question is really asking

A director asking "are we secure?" is almost never asking for a technical assessment. They are asking one of three things:

  • Are we inside the limit we agreed? Is the risk the business is carrying the amount the board thinks it approved?
  • Would I hear about it if we were not? Is there a path by which bad news reaches the board before it reaches the press?
  • Is the money working? Is spend moving the risk, or just maintaining it?

All three are answerable. None of them is answered by yes or no.

The three-sentence answer

Practise this until it comes out without notes.

  1. Position: "We are inside the risk appetite the committee approved on most of our top risks, and outside it on two."
  2. The exceptions: "The two are ransomware recovery time for our order system and third-party access to customer data. Both have owners, plans, and dates in the report."
  3. The ask or the assurance: "Bringing recovery inside tolerance needs the funding we will ask for next quarter. Third-party access will be back inside by March without new money."

That answer does four things a yes cannot. It refers to a limit the board itself set. It names what is wrong, which is what makes the rest credible. It shows that each problem is owned. And it ends with either a decision or a date.

It only works if a risk appetite exists. NIST CSF 2.0 makes risk appetite and tolerance statements a Govern outcome, and the UK Cyber Governance Code of Practice asks boards to define and communicate a cyber risk appetite. If yours has none, the honest answer is: "We have not agreed what secure enough means for us. I would like to bring a proposal to the next meeting." That is a strong answer, because it gives the board a job only the board can do.

The follow-ups, and how to answer them

"Could what happened to them happen to us?" Asked after a peer incident. Answer with the specific control that failed for them, whether you have it, and how you know. "Their attackers came in through a help desk password reset. Our resets for privileged accounts require a manager callback, and we tested that in September." If you do not know yet, say when you will. Never answer a peer incident from memory in the room.

"What is our biggest risk?" Name one, from the register, in one sentence, with its status. Picking one is the point; listing five sounds like none are prioritized.

"Are we spending enough?" Benchmarks help as context only. The IANS Research and Artico Search budget benchmark puts security at 10.9% of IT spend, down from 11.9%, across 587 CISOs. Say that, then say whether your own spend is moving the risks outside tolerance, which is the question that matters. The budget conversation in full is a separate piece on this desk.

"Would we know if we had been breached?" The honest answer is about coverage and time. "For our cloud estate and corporate endpoints, yes, and our detection target is hours. For the acquired business we are still integrating, not yet, and that is one of the two risks outside tolerance."

What not to say

Avoid statements a director could later read as a promise. "We are fully protected" and "that could not happen here" are the two that age worst. Avoid citing attack volume as evidence of anything; a board that hears "we blocked a million attacks" learns nothing about whether the one that got through was stopped.

Avoid answering for areas you do not own. If the question is about a subsidiary or a product line outside your remit, say who owns it and offer to bring them.

And avoid answering a different question from the one asked. A director who hears a ten-minute tour of the control framework in response to a one-line question concludes either that the answer is no, or that you do not know it. Give the three sentences first. Offer the detail after, and let the director decide whether they want it. Most will not, and the ones who do will ask better questions because the frame is already in their head.

Why this matters beyond the room

For US public companies, Regulation S-K Item 106(c) requires the annual filing to describe how the board oversees cyber risk and how it is informed. The answers given in board meetings are part of the record of that oversight. An answer framed against an agreed appetite, with named exceptions, reads well later. A reassurance with no basis does not.

Next steps

  1. Write your three-sentence answer for this quarter, and test it on the committee chair before the meeting.
  2. If there is no risk appetite statement, draft one; it is the precondition for every answer above.
  3. Build the quarterly report around the same structure: see the quarterly board cyber report.
  4. For the budget follow-up, see a security budget a CFO cannot cut and the security share of IT budget card.
  5. Keep the numbers behind your answer on one page with the board cyber metrics one-pager template.