Cybersecurity

vCISO Services RFP Template (Free): Fractional CISO

Paste-ready vCISO requirements (scope, named lead, deliverables, independence, handover and pricing), questions that separate providers, and a weighted scoring rubric.

14 pages Microsoft Word Updated November 22, 2026
Download Template
vCISO Services RFP Template (Free): Fractional CISO preview
vCISO Services RFP Template (Free): Fractional CISO

Preview the first pages

See the structure before you download. The Word file has every section listed below, ready to fill in.

What's inside

The sections in the document, in order.

  1. How to run a vCISO RFP
  2. vCISO RFP requirements
  3. Questions to ask vCISO providers
  4. Scoring rubric
  5. Frequently asked questions
  6. Related RFP templates

Use this vCISO RFP template when you're hiring a virtual or fractional CISO: a named, part-time security leader who owns your security program, leads your compliance work and reports on cyber risk to your leadership and board.


You're buying one person's judgment and time, so the template puts the named lead, the first-phase plan and independence from product sales at the center.


It's written for the executive sponsor, IT lead and procurement team running the selection, and it covers when to issue an RFI first, the requirements to send, the questions that separate providers, and how to score the answers.


What's inside this template


  • A step-by-step plan for running the selection, with an example schedule and advice on when a vCISO RFI should come first
  • Requirements for scope, the named lead and team, deliverables and reporting, confidentiality and independence, engagement and handover, and pricing, each marked Must-have or Nice-to-have
  • Questions that test how a provider handles a customer security questionnaire with a deadline, a board risk briefing, a ransomware incident and an MSSP that misses its service levels
  • A weighted scoring rubric that puts the named lead's fit and the first-phase plan first, with a defined scoring scale
  • An editable Word RFP with response codes, a pricing table for the assessment, retainer and extra time, and a timeline

Download the editable Microsoft Word version below. Every requirement, provider question and scoring weight on this page is in the document, ready to tailor and send.

How to run a vCISO RFP

Choosing a vCISO is a hiring decision as much as a purchase: the person you pick will sit with your leadership, see your weaknesses and speak for your security program to customers, auditors and the board. The example schedule in this template runs about nine weeks from kickoff to a signed engagement; allow less for a fixed-scope assessment, and more if your board must approve the engagement.

  1. Write down why you need a vCISO now (weeks 1-2). List what's driving the decision: customer security questionnaires nobody in-house can answer with confidence, an audit or certification date, a request from the board or your cyber insurer, a recent incident, or a CISO who has left. Then record what you have today: who owns security, the size of the IT team, your MSP, MSSP or MDR provider, your auditors, the frameworks you answer to and any audit dates. Providers will scope and price against this, so put it in the background section of the RFP.
  2. Assemble the buying team. Include the executive the vCISO will report to, your IT lead and finance. Add whoever handles customer security reviews today, such as someone in sales or customer success, plus compliance and legal. If the vCISO will brief your board, ask the board or its audit or risk committee what it expects to hear. Keep your MSP informed, but don't make it a decision-maker if it may bid or if the vCISO will oversee its work.
  3. Choose the engagement model, and decide whether you need an RFI (weeks 2-3). Decide whether you want an ongoing retainer, a fixed project such as an assessment and roadmap, an interim CISO while you hire a permanent one, or a fixed first phase followed by a retainer. If that's still open, or your long list is too long to interview, issue a short RFI asking each provider for the named lead's background, the engagement models it offers and any product resale or referral relationships, and use the answers to build a shortlist.
  4. Tailor and issue the RFP (weeks 3-6). Delete requirements that don't apply, adjust priorities, and mark each framework as in scope or not. Ask every provider to price the same scope and the same amount of the named lead's time, so the proposals can be compared. Give providers three weeks to respond, with a written question-and-answer window in the first week.
  5. Score the proposals and build a shortlist (weeks 6-7). Have each evaluator score independently against the rubric before comparing notes, and set aside any provider that misses a Must-have. Check who would really do each task: a strong named lead in the proposal counts for little if most of the work goes to staff you haven't met.
  6. Interview the named leads and check references (weeks 7-8). Interview the proposed vCISO from each shortlisted provider, not only the sales team. Send each the same scenario in advance, such as a customer security questionnaire due within days or a request for a board briefing, and compare how they work through it. Review their redacted sample deliverables, and call references from clients like you that the named lead served directly.
  7. Negotiate and award (weeks 8-9). Write the first-phase deliverables and dates, the named lead and backup, the time included and the rules for extra time into the statement of work. Settle ownership of documents and accounts, the notice period and the handover terms before you sign, and get the disclosure of resale and referral fees in writing.

