### MSP security stack 2026 : tools, costs and compliance

MSP Tools &amp; Reviews

Security

Technology

BACKUP

BEST PRACTICES

COMPLIANCE

\+11

Kristina Shkriabina

May 8, 2026

4,794 views

Share

EDR list prices run $59.99 to $229.99 per device a year across CrowdStrike Falcon and SentinelOne tiers, a six-layer stack plans at $20 to $37 per endpoint a month before margin, and security averaged 10.9% of IT spending in 2025. Also covers a five-step consolidation plan and device-count budget samples.

Updated: November 2026

A working MSP security stack covers six layers: endpoint detection and response, SIEM, multi-factor authentication, DNS filtering, backup, and vulnerability scanning. This guide maps each layer to specific MSP security tools, commercial and open source, with 2026 list prices, a sample budget split for a 1,000-endpoint book and the controls auditors check against HIPAA, CMMC and SOC 2. Internal IT teams running their own security get the same map, plus in-house budget samples.

### TL;DR

The short answer. A working stack covers EDR, SIEM, MFA, DNS filtering, backup and vulnerability scanning.

Order. Identity and endpoints first, logging second.

Budget. Planning estimates run $20 to $37 per endpoint a month before margin.

In-house IT. Security averaged 10.9% of IT spending in 2025, per the IANS benchmark.

Compliance. Map controls to HIPAA, CMMC and SOC 2 before buying.

### How to think about the MSP security stack

Layered defense is the design that keeps working when a single tool fails or a single vendor suffers a breach. When attackers hit a managed environment, they chain three things: a phishing email or unpatched edge device, a credential-theft step, and lateral movement through privileged tools. Each layer of an MSP security stack exists to break one of those steps, and each layer expects the others to do their job.

Start with the assumption that endpoints will be compromised. EDR catches what AV misses. SIEM captures the trail so you can investigate within minutes rather than days. MFA stops the credential-theft pivot. DNS filtering keeps the initial click from reaching its payload. Backup is the floor: when everything else fails, recovery time is the only metric clients remember. Vulnerability scanning shrinks the surface that everything else has to defend.

Coverage matters more than depth at any single layer. Three EDR-adjacent tools, each sold as a "platform," next to DNS filtering and email security left on Microsoft 365 defaults, add up to duplicated detection logic and an open delivery channel. Spreading the same budget across all six layers closes more of the attack chain.

The three-step attack chain and the layer that breaks each step, with all six layers of the stack

This CRN video looks at how the MSP security stack is changing:

### Endpoint detection and response

EDR carries the largest share of a managed security budget. SentinelOne, CrowdStrike Falcon, and Huntress are three EDR platforms with MSP partner programs. SentinelOne and CrowdStrike sit in the high-end tier; both ship behavioral detection, automated rollback, and managed threat hunting. Huntress takes a different approach, pairing lightweight agents with a 24/7 SOC that triages alerts and writes incident reports for end-clients. Our endpoint security guide covers the wider category around EDR, from EPP to XDR.

Defender for Endpoint deserves a mention if your books lean heavy on Microsoft 365 Business Premium or E5. The licensing math sometimes works in your favor since the agent ships with the seat. Plan the multi-tenant side early: partners manage tenants through Microsoft 365 Lighthouse or the multi-tenant view in the Defender portal, so check how either fits your ticket flow.

ThreatDown, the business security line from Malwarebytes, is another EDR option worth a look; our ThreatDown review covers it in depth.

For open-source coverage, OSSEC and Wazuh agent-based monitoring give you HIDS-style detection without a per-endpoint fee. Velociraptor handles forensic collection and live response. Neither replaces a paid EDR, but they fill gaps for low-margin clients or for retained forensic capability.

Choose EDR by response model as well as by feature checklist. A tool with strong detections and no SOC behind it sends triage to tier-2 technicians at 2 a.m., and that labor cost can outweigh the per-endpoint savings. Our SOC as a service guide covers the build versus buy math.

Published list prices give a starting point for 2026. CrowdStrike Falcon Go, Pro and Enterprise list at $59.99, $99.99 and $184.99 per device a year, and the fully managed Falcon Complete tier is quote-only. SentinelOne Singularity Core, Control, Complete and Commercial list at $69.99, $79.99, $179.99 and $229.99 per endpoint a year. Build the cost model on device counts rather than seat counts, since one user with three managed devices needs three EDR licenses.

