MSP vs MSSP: what is the difference?

MSP vs MSSP: an MSP runs your IT, an MSSP handles security. How EU law defines both, what NIS2 and DORA expect, and how to decide which you need.

9 min read
MSP vs MSSP: what is the difference?

Key takeaways

  • An MSP (managed service provider) runs part of your IT under a recurring contract: servers, network, endpoints, cloud, backups and help desk. An MSSP is an MSP that specialises in security: monitoring, detection and incident response, usually from a SOC.
  • NIS2 defines both (Article 6, points 39 and 40): an MSSP is a managed service provider that carries out or assists with cybersecurity risk management, so every MSSP is an MSP and not the reverse.
  • The MSP answers the question 'is it working?', the MSSP the question 'is someone attacking us?'. When the same team administers and watches your systems, nobody independent checks the people with the keys.
  • MSPs and MSSPs are NIS2 entities in their own right (Annex I, sector 9), and Implementing Regulation (EU) 2024/2690 sets their technical requirements.
  • If your organisation is in scope of NIS2, your MSP is a supplier covered by supply chain security (Article 21(2)(d)); under DORA it is an ICT third-party service provider and responsibility stays with the financial entity.
  • The UK, US, Australian, Canadian and New Zealand authorities (advisory AA22-131A) describe a vulnerable MSP as an initial access vector to multiple networks and recommend MFA, least privilege and logs kept for at least six months.

An MSP (managed service provider) keeps your IT running under a recurring contract: servers, network, endpoints, cloud, backups and help desk. An MSSP (managed security service provider) is an MSP that specialises in security: monitoring, detection and incident response, usually from a SOC. EU law draws the line the same way: every MSSP is an MSP, not every MSP is an MSSP.

This guide is for IT managers, CISOs and compliance leads in European mid-market organisations who want to know where their IT provider's job ends and where security begins: the practical differences, what NIS2 says about both, why an MSP is also a point of risk, and how to decide what you need. If you already know you need a security provider, our guide on what an MSSP is and how to choose one goes deeper on that side.

MSP vs MSSP: the short answer

The two are easiest to tell apart by the question each one answers.

  • The MSP asks: is it working? Its job is availability. Servers up, network reachable, patches applied, backups completed, users able to log in. The typical way of working is a NOC (network operations centre) that watches performance and outages.
  • The MSSP asks: is someone attacking us, and what do we do? Its job is threat detection and response. Logs collected and correlated, alerts investigated, compromised machines isolated. The typical way of working is a SOC (security operations centre), often staffed around the clock.

The differences follow from there:

  • Typical services. MSP: infrastructure, network, endpoints, patching, backup, cloud tenants, help desk. MSSP: SIEM monitoring, alert triage, incident response, managed EDR, vulnerability management, sometimes penetration testing.
  • What the SLA measures. MSP: uptime, time to respond to and resolve a ticket. MSSP: time to triage an alert, time to notify you, time to contain.
  • Access. An MSP usually holds administrative rights to run your systems. An MSSP needs visibility (logs, telemetry) and, for response, a limited set of agreed actions.

What EU law says about MSPs and MSSPs

Directive (EU) 2022/2555 (NIS2) defines both terms. A managed service provider is "an entity that provides services related to the installation, management, operation or maintenance of ICT products, networks, infrastructure, applications or any other network and information systems, via assistance or active administration carried out either on customers' premises or remotely" (Article 6, point 39). A managed security service provider is "a managed service provider that carries out or provides assistance for activities relating to cybersecurity risk management" (Article 6, point 40).

So in law the MSSP is a subset of the MSP. Two words in the MSP definition carry most of the weight. Management: the provider takes ongoing responsibility for something, it does not sell a product and leave. Active administration: to do that it holds access, often privileged, to your systems. That access is what makes an MSP useful and what makes it sensitive.

Both are also regulated entities in their own right. NIS2 lists them together in Annex I, sector 9, ICT service management (business-to-business). The directive applies to entities of the types in Annex I that qualify as medium-sized enterprises under Recommendation 2003/361/EC or exceed those ceilings (Article 2(1)). Those that exceed the ceilings for medium-sized enterprises are essential entities (Article 3(1)(a)), the others are important entities (Article 3(2)). For jurisdiction, MSPs and MSSPs fall under the Member State of their main establishment in the Union (Article 26(1)(b)), not every country where they have customers.

