Illustration of a person at a desk at night fitting a red-orange jigsaw piece into navy, teal and mustard pieces above a laptop showing a shield, with a crescent moon in the window

MSP, MSSP, MDR, SOC, Co-Managed: What Each One Actually Does

A security quote full of MSP, MSSP, MDR and SOC is hard to compare. This decodes each term, shows who acts when something goes wrong under each, and walks through working out what you already have and what you actually need.

A security quote lands on your desk and it reads like alphabet soup. MDR with a 24/7 SOC. Managed EDR. SIEM add-on. Or your cyber insurance renewal asks whether you use an MSSP or an MDR provider, and your IT person shrugs, because they're one person and they've never bought either.

The terms overlap and the sales pages don't help. This is what each one means, who does what under each, and how to work out what a company that already has an IT person actually needs. Sometimes that's nothing new.

The quick answer

  1. MSP (managed service provider): runs your IT. Help desk, laptops, Microsoft 365 users, the network.
  2. MSSP (managed security service provider): watches your security. What it does about what it finds depends on the contract.
  3. MDR (managed detection and response): a service where a team watches around the clock and acts on threats, not just reports them.
  4. SOC (security operations center): the team of analysts doing the watching. You don't usually buy "a SOC". You buy a service that has one, or you build one.
  5. EDR and SIEM are tools, not services. Somebody still has to read what they find.
  6. Co-managed is an arrangement, not a product: your IT person keeps the day-to-day and an outside provider takes a written-down slice of the work.

The question that sorts all of them: when something looks wrong at 2am on a Saturday, who acts, and what are they allowed to do without asking?

You can stop here if your current IT person or provider already has detection and after-hours response written into the contract, and it works. You don't need another provider. Stay with what you have.

Check what you have first

Before comparing anything, find out what you already pay for. Three places to look.

  1. The contract or statement of work with your IT provider. Search it for "monitoring", "incident", "response", "after hours" and "24/7". CISA's advisory for MSP customers (May 2022) says the contract should spell out whether the provider or the customer owns hardening, detection and incident response, and how and when the provider tells you about an incident. If those words aren't in yours, assume it isn't covered.
  2. What's on the computers. On a Windows PC, open the Windows Security app and go to Settings > Manage providers (Microsoft's steps). It lists the antivirus, firewall and web protection in use. If the antivirus is something other than Microsoft Defender, Microsoft says Defender Antivirus turns itself off, so that other product is doing the work. Write down its name. That's the vendor to ask about.
  3. Who has admin access to Microsoft 365. In the Microsoft 365 admin center, go to Settings > Partner relationships (Microsoft Learn). You need to be at least a Billing Administrator to see it. Each row is a company with a relationship to your account. The type matters: Microsoft's page says an Advisor can hold the Global admin and Helpdesk admin roles, while a Reseller has no roles at all.

The terms side by side (as of November 2026)

This table shows what each term means and who usually acts when something's wrong. "Usually" is doing a lot of work. The contract decides, not the label.

Term

What it is

Who acts when something's wrong

After hours?

MSP

An outside company that runs your IT, "an outsourced IT department"

The MSP fixes IT problems. Security response only if the contract says so

Depends on the contract

MSSP

An outside company focused on security monitoring, incident response and data protection

Varies. In the traditional model it sends you confirmed alerts and your team fixes the problem

Depends on the contract

MDR

A managed service: EDR tools plus people who hunt for threats, monitor and respond

The provider's team takes or orchestrates containment

Yes, that's the point of it

SOC

A team of analysts who monitor, detect, investigate and respond. Not a tool or a room

The analysts triage alerts, contain threats and coordinate the fix

Around the clock, in Huntress's definition

EDR

Software on each computer and server that watches for attacks

The tool can act on its own, for example by isolating a device. Everything else goes to whoever reads its alerts

Only if someone is reading

SIEM

A tool that gathers security data from your systems and shows it in one place

You, or whoever you pay to watch it

Only if someone is reading

Co-managed

Your IT person keeps the day-to-day, an outside provider takes a defined part

Whoever the written split says

Whatever the written split says

Sources: CISA's MSP advisory, NIST's SIEM definition, and Huntress's pages on MSP vs MSSP, MSSP vs MDR, SIEM vs EDR vs MDR and what a SOC is, checked November 2026.

A note on those sources. CISA defines an MSP as an entity that delivers, operates or manages IT services for customers under a contract, and NIST defines a SIEM. I couldn't find a government definition of MSSP or MDR, so those rows lean on Huntress's glossary. Huntress sells MDR. Weigh that.

