Skip to main content
MSP Operations

MSP Cybersecurity: What MSPs Secure, MSP vs MSSP, and Securing the MSP Itself

MSP cybersecurity explained: what an MSP typically secures for clients, how it differs from an MSSP, and how MSPs secure their own practice.

G
GetCybr Research
··9 min read
Diagram contrasting the security services an MSP provides to clients with the controls an MSP applies to its own practice

Key Takeaways

MSP cybersecurity means two things: the security an MSP provides to its clients, and the security of the MSP itself, which holds privileged access to many client networks. This guide sets out what MSPs commonly secure, compares an MSP with an MSSP in plain terms, quotes the CISA, NSA, FBI and NCSC-UK joint advisory AA22-131A and NCSC guidance on securing the provider, and shows how to turn security work into a compliance service. Sources read on 21 November 2026.

“MSP cybersecurity” is used for two different things. One is the security an MSP provides to its clients. The other is the security of the MSP itself, which is a target because of the access it holds. This guide covers both, explains how an MSP differs from an MSSP, and ends with how MSPs turn security work into a service clients can evidence.

At a glance

  • What MSPs typically secure for clients: patching, endpoint protection, backup and recovery, identity and multi-factor authentication, email security, and monitoring and logging. The contract sets the exact scope.
  • MSP vs MSSP: an MSP typically runs IT with a security baseline built in. An MSSP typically makes security its main service. Many providers do some of both.
  • Why the MSP is a target: the joint advisory AA22-131A says MSP services “usually require both trusted network connectivity and privileged access to and from customer systems”.
  • What to do about it: apply the advisory’s recommendations to your own practice first, then use the same discipline as a compliance service for clients.

What “MSP cybersecurity” covers

The joint advisory AA22-131A, in its appendix, uses a definition under which an MSP delivers services such as network, application, infrastructure and security “via ongoing and regular support and active administration”. Security is part of that service, and what an MSP secures for a client is commonly the following.

  • Patching and updates. Keeping operating systems, applications and network devices updated on an agreed schedule, and reporting on what is outstanding.
  • Endpoint protection. Deploying and maintaining endpoint security tooling across managed devices, and acting on what it reports.
  • Backup and recovery. Taking backups, protecting them from tampering and testing that data can be restored.
  • Identity and multi-factor authentication. Managing user accounts and administrative rights, enforcing MFA, and removing access when people leave.
  • Email security. Filtering for phishing and malware and managing mail configuration, as the advisory lists phishing among the techniques used against MSPs.
  • Monitoring and logging. Collecting alerts and logs from managed systems and triaging them. How much attention they get depends on the service tier, covered in the comparison below.

Two cautions apply. First, this is a practitioner’s list, not a standard: providers package these differently and charge differently. Second, the client should never have to guess. The NCSC says the contract “should clearly specify what is and what is not included” and suggests a matrix of responsibilities that details what the MSP will do and what the customer is expected to do.

MSP vs MSSP: what is different

The two terms overlap, and no official body fixes the boundary. The table describes what is typical, so treat it as a starting point for a scoping conversation and not a definition. Many providers are both, or deliver security monitoring through a partner.

Area MSP (typical) MSSP (typical)
Core job Runs and supports IT: service desk, devices, cloud, network. Security is built into that service. Makes security the main service and the main measure of success.
Security scope Baseline hygiene: patching, endpoint protection, backup, identity and MFA, email security. Detection, investigation and response, often with vulnerability management and security reporting on top.
Monitoring model Alerts from management and endpoint tools, triaged by the service desk or a security partner, with coverage hours set by the contract. Dedicated security analysts working from a monitoring platform, with the coverage model, often round-the-clock, set by the contract.
SLA categories Service desk response and resolution tiers, plus availability of managed services. Alert triage, escalation and containment targets, plus incident reporting.
Evidence clients receive Patch, backup and health reports. Alert and incident reports, security metrics and trend reviews.
Client usually needs it when The business needs its IT run well with a sound security baseline and has little in-house security staff. The business has to show continuous monitoring to a regulator, insurer or customer, or holds data that makes a quiet breach costly.

Neither model is better in the abstract. A small client with a modest risk profile can be well served by an MSP with a strong baseline. A client under a regulator or insurer that expects continuous monitoring may need MSSP-style coverage, from the same provider or an MSSP partner. If you do both, say which service line each contract covers, and record the split in the responsibility matrix.

Securing the MSP itself

The joint advisory AA22-131A, “Protecting Against Cyber Threats to Managed Service Providers and their Customers”, was released on 11 May 2022 by the cybersecurity authorities of the United Kingdom (NCSC-UK), Australia, Canada, New Zealand and the United States (CISA, NSA and FBI). It says they “are aware of recent reports that observe an increase in malicious cyber activity targeting managed service providers (MSPs) and expect this trend to continue”. Its explanation of why is short: “MSPs provide services that usually require both trusted network connectivity and privileged access to and from customer systems.” It adds that “threat actors can use a vulnerable MSP as an initial access vector to multiple victim networks, with globally cascading effects.”