Commission Implementing Regulation (EU) 2024/2690 then sets the technical and methodological requirements of the NIS2 risk-management measures for this group, alongside cloud and data centre providers, and specifies when an incident counts as significant for them (Article 1). Being an MSP rather than an MSSP does not lighten those rules: the regulation covers both.

What an MSP does in practice

Scope changes from contract to contract. Most MSP contracts combine some of these: servers and storage, on premises or in the cloud; network, firewalls and VPNs; endpoints, accounts and help desk; patching on an agreed schedule; backups with periodic restore tests; cloud tenants, licences and costs; availability monitoring, with alarms on services down or resources under strain.

What sets an MSP apart from a call-out supplier is the commercial model. In break-fix you pay when something breaks, and the supplier earns more when things go wrong. In the managed model you pay a recurring fee for a defined scope, and the provider has a reason to prevent failures rather than repair them. The fee sits on a contract with service levels: response and resolution times by severity, maintenance windows, hours covered.

Where the line blurs

On paper the line is clean. In the market it is not. Many MSPs sell basic security services, such as managed antivirus or firewall configuration, and some MSSPs also run infrastructure. A label on a proposal tells you little: read the service description.

One question cuts through it: is the provider that runs your systems also the one that watches them? When the same team holds administrative access and reviews the security alerts, nobody independent checks the work of the people with the keys. That is why many organisations keep the two roles with different providers, or at least ask that they sit in separate teams inside the same company, with separate accounts and reporting lines.

NIS2 pays particular attention to the security side. Recital 86 notes that managed security service providers have themselves been targets of cyberattacks and, because of their close integration in the operations of entities, pose a particular risk, and concludes that essential and important entities "should therefore exercise increased diligence in selecting a managed security service provider". The same reasoning applies, in proportion, to any MSP that administers critical systems.

Why an MSP is also a point of risk

An MSP often reaches many customers from the same tools. For an attacker that is efficient: compromise the provider, and there is a path to its customers. In the joint CISA advisory AA22-131A on cyber threats to managed service providers and their customers (11 May 2022), the cybersecurity authorities of the UK, Australia, Canada, New Zealand and the US wrote that threat actors "can use a vulnerable MSP as an initial access vector to multiple victim networks, with globally cascading effects".

The same advisory lists baseline measures for MSPs and their customers. Read from the customer side, they come down to a short list:

  • Multi-factor authentication on remote access and on every provider account that enters your environment, with those accounts treated as privileged.
  • Least privilege: provider accounts limited to the systems the provider manages, not added to every administrator group by default.
  • Log retention: the authorities recommend that organisations "store their most important logs for at least six months", because incidents can surface months later.
  • Old accounts removed, including those of provider staff who no longer work on your contract and those left behind when a contract ends.
  • Backups that are tested, and incident response plans that have been exercised.
  • A clear contract: the advisory says customers should ensure their contractual arrangements specify that the MSP implements these measures, and that contracts "should detail how and when MSPs notify the customer of an incident affecting the customer's environment".

Your MSP as a supplier under NIS2 and DORA

For most mid-market organisations the more frequent case is the other one: the MSP is not the regulated entity, you are. If your organisation is an essential or important entity, supply chain security, "including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers", is one of the minimum cybersecurity risk-management measures (NIS2, Article 21(2)(d)). When choosing those measures, entities take into account the vulnerabilities specific to each direct supplier and service provider and the overall quality of their cybersecurity practices (Article 21(3)).

The MSP that administers your servers is very likely your most critical IT supplier. In practice that means listing it, assessing it, putting security requirements in the contract and reviewing them over time. How to run that process is covered in our guide to third-party risk management, and the wider obligations are in our NIS2 directive guide. National transposition laws add details such as the competent authority, so check the rules of your Member State.

For financial entities the reference is Regulation (EU) 2022/2554 (DORA). An MSP that runs ICT systems on an ongoing basis provides ICT services, so it is an ICT third-party service provider (Article 3, points 19 and 21). The financial entity remains fully responsible for compliance with its obligations even when it uses such services (Article 28(1)(a)), and Article 30 sets the minimum content of the contract. Our DORA service page covers the wider programme.

The same holds for both NIS2 and DORA: outsourcing changes who does the work, not who answers to the authority.