vCISO RFP requirements

Each line is written to paste straight into your RFP. Must-have means a provider that cannot meet it is out; Nice-to-have earns extra points. Change the priorities to fit your situation, and delete what doesn't apply.

Scope of services

ID Requirement Priority
S1 Leadership of our security program as our CISO for the contract term: setting priorities, owning the security policies and roadmap, and making or recommending decisions within the authority we define. State which decisions the vCISO would expect to make and which they would put to our executives. Must-have
S2 An initial assessment of our security program against a framework we agree, such as NIST CSF [if applicable], covering governance, people, processes and technology, based on interviews with our leadership, IT staff and providers and a review of our current tools, configurations and documents. Must-have
S3 A risk assessment and a risk register that records each risk with a rating, an owner, a treatment decision (reduce, accept, transfer or avoid) and a target date, kept current for the whole engagement and reviewed with our leadership on a schedule we agree. Must-have
S4 A security roadmap ranked by risk reduction, with a budget estimate for each item covering internal effort, tools and outside services, aligned with our budget cycle and updated when priorities change. Must-have
S5 Writing or updating our security policies and standards (for example information security, acceptable use, access control, data classification and handling, incident response, vendor risk, and backup and recovery), mapped to the frameworks in scope, with a scheduled review and approval cycle. Must-have
S6 Leadership of our compliance program for the frameworks that apply to us: SOC 2 [if applicable], ISO/IEC 27001 [if applicable], HIPAA [if applicable], PCI DSS [if applicable], CMMC [if applicable] and NIST CSF [if applicable]. This covers gap assessment, a remediation plan, assigning control owners, evidence collection and coordination with our auditor or assessor. Must-have
S7 Answering, or reviewing our answers to, security questionnaires and audits from customers, prospects and our cyber insurer; building and maintaining a library of approved answers and supporting documents; and joining customer security review calls when we ask. State the turnaround you commit to. Must-have
S8 Oversight of our MSP, MSSP or MDR provider and other security vendors: reviewing their scope, contracts and service-level reports, holding them to their commitments, and running security reviews of new vendors before we sign with them. Must-have
S9 Writing or updating our incident response plan and playbooks, covering roles, decision authority, escalation, contacts for our legal counsel, cyber insurer and outside incident response firm, and our notification duties to regulators, customers and others. Must-have
S10 Tabletop exercises for our executives and for our technical teams, run on a schedule we agree, each followed by a written after-action report with assigned follow-up items. Must-have
S11 A defined role for the vCISO during a security incident, such as coordinating the response, advising executives on decisions, and working with our counsel, insurer and incident response firm. State what the vCISO does not do (for example hands-on forensics) and who does it. Must-have
S12 Oversight of our security awareness program: setting the training plan and phishing simulations, tracking completion and results, and reporting them to leadership. State whether you run the program or oversee whoever does. Must-have

Named lead and team