The advisory dates from 2022, so read it as an established baseline and not as a statement about current volumes. Its recommendations for MSPs include the following, quoted as published.

  • Multi-factor authentication. “MSPs should also implement MFA on all accounts that have access to customer environments and should treat those accounts as privileged.”
  • Logging. “MSPs should log the delivery infrastructure activities used to provide services to the customer.”
  • Segregation. “Segregate customer data sets (and services, where applicable) from each other” and “Do not reuse admin credentials across multiple customers.”
  • Updates. “MSPs should implement updates on internal networks as quickly as possible.”
  • Backups. MSPs should “maintain offline backups encrypted with separate, offline encryption keys”.
  • Incident response. “MSPs should develop and regularly exercise internal incident response and recovery plans and encourage customers to do the same.”
  • Supply chain. “MSPs should understand their own supply chain risk and manage the cascading risks it poses to customers.”
  • Contracts. “Both MSPs and their customers will benefit from contractual arrangements that clearly define responsibilities.”

NCSC guidance, “Choosing a managed service provider (MSP)”, published 24 November 2025, shows what customers are being told to ask. It says: “Check that MSPs also protect their access to your systems.” It adds that MSPs “should also have 2SV in place, so these important credentials are protected”, and that the provider “should have clear steps on how they will respond to any incidents and how they will engage with you (including what happens if MSPs are themselves impacted by an incident)”. It also advises customers to use MSPs with recognised certifications, naming Cyber Essentials Plus, and describes ISO 27001 and SOC 2 as demonstrating that an organisation takes information security seriously.

In the UK, regulation is starting to follow the same logic. The Cyber Security and Resilience Bill would bring medium and large managed service providers into the scope of the NIS Regulations 2018. As of 21 November 2026 it is still a Bill, so see what MSPs need to know about the Cyber Security and Resilience Bill for the status and the official sources. For a wider look at hardening a practice, see your MSP is the attack surface.

A self-check for your own practice

  • Is MFA enforced on every account that can reach a client environment, including service accounts where it is supported?
  • Do you use separate administrative credentials for each customer?
  • Are your delivery tools, such as RMM and PSA platforms, logged and monitored?
  • Can you restore your own systems from backups that an attacker in your network could not reach?
  • When did you last exercise an incident response plan that covers you being the compromised party?
  • Do your contracts state who owns which security responsibilities?

Turning security into a compliance service

Clients usually do not ask for “security”. They ask for evidence against something named: a customer questionnaire, an insurer’s renewal form or a regulation. That makes frameworks the natural way to package MSP cybersecurity as a recurring service. These are the ones clients commonly ask an MSP about, each with a page that states its scope and source.

  • Compliance frameworks catalogue: the full list, to see which frameworks overlap.
  • Cyber Essentials: the UK government baseline scheme. The NCSC’s MSP guidance names Cyber Essentials Plus as a certification to look for.
  • NCSC Cyber Assessment Framework: an outcomes-based NCSC framework developed to support cyber oversight.
  • NIST SP 800-171: commonly requested by US defence and federal supply chains.
  • FTC Safeguards Rule: for US financial institutions within the FTC’s scope.
  • HIPAA: for US healthcare organisations and their business associates.
  • SOC 2: commonly requested of service organisations by their customers.

If you need a baseline to assess clients against first, the MSP client security baseline using CIS Controls gives a structure you can reuse. Pricing the work is a separate question, and the readiness list in the vCISO cost guide links guides for Cyber Essentials, ISO 27001, SOC 2, CMMC and PCI that separate what the scheme or certification body charges from the work of getting ready, and say where no official price exists.

Where GetCybr fits

GetCybr is a compliance platform for MSPs: one platform holds many client organisations, each with its own data, frameworks and reports. The GRC software for MSPs page explains the model. For the work above, that means you can run the same structured assessment across clients and keep each client’s evidence separate. Run security assessments as a conversation: GetCybr’s AI interview asks the questions and drafts control maturity, and nothing is saved until your reviewer applies it. White-label client reports are included.

GetCybr is software. The security services, and the decisions about client scope, remain yours. It does not make a practice or its clients compliant with a framework.

Sources

Read on 21 November 2026. Quotations in this guide are taken from these pages.

The MSP vs MSSP comparison is a practitioner summary of typical scope, not a quotation from either source. General information, not legal advice.

Next step

If you run compliance services across many MSP clients, you can become a partner.

Run compliance and vCISO work for every client

MSPs: put the repeatable assessment, roadmap, and reporting work on GetCybr while your team stays in control of every client relationship.