MSP Cybersecurity Stack Explained: The 9 Layers to Check
A proposal that says it "includes security" tells you very little. The difference between two providers quoting the same monthly price is which layers they actually run, which they resell, and which they only watch during business hours. That is what an MSP cybersecurity stack really is: not a page of product logos, but a set of named layers, each with an owner and a response time attached. If a provider cannot tell you who watches a given layer at 2am and how fast they act, that layer is monitoring, not protection.
This guide walks through the nine layers a small or midsize business should expect to see in a managed IT proposal. For each one you get what it does in one plain sentence, the question that separates a real deployment from a checkbox, and what can go wrong when it is missing. Then it covers the difference between 24/7 monitoring and 24/7 response, gives you a comparison table to take into a proposal review, and closes on the four layers no small business should go without.
What an MSP cybersecurity stack actually is
A cybersecurity stack is the combination of tools, processes, and people a managed service provider uses to prevent, detect, and recover from attacks on your systems. The tools get the attention in sales decks. The processes and people decide whether the tools do anything.
Two proposals can list the same nine categories and deliver very different protection. One provider deploys endpoint detection on every device, tunes the alerts, and has an analyst who isolates an infected laptop within minutes, at 2am on a Sunday. Another resells the same product, leaves it at vendor defaults, and forwards alerts to a shared inbox that someone reads on Monday. Both proposals say "EDR included." Only one of them is protection.
That is why the useful unit of comparison is not the product. It is the layer plus three facts about it:
- Who operates it. Does the MSP's own team configure and manage the tool, or is it resold and left at defaults? Some layers are reasonably delivered through a partner. The MSP should still be able to tell you which ones and who that partner is.
- Who watches it, and when. Business hours only, 24/7 by the MSP's staff, or 24/7 by a third-party security operations center (SOC) the MSP contracts with?
- What happens when it fires, and how fast. A named action (isolate the device, disable the account, block the sender) with a response time in the contract, not just a notification.
The CIS Controls, a widely used and prioritized set of security safeguards, include a control just for outsourcing: Service Provider Management. The security you hand to someone else is only as good as your visibility into who is doing the work. An MSP that will not name which layers it resells versus operates is hiding the answer, not simplifying it.
The MSP security stack, layer by layer
Here are the nine layers, grouped roughly from prevention to recovery. Your business may not need every one at full depth, and the closing section covers how to prioritize. But you should know what each one is, so a proposal cannot skip one quietly.
1. Endpoint protection (EDR, not just antivirus)
What it does: Endpoint detection and response (EDR) watches laptops, desktops, and servers for suspicious behavior, not only known malware signatures, and lets the MSP isolate a compromised device remotely.
The question to ask: "What percentage of our endpoints will run EDR, who reviews its alerts after hours, and can your team isolate a device without waiting for us to approve it?"
When it is missing or hollow: Traditional antivirus can miss attacks that use legitimate admin tools, and ransomware can use those same tools to move through a network. An EDR agent with nobody reviewing its alerts records the attack in detail and stops nothing. Ask for coverage as a percentage, and ask to see it in the console after onboarding. "All endpoints" in the proposal and a handful of unprotected machines in practice is the gap to look for.
2. Patch management
What it does: Keeps operating systems, browsers, third-party applications, and network devices updated so known vulnerabilities get closed before attackers use them.
The question to ask: "What is your patch window for critical vulnerabilities, do you patch third-party apps and firewalls or only Windows, and what patch-compliance percentage will you report to us each month?"
When it is missing or hollow: Operating-system patching alone leaves the gaps attackers favor: browsers, PDF readers, VPN appliances, and firewalls. CISA maintains a Known Exploited Vulnerabilities catalog, a running list of flaws attackers are actively using, and a capable MSP can tell you how quickly it closes items that land on it. CISA's cyber guidance for small businesses suggests leadership track the percentage of systems fully patched as a goal. Your MSP should hand you that number every month without being asked twice.
3. Email security
What it does: Filters phishing, malicious attachments, and impersonation attempts before they reach inboxes, and enforces sender authentication (SPF, DKIM, and DMARC) so attackers cannot easily send mail that looks like it came from your domain.
The question to ask: "Is filtering beyond our mail platform's defaults included, is DMARC set to enforce rather than just monitor, and when an employee reports a suspicious email, who handles it and how fast?"
When it is missing or hollow: Every employee's inbox is a way in. A provider that relies only on default filtering, leaves DMARC in report-only mode indefinitely, or has no process for the phish an employee forwards to the help desk is leaving the front door to chance.
4. Identity and multifactor authentication
What it does: Controls who can sign in to what. That means MFA on email, remote access, and admin accounts, separate admin accounts for privileged work, and prompt removal of access when someone leaves.
The question to ask: "What percentage of our users and admin accounts will have MFA enforced, which MFA methods do you deploy, and how quickly is a departing employee's access removed?"
When it is missing or hollow: Stolen passwords are cheap, and a single account without MFA can undo everything else in the stack. CISA's MFA guidance for businesses says they "should aim to use a phishing-resistant MFA method," and its Cyber Essentials says MFA "should be required of all users, but start with privileged, administrative, and remote access users." Watch the exceptions list. If it reads "MFA everywhere except the owner's account and the shared admin login," those two accounts are exactly the ones an attacker wants.
5. Network, firewall, and DNS filtering
What it does: The firewall controls traffic in and out of your offices, DNS filtering blocks connections to known-malicious sites, and network segmentation keeps a compromise in one area from spreading everywhere.
The question to ask: "Who keeps our firewall firmware current, does DNS filtering cover remote staff as well as the office, and is our network segmented so guest Wi-Fi, cameras, and printers cannot reach our servers?"
When it is missing or hollow: A firewall installed years ago and never updated can become the way in. A flat network, where every device can talk to every other device, turns one infected laptop into an office-wide incident.
6. Backup and tested restore
What it does: Keeps copies of your servers, cloud files, and Microsoft 365 or Google Workspace data somewhere an attacker cannot encrypt or delete them, and proves you can actually get them back.
The question to ask: "Are backups immutable or kept offline, do you back up our cloud mailboxes and files, how long would it take to restore our main server, and when did you last run a documented restore test for us?"
When it is missing or hollow: A backup job that reports success is not proof of a restore. Data Recovery has its own entry in the CIS Controls for a reason. Backup without a documented restore test is a hope, not a plan. Ask for the test report, with the date, what was restored, and how long it took.
7. Logging and SIEM
What it does: Collects sign-in, firewall, server, and cloud logs in one place and keeps them long enough to investigate an incident. A security information and event management (SIEM) tool then correlates those logs to spot attacks that no single tool would catch on its own.
The question to ask: "Which log sources do you collect, how long do you retain them, and who reviews the alerts the SIEM generates, and during which hours?"
When it is missing or hollow: Without logs, an investigation starts with "we don't know how they got in or what they took," which is a hard sentence to say to a cyber insurer or a regulator. A SIEM that nobody reviews is an expensive archive. This layer may also be delivered through a third party, which is fine as long as the MSP names the partner and explains exactly how an alert gets handed back for action.
8. Security awareness training
What it does: Teaches staff to recognize phishing and social engineering, through short training modules and simulated phishing emails, and measures whether behavior improves over time.
The question to ask: "How often do you run phishing simulations, what do you report to us, and what happens with users who click repeatedly?"
When it is missing or hollow: An annual video with no follow-up is a compliance checkbox. Training that matters produces a trend line, click rates and report rates over time, shared with leadership. CISA's small-business guidance makes a related point: leadership, not just IT, has to own the push for basics like MFA, because staff follow what the people in charge track.
9. Incident response
What it does: A written, tested plan for what happens when something gets through: who is called, who makes decisions, how systems are contained and restored, and who talks to your insurer, your lawyers, and your customers.
The question to ask: "Can we see the incident response plan you would run for a client like us, when did you last run a tabletop exercise, and which incident work is included versus billed by the hour?"
When it is missing or hollow: The time to discover that incident response is billed at emergency rates, or that your MSP expects you to bring your own forensics firm, is not during the incident. NIST's SP 800-61 Revision 3 treats incident response as part of ongoing risk management rather than a one-off scramble, and a capable MSP should be able to describe its plan in those terms.
24/7 monitoring and 24/7 response are different products
This is the distinction to settle first in an MSP security proposal, because the gap between the two can hide much of the price difference between providers.
24/7 monitoring means a tool or a person sees the alert at any hour. 24/7 response means someone with the authority and access to act on it does something within a stated time, at any hour. A provider can honestly offer the first without the second. The alert arrives at 2:14am, a ticket is created automatically, and an engineer opens it at 8:30am. That is monitoring. By 8:30am, ransomware has had six hours to spread.
Monitoring without a contracted response time is a notification service. When a proposal says "24/7," ask three follow-ups:
- Is that monitoring, response, or both, and which layers does it cover? It may be the endpoint layer only.
- Who does the overnight work: the MSP's own staff or a third-party SOC? If a third party, what can they do on their own, such as isolating a device or disabling an account, and what waits for the MSP in the morning?
- What is the contracted response time for a confirmed security incident after hours, and is it written into the agreement with a remedy if it is missed?
The right answer is not necessarily 24/7 response on every layer. For a 20-person office, after-hours EDR response plus business-hours coverage on everything else can be a sensible trade. The point is to choose it knowingly instead of discovering it during an incident. If you are weighing a dedicated security provider for the overnight layer, the breakdown of MSP vs MSSP covers how the two roles split. The IT support SLA guide covers how to get response commitments into contract language rather than marketing copy.
A proposal comparison table you can lift
Take this into your next proposal review. For each layer, note what each provider said and which column their answer lands in.
| Layer | Ask for | Strong answer | Red flag |
|---|---|---|---|
| Endpoint (EDR) | Coverage %, after-hours reviewer, isolation authority | EDR on every endpoint, alerts reviewed 24/7, device isolation within a stated time | "Antivirus included," or EDR alerts emailed to a shared inbox |
| Patch management | Critical patch window, third-party apps, monthly compliance % | Critical patches applied within days, third-party apps and firewalls included, compliance % reported monthly | Windows updates only, no reporting |
| Email security | Filtering beyond defaults, DMARC status, phish-report process | Advanced filtering, DMARC at enforce, reported phish triaged the same day | Platform defaults only, DMARC left in monitor mode |
| Identity and MFA | MFA coverage %, methods, admin separation, offboarding speed | MFA on every account including admins, separate admin accounts, same-day offboarding | MFA "available," with exceptions for executives or shared logins |
| Network and DNS | Firewall firmware owner, DNS filtering scope, segmentation | Managed firmware updates, DNS filtering for remote staff, guest and device networks segmented | Firewall untouched since install, flat network |
| Backup and restore | Immutability, cloud data, restore time, last test date | Immutable copies, Microsoft 365 or Workspace backed up, documented restore tests on a set schedule | "Backups run nightly" with no test record |
| Logging and SIEM | Log sources, retention period, alert reviewer | Named log sources, retention stated in months, reviewer and hours named | Logs collected, nobody assigned to read them |
| Awareness training | Simulation cadence, reporting, repeat-clicker process | Regular simulations, trend reporting to leadership | An annual video, no metrics |
| Incident response | Written plan, last tabletop, included vs billed work | Plan shared, tabletop held in the last year, included scope stated in writing | "We'll handle it," with no plan and no pricing |
Two patterns are worth watching as you fill it in. First, a provider whose strong answers all sit on the prevention layers while the response answers stay vague is selling tools, not security operations. Second, a provider who answers every row with a brand name and no process is telling you what they buy, not what they do. Compare process maturity before you compare tool stacks.
The four layers no small business should go without
Not every business needs a 24/7 SOC and a full SIEM. Every business with email, laptops, and data it cannot afford to lose needs these four, operated rather than just licensed:
- EDR on every endpoint, with a named after-hours response. Not antivirus, and not alerts that wait for Monday.
- MFA enforced on every account, admins and executives included. The exceptions list is where breaches start.
- Patch management with a reported compliance number, covering third-party apps and network devices, not only Windows.
- Immutable backups with documented restore tests, including cloud mailboxes and files.
The other five layers scale with your risk. Advanced email security and DNS filtering are inexpensive and belong in a solid proposal. Log retention and a SIEM become requirements when you handle regulated data or when your cyber insurer asks for them. If that describes your business, the compliance frameworks shape the stack, and the guide to HIPAA, PCI, and SOC 2 for managed providers covers how. Formal training programs and tested incident response plans matter more as headcount grows and more people can click the wrong link.
If you are earlier in the decision and still weighing whether outsourced security makes sense at all, start with why small businesses turn to an MSP for cybersecurity. And if you want a neutral way to check a proposal's coverage, NIST's Cybersecurity Framework organizes the same thinking into six functions: govern, identify, protect, detect, respond, and recover. A provider running a real stack should be able to map its layers to those functions on one page.
Compare providers on security posture, not on the word "included"
Once you know which layers matter for your business, the shortlist gets shorter quickly. Build it by state before you take a sales call. Compare cybersecurity providers in Ohio, Texas, North Carolina, or your own state in the MyMSPHub directory of managed IT providers. Then put the nine questions above to every finalist and keep the ones who answer with percentages, dates, and response times. The MyMSPHub buyer's guide walks through the rest of the evaluation, from shortlist to signed agreement.
Frequently asked questions
What should an MSP cybersecurity stack include?
At minimum: endpoint detection and response on every device, patch management that covers third-party apps, email security, MFA on every account, a managed firewall with DNS filtering, and immutable backups with documented restore tests. Logging and SIEM, security awareness training, and a tested incident response plan round out a complete stack. For each layer, the proposal should say who operates it, who watches it, and how fast they act.
How can I tell if an MSP actually runs its security tools or just resells them?
Ask, layer by layer, who configures the tool, who reviews its alerts, and who takes action. Then ask for evidence: an EDR coverage report, a monthly patch-compliance number, a dated restore test, and a sample incident report with client details removed. Reselling is not automatically a problem, since an MSP may partner with a third-party security operations center. Refusing to say which layers are resold is.
What is the difference between 24/7 monitoring and 24/7 response?
Monitoring means someone or something sees an alert at any hour. Response means someone with the authority and access acts on it within a contracted time at any hour, for example isolating an infected laptop or disabling a compromised account. A proposal can offer 24/7 monitoring with business-hours response. Ask which one you are buying, for which layers, and where the response time is written in the contract.
Does a small business need a SIEM from its MSP?
Not necessarily. A SIEM earns its cost when you handle regulated data, when your cyber insurer or a customer contract requires centralized logging, or when your environment is complex enough that an attack could cross several systems. Without those pressures, a smaller office may get more protection per dollar from EDR with 24/7 response, MFA everywhere, and tested backups. Whatever you choose, confirm log retention, because investigations depend on logs that still exist.
How often should an MSP test backup restores?
Often enough that you would trust the result in an emergency, on a schedule written into your agreement. A sensible baseline to ask for is a documented restore test of critical systems at least quarterly, plus a test after any major change. The test should record what was restored, how long it took, and whether it worked. A report that backups completed successfully describes copying data, not getting it back.
Is EDR better than antivirus for a small business?
In capability, yes. Traditional antivirus blocks known malicious files. EDR also watches behavior, which catches attacks that use legitimate admin tools, and it lets the MSP isolate a device remotely. The difference only matters if someone reviews the EDR alerts and acts on them, so ask who does that and during which hours.
What security should be non-negotiable in an MSP contract?
Four layers: EDR on every endpoint with a named after-hours response, MFA enforced on every account including admins, patch management with a reported compliance percentage, and immutable backups with documented restore tests. Get the coverage percentages and response times in writing. The remaining layers scale with your risk, your compliance obligations, and your size.
Related Articles
Free Buyer's Guide
The complete guide to finding and hiring the right MSP for your business.
Download Free Guide