Cyber Risk Assessment Template for MSP Clients

A reusable cyber risk assessment template for MSP clients, with a scoring scale, worked example and EU, UK and US differences.
On this page

Last updated: 19 November 2026

Quick answer: A cyber risk assessment template for MSP clients is a repeatable structure for scoping each client, listing assets and threats, scoring likelihood and impact, recording existing controls and agreeing treatment with a named owner. Use one method for every client, align it with NIST SP 800-30 or ISO/IEC 27005, and refresh it at least annually.

Most managed service providers already know their clients’ networks better than the clients do. What is often missing is a written, defensible cyber risk assessment that turns that knowledge into decisions the client’s leadership can sign off. Without one, security recommendations look like upselling, and compliance questions from auditors, insurers or regulators go unanswered.

This guide gives you a cyber risk assessment template you can reuse across your client base, a worked example, a scoring scale, and the points where European, UK and US expectations differ. It is written for MSPs, MSSPs and consultancies that deliver vCISO-style services.

What is a cyber risk assessment template for MSP clients?

It is a standard document and method that you apply to every client so that risks are identified, scored and treated in the same way each time. The template fixes the structure; the content changes per client.

Consistency is the point. When every client is assessed on the same scale, you can compare risk across your portfolio, spot common weaknesses and show progress quarter by quarter. It also protects you: if a client suffers an incident, a signed assessment shows what you identified, what you recommended and what the client chose to accept.

A template does not have to be complicated. The NCSC’s risk management guidance stresses that no single technique suits every situation and that risk work should support business outcomes rather than box-ticking. For smaller clients, a lean asset-and-threat approach is usually enough; larger or regulated clients may need a more formal methodology.

Why do MSP clients need a formal risk assessment?

Because regulators, insurers and customers increasingly expect risk decisions to be documented, and many small and mid-sized organisations still do not do it. The UK government’s Cyber Security Breaches Survey 2025/26, published on 30 April 2026, found that 43% of businesses identified a breach or attack in the previous 12 months, yet only 30% had carried out a cyber security risk assessment and just 15% had reviewed risks from their immediate suppliers.

That gap is your opportunity. A risk assessment is often the first structured deliverable in a vCISO engagement, and it creates the roadmap for everything that follows: policies, control improvements, incident planning and supplier reviews.

Regulation adds pressure in the EU. Under the NIS2 Directive, Article 21 requires essential and important entities to take an all-hazards approach and to have policies on risk analysis and information system security, while Article 20 makes management bodies responsible for approving and overseeing those measures. If your client is in scope, a documented risk assessment is not optional.

Which methodology should the template follow?

Pick one recognised method and apply it consistently. The two most widely used are NIST SP 800-30 and ISO/IEC 27005, and both work well as the backbone of an MSP template.

  • NIST SP 800-30 Rev. 1. The NIST Guide for Conducting Risk Assessments, published in September 2012, describes a four-step process: prepare, conduct, communicate and maintain. It frames risk in terms of threat sources, vulnerabilities, likelihood and impact.
  • ISO/IEC 27005:2022. The ISO guidance supports the risk requirements of ISO 27001 and allows both asset-based and event-based approaches. It suits clients working towards certification. See our ISO 27005 risk assessment guide for the detail.
  • NIST CSF 2.0. The NIST Cybersecurity Framework 2.0, published on 26 February 2024, is not a risk method as such, but its Govern and Identify functions give you a useful checklist of outcomes to test during the assessment. Our NIST CSF framework page summarises the structure.

In practice: many MSPs use an ISO 27005-style asset and scenario register for every client, then map findings to NIST CSF outcomes for reporting. That gives technical depth and a board-friendly summary from one piece of work.

What should the cyber risk assessment template include?

At minimum, eight sections. Copy the structure below into your own document or GRC tool and keep the headings identical for every client.

1. Scope and context

Client name, business activities, locations, headcount, regulatory drivers (for example GDPR, NIS2, DORA, HIPAA or PCI DSS), assessment date, assessor and client sponsor. State what is out of scope.

2. Risk criteria

The likelihood and impact scales, the risk matrix and the client’s risk appetite. Agree these with the client before scoring anything, or every rating becomes a debate.

3. Asset inventory

Key systems, data sets, cloud services, endpoints and people. Record the owner and the business process each asset supports. Your RMM and PSA data are a good starting point.

4. Threats and vulnerabilities

Realistic threat scenarios for the client’s sector: ransomware, business email compromise, credential theft, supplier compromise, insider error, outages. Link each to known vulnerabilities or control gaps.

5. Existing controls

What is already in place and how effective it is: MFA coverage, backup testing, patch cadence, logging, awareness training, incident plans.

6. Risk scoring

Inherent risk (before controls) and current risk (with existing controls), using the agreed scale.

7. Treatment plan

For each risk above appetite: treat, transfer, avoid or accept. Name the owner, action, budget line and due date. Accepted risks need a client signature.

8. Sign-off and review

Client approval, next review date and triggers for early review, such as a major incident, acquisition or new regulation.

How should you score likelihood and impact?

Use a simple five-point scale for both, multiply them, and map the result to four bands. Keep the definitions in plain business language so non-technical directors can apply them.

ScoreLikelihoodImpact
1Rare: not expected in the next 3 yearsNegligible: no noticeable disruption or data exposure
2Unlikely: could happen within 3 yearsMinor: hours of disruption, limited internal data
3Possible: could happen within 12 monthsModerate: a day of disruption or personal data exposure needing assessment
4Likely: expected within 12 monthsMajor: several days of outage, reportable breach, customer impact
5Almost certain: already happening or imminentSevere: business survival, regulatory action or large-scale data loss

