vCISO Statement of Work (SOW) Template for MSPs

A reusable vCISO statement of work template for MSPs, with 12 sections, first-year deliverables, a RACI and regional points to include.
On this page

Last updated: 22 November 2026

Quick answer: A vCISO statement of work (SOW) defines exactly what a virtual CISO service delivers for a client: objectives, scope, deliverables, meeting cadence, roles, client responsibilities, exclusions, acceptance criteria and change control. It sits under a master services agreement and makes clear that the vCISO advises while the client’s leadership keeps accountability for cyber risk.

Most disputes in vCISO engagements are not about security. They are about expectations: the client thought the vCISO would run the SOC, the provider thought it was a monthly advisory call, and nobody wrote down who owns the incident response plan.

A clear vCISO statement of work prevents that. This guide gives MSPs, MSSPs and consultancies a reusable SOW template, sample deliverables for the first year, a RACI table and the EU, UK and US points to reflect in the wording.

What is a vCISO statement of work?

It is the engagement-specific document that turns a general contract into a concrete service. The master services agreement (MSA) covers legal terms such as liability, confidentiality and payment; the SOW covers what will be done, by whom, when and how success is measured.

Keeping the two separate lets you reuse one MSA across clients while tailoring the SOW to each client’s size, sector and regulations. When the scope changes, you amend or replace the SOW rather than renegotiating the whole contract.

In practice: write the SOW so a new client executive who was not involved in the sale can read it and understand what they are paying for in ten minutes.

Why does the SOW matter so much for vCISO services?

Because the CISO role is broad and the client often has limited internal capacity to absorb the work. Without clear boundaries, a fractional service drifts into unpaid full-time work or, worse, into accountability the provider cannot carry.

Governance gaps are common. The UK government’s Cyber Security Breaches Survey 2025/26 found that only 31% of businesses had a board member or trustee with responsibility for cyber security, and only 25% had a formal incident response plan. Those are exactly the gaps a vCISO is hired to close, and the SOW should name them as deliverables.

Regulation also shapes the wording. Under Article 20 of the NIS2 Directive, management bodies of essential and important entities must approve cybersecurity risk-management measures, oversee their implementation and follow training. A vCISO can prepare and advise, but the SOW should not suggest that legal accountability transfers to the provider.

What should a vCISO statement of work template include?

Use these twelve sections. Keep the numbering fixed across clients so your delivery team always knows where to look.

  1. Parties and background. Client, provider, MSA reference, a short description of the client’s business and why the engagement exists.
  2. Objectives. Three to five measurable outcomes, for example “achieve ISO 27001 certification readiness” or “approve and test an incident response plan”.
  3. Scope. Entities, locations, systems and frameworks in scope (for example NIS2, ISO 27001, SOC 2, GDPR security requirements). List what is out of scope explicitly.
  4. Service model. Hours or days per month, named vCISO and backup, remote or on-site, working hours and response times for urgent requests.
  5. Deliverables. Specific documents and activities with target dates (see the table below).
  6. Governance cadence. Monthly security steering meeting, quarterly board or management report, annual strategy review.
  7. Roles and responsibilities. A RACI covering the vCISO, client executive sponsor, client IT, the MSP’s operational teams and third parties.
  8. Client responsibilities. Access to people and systems, timely decisions, nominated owners for risks and policies, budget for remediation.
  9. Assumptions and exclusions. For example: no 24/7 incident response unless separately contracted, no penetration testing, no legal advice, no role as the client’s statutory officer.
  10. Acceptance criteria. How each deliverable is reviewed and signed off, and the time allowed for client comments.
  11. Change control. How new requests are raised, estimated and approved, and how urgent work outside scope is handled.
  12. Reporting and KPIs. The metrics you will report, the data sources and the format.

Commercial terms, such as fees and invoicing, can sit in a schedule to the SOW or in the MSA, depending on your standard contract structure.

What deliverables should the first year include?

Split the year into phases. Early deliverables establish the baseline; later ones build the programme and prove it works.

PhaseTypical deliverables
Days 1 to 30Kick-off, stakeholder interviews, asset and supplier overview, current-state gap assessment against the chosen framework
Days 31 to 90Cyber risk assessment and risk register, prioritised roadmap, core policy set drafted, incident response plan drafted
Months 4 to 6Policies approved, awareness plan launched, supplier risk reviews started, first management report
Months 7 to 9Incident response tabletop exercise, control testing, evidence collection for audits or customer questionnaires
Months 10 to 12Internal review or audit readiness check, annual board report, updated roadmap and SOW renewal proposal

Tie each deliverable to a platform workflow where you can: compliance assessments for the gap analysis, enterprise risk management for the register, policy management for approvals and incident and data breach management for the response plan and exercises.

If you deliver this across many clients and want one place to run it, book a partner demo.

How should roles and responsibilities be split?

Use a simple RACI in the SOW. The key principle is that the client’s leadership is accountable for risk decisions, while the vCISO is responsible for preparing, advising and tracking.

