Insights

Notes from practice

Three short pieces on the questions that come up before a company hires security help. No statistics, no predictions — just what the work looks like from this side of the table.

What a customer's security questionnaire is really asking you

The form looks like a test of your security. Most of the time it is a test of whether anyone owns the answer.

The questionnaire arrives from a customer's procurement team, usually after the commercial terms are agreed and usually with a deadline. It runs to eighty questions, half of which do not apply to a company your size. The temptation is to answer it the way you would answer an exam: quickly, optimistically, and in a way that gets the deal moving.

Read the form again and notice what it is for. The buyer is not auditing you. The buyer is collecting evidence that their own auditors, their own customers and their own insurers will accept. They need your answers to be consistent, written down, and defensible by someone in their organization who has never met you. A confident answer that turns out to be wrong is worse for them than an honest gap with a plan attached.

So answer the question that was asked, not the one you wish had been asked. If you do not have multi-factor authentication on every account, do not write that you do. Write what is covered, what is not, and when the rest is planned. The same applies to logging, to encryption at rest, and to the phrase everyone reaches for: 'industry standard'.

Consistency matters more than perfection. Your insurance form, your questionnaire answers and anything on your website should describe the same estate. When a buyer spots two different accounts of your backup arrangements, the deal slows down and the questions get harder.

The last thing is ownership. Someone inside the company has to be the person who can say why an answer was given, and answer a follow-up six months later. If that person does not exist, that is the actual finding — and it is usually the reason an assessment is worth doing before the next questionnaire arrives.

Cyber insurance renewals: the five answers that get flagged

Underwriters read your renewal form as a statement of fact. Five answers draw the most follow-up questions, and they are rarely about the technology.

The renewal form is not a marketing document. It is a declaration, and an incorrect answer can affect a claim years later. These are the five that come back with questions most often.

Multi-factor authentication, claimed too broadly. 'MFA enforced' is flagged when the estate has exceptions: a legacy VPN, a service account, the finance system nobody has touched since it was installed. Underwriters have learned to ask which systems. Answer by system.

Backups described but not restored. 'Nightly backups to a separate location' is a storage answer. The question behind it is whether anyone has restored from those backups and when. If the answer is 'not recently', say so, and make the restore the first item on your list.

An incident response plan with no names in it. A document that says the company will 'activate the incident response team' tells an underwriter nothing. What they want to see is a named person, a route to reach them that does not depend on the office network, and a decision about who talks to customers.

Privileged access 'reviewed regularly'. Regular is not a date. If the review happens, there is a record of it: who held admin rights at the last review, what was removed, when the next one is. If there is no record, the honest answer is that access is granted and rarely removed.

Revenue and loss figures filled in by guesswork. The financial questions are the ones the premium is calculated from, and they are often completed by whoever has the form in front of them. A wrong figure is a problem at claim time, not at renewal time. Get the numbers from finance.

Keep a copy of what you submitted. When the renewal comes round again, the previous declaration is the first thing the next form will be compared against.

You don't need a full-time CISO. You need someone who has done this before

A full-time security leader is the right answer for some companies. For most mid-market firms, the work does not fill the role.

A CISO at a large company runs a department: a budget, a team, a program of work, and a reporting line to the board. That is a full-time job because the organization is large enough to generate full-time work.

At a hundred and fifty people, the same set of responsibilities exists but the volume does not. There is still a strategy to set, risks to own, vendors to review, a board to report to and an incident plan to keep current. In a typical week, that is a few hours of judgment and a lot of waiting. Hiring for it means paying a senior salary for a part-time workload, and then watching a good security leader leave for a company where they can build something.

What the company actually needs is narrower than a job title. Someone who can decide, and be accountable for deciding. Someone who has answered a customer's security questionnaire before and knows which answers create work later. Someone who can sit in front of a board and say 'these are the three things that matter' without a slide deck. Someone to call when something has happened and the first hour decides how the next month goes.

That is what a fractional CISO is: the judgment, bought by the month, without the department. The arrangement only works if the person is genuinely accountable rather than advisory in name. It should be clear which decisions they own, what the reporting cadence is, and what happens when the company needs more than the retainer covers.

There are companies where fractional is the wrong shape: regulated firms with large security teams, organizations running critical infrastructure, or a business where security is the product. Those need a full-time leader, and often a team underneath. Most companies of fifty to five hundred people are not in that group. They need someone who has done this before, for a few days a month, and who will tell them when the arrangement should change.

Book a 30-minute call

If one of these describes your situation, the call is the quickest way to find out what it would take to fix it.

Book a 30-minute call

No deck, no proposal, no follow-up sequence.