Huntress builds for the MSP channel, and the same SOC runs its add-on services for identity threats, SIEM and security awareness training. Managed EDR lists at $8.99 per endpoint a month, and MSP partner rates sit below list. Our Huntress review for MSPs covers partner pricing and how the SOC handles alerts.

### SIEM and log management

Wazuh is a free, open-source SIEM and XDR platform that MSPs can self-host. It scales to thousands of agents on commodity hardware, and the rule library covers compliance frameworks out of the box. The cost is operational: you're running the Wazuh indexer (built on OpenSearch), Filebeat and the Wazuh manager yourself, plus tuning rules to suppress false positives. Our Wazuh review for MSPs covers cost and fit.

For MSPs that want SIEM without the ops burden, Blumira, Arctic Wolf, and ConnectWise SIEM (formerly Perch) offer co-managed services. As a planning estimate, budget $4 to $12 per endpoint per month; quotes scale with log volume and SOC tier. Splunk and Elastic Security exist at the enterprise end if you have a SOC team and need long retention windows.

Log sources decide what a SIEM is worth. A SIEM with EDR alerts, Windows event logs, firewall logs, and Microsoft 365 audit logs gives you something useful. A SIEM with only EDR alerts is an expensive duplicate of the EDR console. Build the source list before you buy.

Retention is the second budget line to scope before signing. SOC 2 sets no fixed retention period, so keep logs that cover the full audit observation window. HIPAA requires covered entities and business associates to keep required documentation for 6 years under 45 CFR 164.316(b)(2), and keeping audit logs on the same 6-year clock is the conservative reading. Hot storage costs more than cold storage, so set the split up front. For the compliance frameworks MSP clients ask about, see the cybersecurity frameworks list .

### Multi-factor authentication and identity

MFA is the layer with the clearest published evidence behind it. A 2023 Microsoft study of MFA found it cut the risk of account compromise by 99.22%, and by 98.56% when credentials had already leaked. Push-based authenticators (Duo, Microsoft Authenticator, Okta Verify) cover the bulk of cases. FIDO2 hardware keys (YubiKey, Token2) belong on admin accounts, especially the global admin and any RMM or PSA console login.

For Microsoft 365 environments, Conditional Access policies in Entra ID P1 handle the core controls: block legacy auth, require MFA on risky sign-ins, restrict admin operations to compliant devices. P2 adds risk-based policies and Privileged Identity Management. The licensing decision usually comes down to whether the client already has Business Premium or needs an add-on.

Plan for the MFA-bypass paths as well. Adversary-in-the-middle phishing kits such as Evilginx steal session tokens after a user completes push or code-based MFA. Phishing-resistant MFA (FIDO2, Windows Hello for Business, certificate-based) closes that path for high-privilege accounts. Push fatigue attacks target the same tier-1 methods, so keep number matching on by default.

Identity management itself sits one layer above MFA. JumpCloud, Microsoft Entra, and Okta cover SSO, lifecycle, and conditional access. For MSPs running 50 small clients, JumpCloud's multi-tenant MSP portal manages each client from one console.

The identity layer is where the same gaps keep turning up across tenants:

### DNS filtering and web protection

DNS filtering catches the click before it loads. DNSFilter and Cisco Umbrella both ship multi-tenant consoles, threat intelligence feeds, and reporting that maps to client-facing reviews. ControlD and NextDNS cover the lower end with simpler pricing and multi-site features.

For open-source pilots, Pi-hole and AdGuard Home work for small offices but lack the central management an MSP needs across a client base. They're useful for testing or for tiny accounts; they aren't a fleet solution.

The pairing matters: DNS filtering plus a secure web gateway plus email security is the delivery-channel triangle. Skip any one and the other two compensate at higher cost. Completing the triangle is a low-cost step to take before adding detection depth at the endpoint.

Cloudflare Gateway deserves a separate mention. The Zero Trust tier integrates with major identity providers and gives you a DNS-and-HTTP filter plus tunneling in one console. For MSPs already running Cloudflare DNS, the upsell is straightforward.

### Backup and disaster recovery

Backup is where an MSP security stack proves its value to clients. Three numbers matter: RPO (how much data you can afford to lose), RTO (how fast you can be operational), and immutability (whether ransomware can reach the backups). A backup tool should report all three for the last 30 days.