ActivityvCISOClient executiveClient IT / MSP operations
Risk assessment and registerResponsibleAccountableConsulted
Risk acceptance decisionsConsultedAccountable and responsibleInformed
Policy drafting and approvalResponsible (drafting)Accountable (approval)Consulted
Technical control implementationConsultedAccountableResponsible
Incident response plan and exercisesResponsibleAccountableResponsible (execution)
Board and management reportingResponsibleAccountableInformed

Common mistake: letting the vCISO sign off risk acceptances. It blurs accountability and can expose the provider if a risk later materialises.

What EU, UK and US points should the SOW reflect?

The template is the same everywhere, but reference the frameworks and expectations your client’s leadership will recognise.

RegionPoints to reflect
EUNIS2 management body approval and training, supply chain security, incident reporting readiness; DORA for financial entities; GDPR Article 28 terms where the provider processes personal data
UKBoard oversight aligned with the Cyber Governance Code of Practice, Cyber Essentials where relevant, UK GDPR processor terms
USNIST CSF 2.0 Govern outcomes, sector rules such as HIPAA or the FTC Safeguards Rule, customer contract requirements such as SOC 2

The UK’s Cyber Governance Code of Practice, published on 8 April 2025, sets out what boards and directors are expected to do on cyber risk, which makes it a useful reference for board reporting deliverables. In the US and internationally, the Govern function of the NIST Cybersecurity Framework 2.0 gives a vocabulary for strategy, roles, policy and oversight outcomes.

If the vCISO will access personal data, for example in logs, HR records or incident investigations, the provider is likely to act as a processor. Article 28 of the GDPR then requires a written contract covering the processing, confidentiality, security, sub-processors and assistance with data subject rights and breaches. Reference the data processing agreement in the SOW.

Which KPIs belong in a vCISO SOW?

Choose a small set the client’s leadership cares about, and agree the data source for each.

  • Percentage of roadmap actions completed on time.
  • Number of high and critical risks open, and their average age.
  • Policy review status: approved, due, overdue.
  • Coverage of key controls, such as MFA and tested backups.
  • Supplier reviews completed for critical vendors.
  • Incident exercises held and actions closed.

In practice: report KPIs as trends, not snapshots. A falling number of overdue high risks tells a clearer story than a single month’s count.

Key takeaways

  • Keep legal terms in the MSA and put scope, deliverables, cadence and responsibilities in the vCISO statement of work.
  • Name out-of-scope work and exclusions explicitly to prevent scope creep.
  • Make clear that the client’s leadership remains accountable for cyber risk decisions.
  • Phase first-year deliverables and tie them to measurable KPIs.
  • Reflect regional drivers such as NIS2, the UK Cyber Governance Code and NIST CSF 2.0, and add GDPR processor terms where needed.

Frequently asked questions

What is the difference between an MSA and a vCISO SOW?
The master services agreement sets the legal and commercial framework for the relationship, such as liability caps, confidentiality, intellectual property and payment terms. The statement of work describes the specific vCISO service for one engagement: objectives, scope, deliverables, cadence, roles and acceptance. One MSA can support several SOWs over time as the service evolves.

How many hours should a vCISO SOW include?
It depends on the client’s size, regulatory exposure and maturity. Rather than starting from hours, start from the deliverables and cadence the client needs, estimate the effort, then set a monthly allocation with a clear process for additional work. Review the allocation after the first 90 days, when the baseline is known.

Can a vCISO be named as the client’s CISO for regulators?
A vCISO can perform the CISO function, but the SOW should be precise about what that means. Under frameworks such as NIS2, management bodies remain accountable for approving and overseeing cybersecurity measures. Describe the vCISO as the designated security lead or adviser, and check any sector-specific rules before accepting a formal regulatory designation.

Should incident response be included in a vCISO SOW?
Planning and exercising usually should be: drafting the incident response plan, running tabletop exercises and advising during incidents. Round-the-clock hands-on response is a different service with different staffing. If you include it, define response times, escalation paths and fees; if not, list it as an exclusion and point to the separate contract.

How often should a vCISO SOW be reviewed?
At least annually, aligned with the client’s strategy review, and whenever the scope changes materially, such as a new regulation, acquisition or certification goal. Many providers also run a formal review after the first 90 days, once the risk assessment and roadmap have revealed the real level of effort required.

Conclusion: a clear SOW makes the vCISO service scalable

A well-structured vCISO statement of work protects both sides: the client knows what it gets, and your team knows where the service ends. Standardise the twelve sections, tailor the scope and deliverables per client, and review them regularly. For the service model around it, read our guides to vCISO and vDPO services and running every client from one console, and see Enactia for MSPs, the GRC platform for vCISO and vDPO services.

To discuss how to package and deliver vCISO services at scale, contact us or book a partner demo.

Written by
Share
Built for MSPs

Turn compliance into recurring revenue. Launch in days, not months.

Governance, risk & compliance made simple

Fewer spreadsheets. Faster compliance. See Enactia in action.

Ready to make compliance simple?

See how Enactia brings governance, risk and compliance into one AI-powered platform. Book a demo now.