The CISO POST All field notes
Leadership · FIELD MEMO 024

How do you hire the right vCISO?

The questions founders should ask to distinguish practical security leadership from a borrowed title, a policy pack, or another advisory retainer.

Hiring a vCISO is difficult because almost every candidate can talk about risk, compliance, and best practice. The useful distinction appears when the conversation reaches your business: which decisions they will own, what your team must execute, how they will handle competing priorities, and what should improve because they are there.

Begin with the problem, not the title

Before interviewing anyone, write down why you think you need a vCISO.

Are enterprise deals slowing down? Is the company moving from SOC 2 into several overlapping obligations? Are founders receiving security decisions they do not know how to evaluate? Is work spread across engineering, legal, IT, and sales without one person holding it together?

These are leadership problems. A vCISO may be the right answer.

If the immediate problem is a backlog of cloud hardening, endpoint deployment, vulnerability remediation, evidence collection, or alert investigation, the company may need an experienced operator instead. Hiring leadership when the gap is execution creates good recommendations and a larger queue.

Be precise about the problem before a candidate explains the service they want to sell.

The hiring testDo not hire the person who sounds most like a CISO. Hire the person who can make security decisions work inside your company.

Ask how they would learn your business

A strong candidate should be curious before being prescriptive.

Ask how they would learn what the company sells, which customers and markets matter, what data the product handles, how the technology works, and which promises have already been made. Listen for the people they would involve and the evidence they would examine.

Be cautious when the answer begins with a standard assessment, a fixed policy library, or a framework chosen before the candidate understands the company.

Frameworks can organise work. They do not decide which risk could stop a deal, interrupt the product, expose customer data, or create a commitment the company cannot keep. The vCISO should be able to connect security choices to those outcomes.

Ask what they will own

The phrase “own security” is too vague to put in an agreement.

Ask the candidate:

A useful answer separates leadership, coordination, implementation, and assurance.

The vCISO may own the risk view, priorities, leadership advice, and programme design. Engineering and IT will still operate many controls. Legal or privacy specialists may need to interpret particular obligations. An auditor must remain independent of the work being audited. Founders still decide when cost, speed, customer commitments, and risk conflict.

If everything is supposedly included, ownership is probably not clear enough.

  • Which decisions and deliverables will you personally own?
  • What must our internal team and founders continue to own?
  • Who keeps the work moving between sessions, and when would you bring in a specialist?

Give them a real decision to work through

Do not spend the entire interview discussing credentials and previous clients. Use a problem the company is currently facing.

For example:

Ask the candidate how they would frame the decision, who should be involved, what they would need to verify, and how they would document the outcome.

Strong answers make uncertainty visible. They distinguish facts from assumptions, explain tradeoffs in plain language, and identify who has authority to decide. Weak answers jump straight to a control, cite a framework without context, or promise that the vCISO will make the problem disappear.

  • A strategic customer wants a control that is not on the roadmap.
  • The company promised a remediation date that engineering will miss.
  • A new AI feature needs access to customer information.
  • SOC 2 work is competing with a material product-security weakness.
  • Leadership wants to accept a risk, but nobody has defined the exposure.

Ask how they will work with customers without overpromising

Many growing companies hire a vCISO partly because enterprise customers want credible security answers. That is reasonable. It also creates a risk that the adviser becomes a reassuring voice on sales calls while the operating reality stays unchanged.

Ask how the candidate will review questionnaires, security schedules, remediation promises, and customer-specific commitments. A good answer should connect every material claim to a real control, an owner, and evidence.

The vCISO should be willing to say when an answer is not yet true. They should also help the company present limitations honestly, offer a credible plan, and avoid turning one deal into an obligation the wider business cannot sustain.

Agree on how the engagement should become less dependent

A vCISO should not become permanent infrastructure by accident.

Before signing, agree on what should be different after six months. The company might expect a clearer risk picture, one prioritised roadmap, named internal owners, a regular decision rhythm, more defensible customer answers, and a plan for the next security hires.

Also agree on the conditions that would change the model. The company may eventually need a full-time leader when security decisions and team management become continuous. It may need an internal security lead while retaining the vCISO for periodic advice. It may need to end the engagement once the operating system is established.

The right vCISO will be comfortable discussing that transition. Their value should be visible in the company’s ability to make better decisions, not in how difficult they are to replace.

The founder’s final check

Before choosing a candidate, ask yourself:

If those answers are clear, the engagement has a reasonable chance of becoming security leadership rather than another collection of recommendations.

  • Do they understand what the business is trying to achieve?
  • Can they explain difficult security choices without hiding behind jargon?
  • Is it clear what they own and what we must do?
  • Will they challenge promises the company cannot support?
  • Are they building internal capability as well as providing advice?
The right vCISO brings clarity, judgment, and a working operating rhythm. They should make the company more capable, not more dependent on the next advisory call.
FIELD MEMO 024

Useful now, not someday.