ID Requirement Priority
L1 The name of the person who will act as our vCISO, with a CV showing the security leadership roles they have held, the industries and company sizes they have served, and the frameworks they have led programs against. Must-have
L2 The named lead is the person we interview and the person who leads the engagement. The provider will not substitute them without our written approval, and if they leave the firm, it will propose a replacement with comparable experience for us to interview. Must-have
L3 Experience leading security programs for organizations in our industry and of our size, with the frameworks in scope, and in presenting to boards or audit committees, supported by references from clients the named lead served directly. Must-have
L4 A list of everyone else who would work on our account (for example analysts, compliance specialists or policy writers), their roles and experience, and a clear split of which tasks the named lead does personally and which others do. Must-have
L5 A named backup who knows our program and covers the named lead's absences, holidays and conflicting commitments, with handovers between them at no extra charge. Must-have
L6 A statement of how many other clients the named lead serves at the same time, and how our time and response commitments are protected when another client has an incident. Must-have

Deliverables and reporting

ID Requirement Priority
D1 A first-phase plan listing each deliverable, its format and its due date, and the date the first phase ends, agreed in the statement of work. Must-have
D2 An assessment report with a short executive summary written for non-technical leaders, and a detailed findings list giving the severity, the evidence and the recommended fix for each finding. Must-have
D3 Written status reports to our executive sponsor on a schedule we agree, covering roadmap progress, changes to the risk register, decisions needed, issues with providers, and time used against the retainer. Must-have
D4 Briefings for our board or its audit or risk committee, prepared and presented by the named lead, covering cyber risk, program progress, incidents and the decisions the board is asked to make, in plain language. Must-have
D5 A set of security measures agreed in the first phase (for example MFA coverage, patching timeliness, open high-rated risks and training completion), tracked over time and tied to the roadmap. Must-have
D6 All deliverables in editable formats, stored in our own document systems, so we keep them whether or not the engagement continues. Must-have
D7 A customer-facing security overview and a standard document pack that our sales team can share with prospects, kept current as the program changes. Nice-to-have

Security, confidentiality and independence

ID Requirement Priority
N1 Confidentiality terms covering everything the provider learns about our security weaknesses, systems and customers, with our data held only on systems we approve and returned or destroyed at the end of the engagement. Must-have
N2 Access to our systems only through accounts we issue to named individuals who have passed background checks in line with our hiring standards, with MFA and the least privilege needed, no shared accounts, and all access removed when the engagement ends or a person leaves the account. Must-have
N3 A description of the provider's own security program, including how it protects client data, keeps each client's information separate and secures staff devices, plus any independent attestation or certification it holds, such as a SOC 2 report or ISO/IEC 27001 certification [if applicable]. Must-have
N4 Disclosure of every security product, service or firm from which the provider or the named lead earns resale margin, referral fees, commissions or partner incentives, and a commitment to disclose any such interest in writing before recommending it to us. Must-have
N5 Disclosure of any ownership, partnership or commercial relationship with our current MSP, MSSP, auditor or other security providers [list them], since the vCISO will oversee their work. Must-have
N6 Product-neutral recommendations: where we need a product or service, the vCISO presents options from different suppliers where they exist, with the reasons for the recommendation and its full cost. Must-have
N7 A statement of whether the provider or an affiliate offers audit, assessment or certification services. The provider will not audit, assess or certify controls it designed or operates for us. Must-have
N8 Professional liability (errors and omissions) and cyber liability insurance with the coverage limits stated, and a commitment to notify us of any security incident at the provider that affects our data within a defined time. State the time. Must-have

Engagement and transition