You may also see NOC (network operations center) on a quote. Huntress's SOC page puts the difference plainly: a NOC watches network performance (uptime, latency, connectivity), a SOC watches for security threats.

What a company with its own IT person usually needs

It depends on what you're being asked for and where your gaps are. Here's on what.

  • An insurer or customer asks "do you have EDR?" and nothing more. An EDR product on every computer, run by your IT person, may be all you need. Our post on cyber insurance MFA and EDR questions covers what usually counts.
  • You have EDR, but its alerts go to one person's inbox. The tool is fine. The gap is people. That's what MDR is for, or an MSP or MSSP whose contract includes after-hours response. Who answers a 2am security alert walks through finding out whether you have that gap.
  • The form mentions a SIEM or log retention. A SIEM is a tool someone has to watch, not protection on its own. Don't buy one because the word is on a form. Find out what the form is actually asking for first.
  • You're happy with your MSP and it already covers detection and response in writing. Stay. A second provider means a second set of admin accounts in your systems, and CISA notes that each outside provider can bring risks you didn't plan for.
  • Nobody is asking, you're a small office, and Microsoft 365 is your main system. A security provider probably isn't the first thing to spend on. Start with the Microsoft 365 security settings you already pay for.

How to work out what you need, step by step

Plan on an afternoon. Your IT person can do it, or you can do it with them.

  1. Gather every contract. Your IT provider, any security vendor, and your cyber insurance policy.
  2. Highlight five things in each. Who hardens systems. Who detects attacks. Who responds. How and when they tell you about an incident. What happens to their access when the contract ends. CISA's MSP advisory lists these as things the contract should settle, and says provider accounts should use MFA and be disabled when a contract ends, which it notes is often overlooked.
  3. List your tools. Check Windows Security > Settings > Manage providers on a few computers, and note which Microsoft 365 or Google Workspace plan you're on.
  4. Find where each tool's alerts go. For every tool on the list, write down who gets the alert and how. Watch for two things: alerts that only go to one person, and alerts that only arrive by email.
  5. Write a who-does-what sheet. CISA's risk considerations for MSP customers (September 2021) calls this a shared responsibility model: the vendor's jobs, your jobs and the shared ones, down to who applies patches, maintains hardware and trains employees. Use four columns: Task, Your IT person, Provider, Nobody yet. Rows to start with: patching, EDR alerts on weekdays, EDR alerts at night and on weekends, locking a compromised account, cutting a computer off the network, Microsoft 365 sign-in alerts, backups, staff training.
  6. Read the "Nobody yet" column. That's your real shopping list. If it's empty, you're done. If it only has daytime tasks, your IT person may be able to absorb them. If it's the night and weekend rows, that's the gap MDR or a provider with after-hours response fills.
  7. Clean up admin access while you're there. In Settings > Partner relationships, select a partner you no longer work with, then Remove roles and Yes. Microsoft says this doesn't end the partner relationship itself. To end it, contact that partner.
  8. Ask any provider you're considering the same questions. Who acts at 2am. What they can do without asking, especially isolating a computer and locking an account. How they hand things back to your IT person. The full list is in Can We Get Huntress Without Switching IT Providers? under "Questions to ask any partner before you sign", and it works for any provider.
  9. Get the answers in the contract. Not in a sales email.

Why the terms are so muddled

Because the jobs overlap. Even a security vendor will tell you the categories aren't clean: Huntress's own MSP vs MSSP page says the two "aren't mutually exclusive" and that many organizations use both. One company can be an MSP that resells an MDR service, staffed by someone else's SOC, running EDR on your computers. That's why the who-does-what sheet matters more than which acronym is on the quote.

When to get help

You can do everything above yourself. Bring in someone with security experience, whoever that is, when:

  • The "Nobody yet" column has the night and weekend rows in it, and nobody inside the company can take them.
  • An insurer or customer wants a named provider for detection and response, and your contracts don't have one.
  • You find admin access you can't explain, like a partner relationship or an account from a provider you stopped using.

If you'd rather have an independent view, CISA's risk considerations suggest that organizations without the expertise to weigh these risks could hire an independent consultant. If you have an IT person and want a partner to run Huntress and take the after-hours call while they keep the day-to-day, that's what our co-managed security does.

Related reading

Originally published November 2026.

No comments yet

Managed Nerds Weekly

Get the week's posts in one email

New IT, security and SEO posts every Monday. That's it.