Datto BCDR and Acronis Cyber Protect are two MSP-focused options for SMB clients. Datto's image-based backups and rapid spin-up are well-suited for client environments with on-prem servers. Acronis bundles backup, EDR, and patching in one agent, which simplifies the stack at the cost of vendor concentration risk.

For SaaS data, Veeam Backup for Microsoft 365 is a long-standing third-party option, and Microsoft 365 Backup, Microsoft's own service, bills at $0.15 per GB a month. Native retention policies hold versions and deleted items for set windows; a backup adds point-in-time restores that sit outside those policies.

For Linux servers and self-hosted workloads, BorgBackup, Restic, and Proxmox Backup Server give you immutable, encrypted, deduplicated backups without per-server fees. Pair them with offsite replication and those workloads are covered at low cost.

Test restores quarterly. A tested restore turns a backup into evidence. Record the RTO measured in real drill results rather than the vendor's marketing number, and keep the drill artifact (timestamps, screenshots, ticket reference) in the same evidence folder you'll hand to the auditor.

### Vulnerability scanning and patching

Patching is half a security control and half an operations workflow. Action1, NinjaOne Patch Management , and Kaseya VSA handle third-party patching across Windows fleets. Microsoft Intune covers OS and Microsoft 365 apps natively if you're already in that environment. Atera bundles patching with RMM, which works for shops that don't want a separate console.

For vulnerability scanning specifically, Tenable Nessus is the historical default. Qualys VMDR, Rapid7 InsightVM, and Tenable.io cover the cloud-managed end. Greenbone's OpenVAS is the open-source option; it's slower and noisier than commercial scanners but free and capable for compliance-style scans.

Pick one tool per function and chain them on one schedule. A vulnerability appears in the scanner; the patch manager addresses it; the report ties to the same CVE list. Scanning, patching and reporting on the same cadence keeps the evidence consistent and the patch backlog visible.

For SMB clients, scanning quarterly with monthly patching is a defensible baseline. Cyber insurance applications ask about patching cadence, so track patch ratings against a 30-day SLA; our cyber insurance requirements guide covers what carriers ask.

### A sample stack and budget allocation

A 1,000-endpoint book with 50 clients is a useful reference shape. The split below assumes mid-tier commercial tools where it counts and open source where it makes sense. The figures are planning estimates for budgeting; check current quotes before pricing a service.

| Layer | Tool example | Cost per endpoint/month | Share of security budget |
| --- | --- | --- | --- |
| EDR plus Managed SOC | Huntress | $5 to $7 | 30% |
| SIEM (co-managed) | Blumira | $4 to $8 | 20% |
| MFA plus Identity | Duo with Entra P1 | $3 to $6 | 15% |
| DNS plus Web filtering | DNSFilter | $1 to $2 | 8% |
| Backup (BCDR plus M365) | Datto with Veeam | $5 to $10 | 18% |
| Patching plus Vuln scan | Action1 with Nessus | $2 to $4 | 9% |

Total runs roughly $20 to $37 per endpoint per month before margin, which sets a floor on what you can charge for a managed security service. Pricing the service at a 30% margin or higher leaves room to absorb a mid-year price change from one vendor.

The other lever is consolidation. An MSP stack audit surfaces duplicate spend, usually in EDR, RMM-bundled patching, and SaaS backup overlapping with BCDR. Clearing those overlaps frees budget for the layers that tend to run thin, such as DNS filtering, email security and vulnerability scanning, without a price increase to clients.

For broader procurement work, reducing IT costs covers the contract side.

The security budget for a 1,000-endpoint book split six ways, from EDR at 30 percent to DNS filtering at 8

### How to consolidate MSP security tools

Consolidation works layer by layer, and five steps keep it orderly:

Inventory. List every agent, console and contract per client, with renewal dates.

Map. Assign each tool to one of the six security layers, or to RMM, PSA and documentation.

Flag overlaps. Two EDR agents on one device, patching in both the RMM and a separate tool, and Microsoft 365 backup bought twice are the usual finds.

Pick one owner per layer. Weigh the response model, the multi-tenant console and evidence export alongside price.

Retire at renewal. Time each removal to the contract end date so no client loses coverage in between.

