Guide

Fractional CISO Scope of Work Template

A useful fractional CISO scope of work turns a broad promise of security leadership into an agreed mandate: which decisions the leader supports, which outputs will be accepted, who implements the work, and what happens when priorities change. Copy the table below into your proposal review and fill it out with the provider and your internal sponsor.

By Nick Shevelyov 8 min read

If you are using this template to procure leadership, start with vCSO.ai’s fractional CISO scope. Put the reporting cadence, executive decisions and implementation owners side by side with the terms in your draft.

What a fractional CISO scope of work should do

A fractional CISO scope of work should make the leadership arrangement testable. It should state the problem the engagement is meant to solve, the evidence available at the start, the decisions the fractional leader may make or recommend, the work the client retains, and how both sides will know a deliverable is complete.

That clarity matters because “provide CISO leadership” can describe very different arrangements. One company may need an independent baseline and a board-ready plan. Another may need temporary leadership during a vacancy. A third may already have findings and need someone to coordinate priorities. The written scope should distinguish those needs instead of treating the title as the scope.

NIST Cybersecurity Framework 2.0 includes organizational roles, responsibilities, and authorities in its Govern function. This template adapts that governance principle for a fractional leadership engagement. It is not NIST-required language, a certification requirement, or legal advice.

If you are still selecting a provider, first use the fractional CISO hiring guide to interview the named lead and review work samples. Use this template once you have decided to seek fractional leadership and need to compare proposed scopes.

Copyable fractional CISO scope of work template

Copy the table into a document or spreadsheet. Replace role labels with named people before the engagement starts.

Scope element Questions to resolve Agreed term
Mandate and business outcome What must be different at the end of the engagement? Which business decision, customer requirement, leadership gap, or risk priority created the need? [State the outcome and what is out of scope]
Baseline and starting evidence Which assessments, policies, risk records, architecture records, audit reports, incidents, and work plans can the provider rely on? Which evidence is missing, stale, sampled, or unverified? [List sources, dates, limitations, and evidence owners]
Decisions and approver Which decisions may the fractional CISO make, which may they recommend, and which require approval by the sponsor, board, legal, finance, or a system owner? [Decision / recommender / approver / record location]
Capacity and coverage Which planned meetings, review work, and response windows are included? What is the coverage for urgent questions and after-hours events? Who is the backup? [Cadence, availability, exclusions, backup, response route]
Deliverables and acceptance What will be delivered, by whom, in what format, and by when? What review, correction, evidence, or approval makes each item accepted? [Deliverable / owner / acceptance evidence / approver]
Implementation boundary Who changes systems, policies, configurations, vendor contracts, or operating processes? Which specialist services require separate scope? [Advisory work / client work / separately scoped work]
Cadence and working model Who attends executive reviews and working sessions? Where are decisions, actions, evidence requests, and unresolved questions tracked? [Meetings, participants, tracker, communication route]
Escalation What conditions require escalation? Who receives an operational, legal, customer, financial, or board escalation? [Trigger / primary / backup / expected response]
Change control Who may request a scope change? How are urgency, dependencies, tradeoffs, added capacity, and approval recorded before work begins? [Request route / impact review / approver]
Exit and handoff What records, open decisions, access ownership, vendor contacts, and knowledge transfer must be handed over? What ends the engagement? [Handoff package / recipient / acceptance / end condition]

A proposal does not need to predict every future issue. It does need a way to decide whether a new issue fits the mandate. When it does not, change control should force an explicit choice: reprioritize existing work, add scope, engage a specialist, or leave the work with the client.

Define decision rights, not just responsibilities

A list of responsibilities can still leave authority ambiguous. For each recurring decision, identify four roles:

  • Recommender: analyzes the evidence and proposes a choice.
  • Approver: has organizational authority to accept the choice and its consequences.
  • Implementer: changes the system, process, contract, or record.
  • Verifier: checks that the approved action produced the intended result.

The same person can fill more than one role when policy permits it, but do not assume the fractional CISO is automatically the executive of record, control owner, implementer, or signer. Those rights depend on the written engagement and the company’s own governance. The virtual CISO responsibilities guide shows how leadership, sponsor, and implementation responsibilities can be divided.