MSP, MSSP or both: how to decide

When an MSP makes sense

  • The internal IT team is small and spends its days on urgent tickets, with no time for maintenance and patching.
  • You need specific skills (cloud, network, backup) that do not justify a full-time hire.
  • You are moving to the cloud and nobody in house knows the target platform.
  • Continuity depends on one or two people, and their absence stops everything.

When you also need an MSSP

  • Nobody looks at security alerts at night, at weekends or during holidays.
  • You fall under NIS2 or DORA and need to detect, handle and document incidents within the reporting timeframes.
  • Your MSP manages your systems and nobody independent reviews what happens on them.
  • You have a SIEM or EDR that produces alerts, but no analysts to investigate them.

A common setup in the mid-market is a mix: internal IT keeps the decisions, the business knowledge and the relationship with users; an MSP takes on the recurring operations; an MSSP watches the whole environment, including the MSP's own access.

Questions to ask an MSP before signing

  1. What is in scope and what is not? A list of systems, sites and services. What is not written down belongs to nobody when something goes wrong.
  2. Which service levels, for which severity? Separate response and resolution times, hours covered, penalties.
  3. How do you access our systems? Tools used, MFA, named accounts rather than shared ones, session logging.
  4. Who watches your access? If security monitoring sits with the same provider, find out who reviews its own technicians.
  5. How fast do you tell us about an incident? For a NIS2 entity it has to fit your own reporting obligations.
  6. Do you use subcontractors? Who they are, where they are, what they can see.
  7. Which certifications, with which scope? An ISO/IEC 27001 certificate covers the scope it declares: read the scope, not just the logo.
  8. How do we leave? Up-to-date documentation, credentials handed back, data returned, handover to the next provider. It is the clause that is easiest to negotiate at the start.

For the security side, the questions are different (what happens when an alert fires at 3 a.m., which response actions are authorised, who keeps the logs and detection rules): they are in our MSSP guide.

How AmagisTech works

We work on both sides of the line, as separate services. On security, we run a managed SOC and MDR service 24/7 on Google SecOps, with Mandiant intelligence: we collect and correlate logs, investigate the alerts that matter and contain threats, with detection rules written for your environment. On infrastructure, we manage Google Cloud environments, migrations and costs. If you want to understand where the gaps are in your current setup, start from our managed cybersecurity service.

In short: an MSP keeps your IT running, an MSSP is an MSP that handles security, and NIS2 defines and regulates both. If you are in scope of NIS2 or DORA, your MSP is a critical supplier because it holds the keys to your systems, and someone other than the administrators should be watching those systems.

Frequently asked questions

An MSP (managed service provider) keeps your IT running under a recurring contract: servers, network, endpoints, cloud, backups and help desk. An MSSP (managed security service provider) is an MSP that specialises in security, such as log monitoring, alert investigation and incident response, usually from a SOC. NIS2 defines the MSSP as a managed service provider that carries out or assists with cybersecurity risk management (Article 6, point 40).
Yes, in EU law. NIS2 defines a managed security service provider as a managed service provider that carries out or provides assistance for activities relating to cybersecurity risk management. The reverse is not true: an MSP that runs servers and help desk without security monitoring is not an MSSP.
They can be. NIS2 lists managed service providers and managed security service providers in Annex I, sector 9 (ICT service management, business-to-business). The directive applies to those that are at least medium-sized under Recommendation 2003/361/EC, and those above the medium-sized ceilings are essential entities. They fall under the jurisdiction of the Member State of their main establishment in the Union.
Not only the MSP. For an essential or important entity, supply chain security, including relationships with direct suppliers and service providers, is a required risk-management measure under NIS2 Article 21(2)(d), and the incident reporting duty stays with the entity. Under DORA, the financial entity remains fully responsible for its obligations (Article 28(1)(a)). The contract should say how and when the MSP tells you about an incident.
An MSP fits when internal IT is stretched by daily operations or lacks specific skills. An MSSP is needed when nobody watches security alerts around the clock, when NIS2 or DORA require you to detect and report incidents, or when no one independent reviews what your MSP does on your systems. Many mid-market organisations use both, with separate roles.

Let's talk about your security.

A 30-minute call to understand where you stand today and tell you, with no commitment, where it pays to start.

Book a call