An MSP security platform that covers several layers in one console cuts the swivel-chair work between alert, ticket and audit log. EDR and backup usually stay with dedicated vendors, so center the platform on RMM, PSA, patching and log collection and connect the rest. Our MSP platform guide covers how those pieces fit together.

### Security budget samples for in-house IT teams

An internal IT team runs the same six layers without the MSP margin, and its security budget gets measured as a share of IT spend. The IANS security budget benchmark found security averaged 10.9% of IT spending in 2025. Avasant puts the security line at 5.4% of the average IT budget, and the two count spend differently.

The planning estimates above translate into annual tooling budgets by device count:

| Managed devices | Annual tooling at $20 per device a month | Annual tooling at $37 per device a month |
| --- | --- | --- |
| 100 | $24,000 | $44,400 |
| 500 | $120,000 | $222,000 |
| 1,000 | $240,000 | $444,000 |

Check the result against your share of IT spend. A team with a $1.5 million IT budget lands at $81,000 for security at 5.4% and $163,500 at 10.9%, so a 500-device stack at the low end of the range fits between the two. Staff time for alert review, or a co-managed SOC that covers it, sits on top of the tooling line.

Our IT budget planning template breaks the security overlay out line by line.

### Compliance mapping for HIPAA, CMMC, and SOC 2

Auditors look for evidence and control coverage more than a stack diagram. Map each layer to the framework before you buy.

For HIPAA, the Security Rule requires access controls (MFA, role-based access), audit controls (SIEM with multi-year retention), integrity controls (file integrity monitoring, often via EDR), and contingency plans (backup with documented RTO and RPO). The technical safeguards section reads like an MSP security stack checklist.

CMMC 2.0 Level 2 applies to defense contractors that handle Controlled Unclassified Information. The 110 NIST 800-171 controls map closely to the stack: AC family to identity and MFA, AU family to SIEM, IR family to EDR plus SOC, MP and SC families to encryption and DNS controls, and RA plus SI families to vulnerability scanning and patch management.

SOC 2 Type II is the broadest. The Trust Services Criteria (Security, Availability, Confidentiality) map to the same controls but with an emphasis on continuous monitoring evidence: alert logs, ticket trails, change management. Consistent evidence carries as much weight as the controls themselves. Document everything the SIEM alerts on, even non-events; a quiet log with timestamps is still evidence.

Disclosure: Flamingo, which publishes this guide, builds OpenFrame.

OpenFrame is open, AI-native infrastructure for IT and security that covers large areas of SIEM and SOC work alongside RMM, remote access, patching, PSA and documentation, so ticket trails and security telemetry sit in one place at audit time. It is not an EDR, antivirus or backup tool, so those layers stay with the vendors you already run. Its AI agents, Fae and Mingo, take on routine support requests and IT operations tasks so technicians spend their time on decisions. Pricing is $1 per device a month with 10 million AI tokens included, with a 14-day free trial.

Five stack layers mapped across HIPAA, CMMC 2.0 Level 2 and SOC 2 Type II controls

A stack that produces that evidence on demand turns each audit into a reporting task.

### Kristina Shkriabina

Content Marketing Lead

Ohayo\! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.

### Related Content

### Blog Posts

### Product Releases

### Podcasts

### Webinars

### Case Studies

### Events

### Onboarding Guides

Loading related content

### Frequently Asked Questions

/blog/msp-security-stack

### MSP security

### What's the minimum viable MSP security stack for a small client?

EDR with managed SOC, MFA on every account, DNS filtering and immutable backup. At the planning estimates in the budget table, those four layers run about $14 to $25 per endpoint per month. Each one covers a different step: the endpoint, the credential pivot, the delivery channel and the recovery floor.

### How is open source different from free for an MSP security stack?

Open source means you can read the code, modify it and self-host without vendor approval. Free can mean a free tier, freemium or a community edition with feature gates. Wazuh, Greenbone's OpenVAS and Velociraptor are open source. Check the license of any free tool before building a service on it, since licenses can change between versions.

### Which MSP security tools count for cyber insurance applications?

Cyber insurance applications ask about MFA on admin, email and remote-access accounts, EDR on every endpoint, offline or immutable backups and documented patching SLAs. Some carriers also ask about phishing-resistant MFA on privileged accounts and an incident response plan with RTO and RPO targets.

### Should an MSP run its own SIEM or buy co-managed?