ID Requirement Priority
E1 The engagement model proposed (ongoing retainer, fixed project, interim CISO, or a fixed first phase followed by a retainer), the initial term, renewal terms, and the notice period for either side to end the engagement. Must-have
E2 An onboarding plan covering kickoff, stakeholder interviews, access requests, document collection and introductions to our MSP, MSSP, auditor and other key providers. Must-have
E3 A working rhythm with regular meetings with our executive sponsor and IT lead, a single channel for requests, and committed response times for routine requests and urgent issues. State the response times. Must-have
E4 A way to reach the named lead or backup outside business hours during a security incident, with a committed response time and a clear statement of how incident time is charged. Must-have
E5 On-site attendance when we need it, such as board meetings, tabletop exercises and audits at [locations], with travel agreed in advance. Nice-to-have
E6 Ownership by us of all documents, policies, registers, reports and other work produced for us, with a lasting license for our internal use of any provider templates they are built on. Any compliance tool or document workspace used for our program is licensed in our name, or our data in it can be exported in full in a standard format at any time. Must-have
E7 A handover at the end of the engagement to our new CISO or another provider: an index of documents, open risks and actions, projects in progress, provider contacts, and a list of the access the provider held, with a handover period. State its length and cost. Must-have
E8 Help hiring a full-time CISO or security staff when we're ready: drafting the role, joining interviews and planning the handover to the new hire. Nice-to-have

Commercial and pricing

ID Requirement Priority
C1 A fixed fee for the initial assessment, risk register and roadmap, stating what's included and what would change the fee. Must-have
C2 A monthly retainer that states how much of the named lead's time is included, and how that time is measured and reported to us. Must-have
C3 Hourly or daily rates for the named lead and each other role for work beyond the retainer, with no extra time billed unless we approve it in writing first. Must-have
C4 Rules for unused retainer time (whether it carries over, and for how long), for time above the retainer during busy periods such as an audit or an incident, and for changing the retainer level with notice. Must-have
C5 Separate prices for optional services, such as on-call incident availability, audit preparation, tabletop exercises, policy development and running the awareness program. Must-have
C6 A cap on rate increases at renewal. State the cap. Must-have
C7 Termination for convenience by either side with written notice, with fees limited to work done and the agreed handover period, and no termination penalty. Must-have

Questions to ask vCISO providers

These questions are designed to separate providers, not to collect brochure answers. Ask for evidence: a sample deliverable, an interview with the named lead or a reference.

  1. We'd like to interview the person you propose as our vCISO, without the sales team present. What would they want to learn about us in their first weeks, and what would they expect to change first?
  2. Send redacted samples of an assessment report, a risk register, a security roadmap and a board briefing that the named lead produced for a client like us. Which parts would look different for us, and why?
  3. Lay out your first-phase plan for us: the interviews, the framework you would assess against and why, and each deliverable with its date. What do you need from our team to meet those dates?
  4. A major prospect sends a long security questionnaire due at the end of next week, and several questions cover controls we don't have yet. Walk us through how you would answer it, who on your team does the work, how you handle questions where the honest answer is no, and how the gaps it reveals reach the roadmap.
  5. Our board asks for a cyber risk briefing at its next meeting. Show us the briefing you would prepare after the first phase: the format, the measures you would report and the decisions you would ask the board to make.
  6. Late one evening, our MSP reports ransomware on several servers. Describe the first hours: who you call, which decisions you put to our executives, how you work with our legal counsel, cyber insurer and incident response firm, and what you leave to others.
  7. Our MSSP has missed its response-time commitments on several alerts this quarter. How would you find out, what evidence would you gather, and how would you raise it with the provider and with our leadership?
  8. We face [an upcoming audit or assessment for SOC 2, ISO/IEC 27001, HIPAA, PCI DSS or CMMC] [if applicable]. How would you scope it, sequence the work alongside the rest of the roadmap, and divide the work between you, our IT team, our MSP and the auditor?
  9. If our budget covers only part of the roadmap you recommend, how do you decide what to fund first, and how do you explain the remaining risk to our leadership?
  10. List every product, service or firm you resell, partner with or earn referral fees from, and any relationship with our current MSP, MSSP or auditor. Describe a recommendation where you had a financial interest and how you handled it.
  11. How many clients does the named lead serve today? What happens to our work when several clients have incidents in the same week?
  12. Tell us about a time the named lead had to tell a client's leadership that a planned launch or deadline carried a security risk they were not prepared to accept. What happened next?
  13. If the named lead leaves your firm or is unavailable for an extended period, who takes over, how quickly, and how do they get up to speed on our program?
  14. Provide a reference from a client of similar size and industry that the named lead served directly, and one from an engagement that has ended. What did the handover look like?