Bands: 1-4 low, 5-9 medium, 10-16 high, 20-25 critical. The exact thresholds matter less than applying them the same way for every client.

Common mistake: scoring impact only on IT downtime. Include regulatory, contractual and reputational consequences, especially where personal data is involved.

Worked example: a 40-person accountancy firm

Here is how one row of the template might look for a typical small professional services client.

FieldEntry
AssetMicrosoft 365 mailboxes and SharePoint client files
Threat scenarioBusiness email compromise leads to fraudulent payment instructions and client data exposure
VulnerabilityMFA enforced for staff, but not for two legacy shared mailboxes; no conditional access
Existing controlsEmail filtering, annual awareness training
Likelihood / impact4 / 4 = 16 (high)
TreatmentTreat: enforce MFA on all accounts, add conditional access, payment verification call-back procedure
Owner / dueClient operations director with MSP; 30 days
Target risk2 / 4 = 8 (medium)

Repeat for 15 to 30 scenarios and you have a register that the client’s partners can read in one sitting.

If you want to run this template across dozens of clients without maintaining separate spreadsheets, book a partner demo to see how a multi-tenant platform handles it.

How do risk expectations differ in the EU, UK and US?

The core method is the same everywhere, but the legal drivers and the language clients recognise differ by region.

RegionMain driversWhat to emphasise
EUNIS2 Article 21, DORA for financial entities, GDPR Article 32Management body approval, supply chain risk, link to incident reporting duties
UKUK GDPR, NIS Regulations for operators in scope, Cyber Essentials, insurer questionnairesNCSC guidance, board oversight in line with the Cyber Governance Code of Practice
USSector rules such as HIPAA and the FTC Safeguards Rule, state laws, customer contractsNIST SP 800-30 and CSF 2.0 language, written risk assessment evidence

For clients operating across regions, map one set of findings to several frameworks rather than writing separate assessments. A cross-framework library such as the Compliance Universe helps you reuse the same control evidence for NIS2, ISO 27001 and NIST CSF.

How do you run the assessment across many clients?

Standardise, then automate. The process below works for a portfolio of any size.

  1. Onboard with a questionnaire. Send a short pre-assessment covering business context, regulations and key systems.
  2. Pull technical data. Use RMM, vulnerability scans and identity reports to populate assets and control status.
  3. Hold a 90-minute workshop. Validate scenarios and scores with the client’s decision-makers.
  4. Issue the register and treatment plan. Keep a one-page summary for the board and the full register as an appendix.
  5. Track treatment. Turn actions into tickets with owners and due dates, and review them in quarterly business reviews.
  6. Reassess. At least annually, and after major changes or incidents.

Supplier risk deserves its own step. Most client breaches involve a third party somewhere, so pair the assessment with a vendor and third-party risk management review of the client’s critical suppliers.

In practice: run compliance assessments and the risk register from the same data. Control gaps found in an ISO 27001 or NIS2 gap analysis should appear automatically as risks, not be copied by hand.

Key takeaways

  • Use one cyber risk assessment template and one scoring scale for every client so results are comparable.
  • Base the method on NIST SP 800-30 or ISO/IEC 27005, and report against NIST CSF 2.0 outcomes if useful.
  • Agree risk criteria and appetite with the client before scoring.
  • Every risk above appetite needs a named owner, action and due date; accepted risks need a signature.
  • Reassess at least annually and after major incidents or changes.

Frequently asked questions

How often should an MSP reassess client cyber risk?
At least once a year, and whenever something material changes: a significant incident, a merger, a new core system, a move to a new cloud provider or a new regulatory obligation. Many MSPs also review the top risks at every quarterly business review so treatment progress stays visible to the client’s leadership.

Is a spreadsheet good enough as a risk assessment template?
For a handful of clients, yes. As your portfolio grows, spreadsheets become hard to keep consistent, version and evidence. You lose the ability to compare clients, track treatment actions and show auditors a history. That is usually the point where MSPs move the template into a multi-tenant GRC platform.

Who should sign off the client’s risk assessment?
A senior client representative with authority over risk decisions, such as a director, partner or the management body. Under NIS2, management bodies must approve cybersecurity risk-management measures. The MSP prepares and advises, but the client owns the risks and must formally accept any residual risk above appetite.

What is the difference between a risk assessment and a gap analysis?
A gap analysis compares current controls against a framework such as ISO 27001 or NIS2 and lists what is missing. A risk assessment asks what could go wrong, how likely it is and how bad it would be. Gaps feed the risk assessment, but not every gap is a high risk.

Can one template cover EU, UK and US clients?
Yes. Keep the structure, scales and scoring identical and add a regulatory context section per client. Then map findings to the frameworks that apply, such as NIS2, UK GDPR or HIPAA. This keeps your delivery consistent while meeting each region’s documentation expectations.

Conclusion: make risk the start of every engagement

A consistent cyber risk assessment template turns your technical knowledge of each client into decisions their leadership owns. Start with scope and criteria, score honestly, assign owners and revisit the register every quarter. For the service model around it, read our guide to vCISO and vDPO services and see how Enactia for MSPs, the GRC platform for vCISO and vDPO services, supports multi-client risk management.

To discuss how your team could deliver risk assessments 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.