If you have a tier-2 security analyst and a tuned ruleset, self-hosted Wazuh costs less in licensing and gives you more control. Without that analyst, a co-managed SIEM such as Blumira, Arctic Wolf or ConnectWise SIEM costs more per endpoint and takes on 24/7 alert triage. Compare the co-managed quote with the cost of the analyst hours you would otherwise staff.

### How does email security fit into the MSP security stack?

Email is a delivery channel, like DNS and the web. Exchange Online Protection, Microsoft Defender for Office 365 and Google Workspace's built-in protections cover the baseline; Proofpoint Essentials, Check Point Harmony Email (formerly Avanan) and Material Security add advanced phishing and business email compromise detection. Budget for it next to DNS filtering, since both guard the first click.

### What's the right way to track MSP security stack ROI?

Three metrics work: incidents prevented (alerts triaged before escalation), incidents contained (mean time to respond) and audit findings (counted, not weighted). Each vendor dashboard shows part of that picture, so a quarterly internal report that pulls all three together gives clients one view.

### What security tools should an MSP standardize across clients?

One tool per layer: EDR with a managed SOC, MFA and identity, DNS filtering, backup for servers and Microsoft 365, and patching with vulnerability scanning, plus a SIEM where client size or compliance calls for it. Standardizing keeps onboarding, alert handling and audit evidence the same across every tenant, and it gives you one price sheet for the security service.

### How do you consolidate MSP security tools into fewer consoles?

Inventory every agent and contract per client, map each tool to a layer, flag the overlaps and pick one owner per layer. Retire the duplicates at contract renewal so coverage never lapses. A platform that combines RMM, PSA, patching and log collection removes several consoles at once, while EDR and backup usually stay with dedicated vendors.

### What security stack does an in-house IT team need?

The same six layers an MSP runs: EDR, SIEM or managed detection, MFA, DNS filtering, backup, and vulnerability scanning with patching. At the planning estimates in this guide, tooling runs $20 to $37 per device a month, and the IANS benchmark puts security at 10.9% of IT spending in 2025. Teams without 24/7 staff can pair EDR with a managed SOC.

### About OpenFrame

### What's included in OpenFrame? Does it integrate with my existing tools?

OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.

Still deciding?

Ask Mingo answers from our docs and customer stories.

[BACKUP](https://www.flamingo.run/blog?tags=backup)

[BEST PRACTICES](https://www.flamingo.run/blog?tags=best-practices)

[COMPLIANCE](https://www.flamingo.run/blog?tags=compliance)

[Kristina Shkriabina](https://www.flamingo.run/authors/kristina-shkriabina)

[Subscribe to Flamingo Blog (RSS)](https://www.flamingo.run/blog/rss.xml)

[email security](https://www.flamingo.run/blog/email-security-solutions)

[endpoint security guide](https://www.flamingo.run/blog/endpoint-security)

[ThreatDown review](https://www.flamingo.run/blog/threatdown-review)

[SOC as a service](https://www.flamingo.run/blog/soc-as-a-service)

[Huntress review for MSPs](https://www.flamingo.run/blog/huntress-review-for-msps)

[Wazuh review for MSPs](https://www.openmsp.ai/blog/wazuh-review-for-msps)

[cybersecurity frameworks list](https://www.flamingo.run/blog/cybersecurity-frameworks-list)

[Microsoft study of MFA](https://arxiv.org/abs/2305.00945)

[Patch Management](https://www.flamingo.run/blog/best-patch-management-software)

[Greenbone's OpenVAS](https://www.openmsp.ai/blog/openvas-vulnerability-scanner)

[cyber insurance requirements](https://www.flamingo.run/blog/cyber-insurance-requirements)

[MSP stack audit](https://www.flamingo.run/blog/msp-stack-audit)

[reducing IT costs](https://www.flamingo.run/blog/how-to-reduce-it-costs)

[MSP platform guide](https://www.flamingo.run/blog/what-is-msp-platform)

[IANS security budget benchmark](https://www.ians.com/insights/ciso-leadership/2025-security-budget-benchmark-report)

[IT budget planning template](https://www.flamingo.run/blog/it-budget-planning-template)

[SIEM and SOC](https://www.openmsp.ai/vendor/openframe-siem)

## Additional pricing (as published)

Flamingo Raises $4.5M Seed Round · Led by Vertex Ventures, bringing total funding to $6.7M to build the open, AI-native layer for IT and security.