Example scope row with change control

The example below is fictional. It shows how a broad promise can become an accountable row without pretending the provider controls every dependency.

Field Fictional example
Mandate Give the executive team a verified view of privileged production access and a prioritized decision plan.
Starting evidence Current identity-provider export, cloud role listings, access-review procedure, and the last completed review. Service-account ownership is incomplete and remains an evidence gap.
Included work Review the agreed listings, interview the identity and platform owners, document findings and limitations, recommend priorities, and present decisions in the monthly executive review.
Client-owned work Approve access changes, make configuration changes, notify affected users, and retain change records.
Deliverable and acceptance Privileged-access finding set and prioritized action plan. Accepted when the platform owner confirms factual accuracy, open coverage is recorded, and the sponsor approves the priorities.
Coverage Planned working sessions and the agreed escalation route during business hours. Incident command and after-hours response are not included.
Change control Reviewing customer-support access is a new request. The sponsor and fractional CISO first decide whether it replaces lower-priority work or requires a separate scope. No review begins until scope, evidence owner, and acceptance criteria are recorded.
Handoff Current findings, evidence references, decisions, open actions, owners, and next review dates transfer to the internal security lead.

Set acceptance criteria for every deliverable

A deliverable name is not an acceptance test. “Board report,” “roadmap,” or “risk register” says little about quality or completion. Pair each output with evidence and a decision.

For example, a roadmap might be accepted when:

  1. each priority traces to a reviewed finding or stated business requirement;
  2. the responsible client owner has confirmed the dependency and proposed sequence;
  3. open evidence and assumptions are visible rather than presented as facts;
  4. leadership decisions have a named approver and review date; and
  5. implementation tasks are separated from advisory recommendations.

Acceptance does not mean every recommended action has been implemented. It means the agreed output is accurate enough for its intended decision and its remaining limits are understood.

Write coverage and escalation terms plainly

Do not infer emergency coverage from a senior title. State whether the engagement includes incident-readiness review, on-call advice, incident command, customer communications, regulator communications, or none of those. Name the primary route and a backup. If specialist counsel, forensics, penetration testing, or managed detection may be needed, say who can engage them and whether their work is separately scoped.

During a leadership transition, pair the scope with the CISO departure checklist so company-controlled records, active incidents, expiring exceptions, and external commitments have owners.

Review the scope before signing

Ask the sponsor, named fractional lead, and affected technical owners to review the completed table together. Then test it with three scenarios:

  • A material finding needs a funding decision. Who recommends, approves, implements, and verifies?
  • A security event occurs outside the stated coverage. Who receives the escalation and who leads the response?
  • A customer request creates urgent work not listed in the mandate. What gets deferred, and who approves the change?

If the written scope cannot answer those questions, it is not yet ready. Translate the final decisions into the applicable agreement with qualified legal and procurement review.

If you need an evidence-backed starting point or continuing leadership, vCSO.ai’s Cyber Risk Assessment and Fractional CISO Leadership can be scoped around agreed evidence, leadership decisions, reporting, and a prioritized action plan. Client implementation, specialist work, coverage, and repeat technical reviews remain subject to the written mandate.

Questions & answers

What should a fractional CISO scope of work include?

Include the mandate, starting evidence, decision rights, capacity and coverage, cadence, deliverables and acceptance criteria, implementation boundary, escalation path, change control, and exit or handoff terms.

Is this template a contract or legal language?

No. It is a practical buyer worksheet, not legal advice or a substitute for an agreement reviewed by qualified counsel. Translate the agreed scope into your organization’s contracting documents.

Who should approve the scope?

The executive sponsor should approve the mandate and decision rights. Technical, legal, risk, finance, and business owners should confirm the responsibilities and dependencies that affect them.

Ready to turn this into a working plan?

Our team helps growth-stage companies, PE/VC sponsors, and cybersecurity product teams translate security questions into board-ready decisions. First call is strategy, not vendor pitch.

Scope an assessment