Scoring rubric

Score each criterion from 1 to 5, multiply by its weight, and add the results. The weights below are a starting point; agree on your own before any proposals arrive so the scoring can't be bent around a favorite.

Criterion Weight What a strong response shows
Named lead's fit and experience 25% Security leadership experience in your industry, at your size and with your frameworks, a strong interview without the sales team, and references from clients the named lead served directly.
Quality of the first-phase plan 20% Specific, dated deliverables, a sensible choice of framework, a clear list of what's needed from your team, and sample deliverables that show what you'll receive.
Judgment in the scenarios 15% Practical, honest answers to the questionnaire, board, incident and MSSP scenarios, with clear priorities and a realistic view of the vCISO's role.
Reporting and communication 10% Status reports and board briefings in plain language that you would be comfortable putting in front of your board, with measures tied to the roadmap.
Independence and conflicts 10% Full written disclosure of resale, referral and partner fees and of relationships with your providers, product-neutral recommendations, and separation from audit work.
Engagement terms and handover 10% A named backup, clear response times, your ownership of documents and accounts, a reasonable notice period and a credible handover plan.
Commercials and value 10% Clear pricing for the first phase and the retainer, a defined amount of the named lead's time, fair rules for extra and unused time, and a transparent rate card.
Total 100%

Scoring scale

  • 5 Exceeds: meets every Must-have and most Nice-to-haves, shown through an interview with the named lead, sample deliverables and a matching reference client.
  • 4 Strong: meets every Must-have and some Nice-to-haves, with clear evidence.
  • 3 Adequate: meets most Must-haves; gaps have a credible plan.
  • 2 Weak: misses one or more Must-haves, or the answer is vague.
  • 1 Poor: does not meet the requirement, or no answer.

Frequently asked questions

What should a vCISO RFP include?

Your background and what's driving the need; the scope of services, from risk assessment and roadmap to compliance, provider oversight, customer questionnaires, incident response planning and board reporting; requirements for the named lead and team, deliverables, confidentiality and independence, each marked Must-have or Nice-to-have; questions and scenarios that show how each provider works; engagement, handover and pricing terms; and the rubric you'll score with. This template includes all of them.

How much does a vCISO cost?

Price depends on scope, so the only useful comparison is between proposals priced against the same scope. The main cost drivers are how much of the named lead's time you need each month, how many frameworks and audits are in scope and how soon they fall due, how regulated your industry is, the size and complexity of your environment, whether the vCISO must be on call for incidents, and whether any work must happen on site. Compare the fixed first-phase fee, the retainer and the rates for extra time separately in the pricing table.

vCISO or MSSP: what's the difference?

An MSSP (managed security service provider) runs security operations for you, such as monitoring alerts and managing security tools, under a service contract. A vCISO is a security leader who sets priorities, owns the security program and its policies, reports to your leadership, and decides what you need from providers such as an MSSP. The roles complement each other: a vCISO can oversee an MSSP's work and hold it to its service levels. If a firm offers both, ask how its vCISO stays independent when reviewing a colleague's service.

Do we need a vCISO for SOC 2?

Not by title: SOC 2 doesn't require a CISO or a vCISO. It does expect clear responsibility for security, and controls that are designed, operating and backed by evidence the auditor can test, which is hard to achieve without someone who owns the program. A vCISO can lead the readiness work: scoping the report, writing policies, assigning control owners, collecting evidence and working with the auditor. Keep the roles separate, because the CPA firm that examines your controls must be independent of them and shouldn't be the firm that designed them.

Related RFP templates

Download Template

More cybersecurity templates