MSSP pricing: six models, four drivers, one honest comparison.
Managed security service providers charge per device, per user, per asset, on data volume, in tiers, or on retainer, and most quotes mix two of those. The model matters less than the scope behind it. Here is how to read a quote, and how to put two of them side by side.
MSSPs use six pricing models: per device or endpoint, per user, per asset, data volume (daily SIEM ingest), tiered packages, and retainer or hourly billing for incident response and advisory work. Many quotes combine two, such as endpoints per device and identity per user.
Four drivers move the number more than the device count: whether the provider only monitors or is permitted to respond, the coverage hours and how they are staffed, whether the provider operates your tools or licenses its own, and how much log data is ingested and retained.
Vijilan prices per asset per month: endpoints, users, servers and firewalls are each assets, cloud and identity sources are priced per user, and partners get volume discounts across their whole book. Rates are released after partner verification rather than published.
Six ways an MSSP can charge you.
Per device or per endpoint
The most common meter. Simple to quote, and simple to misread: check whether servers, virtual desktops and cloud workloads count as one device each, and whether firewalls and network gear are in the count at all.
Per user
Favors organizations where each person runs several devices. Often how identity and email protection is priced even when endpoints are priced per device, so one quote can quietly use both meters.
Per asset
A blended meter where endpoints, users, servers and firewalls are each counted as assets at their own rate. It is how Vijilan prices, because it follows what is actually monitored rather than forcing every source into one unit.
Data volume
Priced on daily ingest into a SIEM. Common where log monitoring is the core of the service, and the meter most likely to grow faster than the business does. Retention period is the second half of the same number.
Tiered packages
Named tiers that bundle a set of services at a per-unit rate. Useful for comparing like with like inside one provider, and hard to compare across providers, because two tiers with the same name rarely contain the same things.
Retainer or hourly
Used for incident response, forensics and advisory work rather than continuous monitoring. Worth knowing whether a breach response is inside the monthly fee or billed on top, before you need one.
Four drivers that matter more than the device count.
Monitor-only or respond
An MSSP that watches and alerts is a different operational commitment from one contractually able to isolate a host or disable an account. The second costs more to run and is worth more on the night it matters.
Coverage hours
Business hours, extended, or a staffed 24/7 rotation. All three get described as round-the-clock somewhere. Ask who is awake at 3am and how many of them there are.
Whose tools
Some providers operate the security stack you already own; others bring and license their own. Those are different quotes, and comparing them without normalizing is the most common mistake in this evaluation.
Log volume and retention
If a SIEM is in scope, how much data goes in and how long it stays searchable. Compliance requirements usually set the retention period, and they usually arrive late in the evaluation.
Put every quote on the same meter first.
Convert each quote to the same unit for your estate: total monthly cost for your actual endpoints, users, servers and firewalls. Then ask every provider the same four questions. Which actions may you take without contacting us. Who is staffed at 3am. Are the security tool licenses included. How much log data is retained, and for how long.
A quote that is cheaper because it only monitors, runs business hours, or excludes the license you will have to buy anyway is not a better price. It is a different product.
MSSP pricing, answered.
How much does an MSSP cost?
It depends far more on scope than on headcount. The same organization can receive quotes that differ several times over because one provider monitors and alerts, another responds, one licenses its own tooling and another operates yours. Vijilan does not publish rates: they are released after partner verification, because partner economics do not belong on a public page. What is worth publishing is how the number is built, which is what this page covers.
What are the common MSSP pricing models?
Six: per device or endpoint, per user, per asset (a blended meter covering endpoints, users, servers and firewalls), data volume for SIEM-based services, tiered packages, and retainer or hourly billing for incident response and advisory work. Many quotes combine two or more, for example endpoints per device and identity per user.
How does Vijilan price managed security?
Per asset per month. Endpoints, users, servers and firewalls are each priced as assets, cloud and identity sources are priced per user, and partners get volume discounts across their whole book. Partners buy at a partner rate and an end customer buying direct pays a different one. ThreatRespond™ operates over the security tools you already own, so an existing EDR license stays yours and is not in our number. ThreatDefend™ includes CrowdStrike Falcon® licensed, deployed and operated end to end.
Why do MSSP quotes vary so much?
Because they are usually pricing different scopes. Response authority, coverage hours, whether the platform license is bundled, and how much log data is retained each move the number more than the device count does. Normalize those four before comparing totals.
Is an MSSP cheaper than building an in-house SOC?
For almost every organization below enterprise scale, yes. A genuinely staffed 24/7 rotation is several full-time salaries plus training, tooling and the management to keep it running. A managed service is cheaper because that cost is shared across every organization the SOC covers.
What is the difference between MSSP and MDR pricing?
MSSP pricing often centers on monitoring and device management, sometimes priced on data volume. MDR pricing centers on detection and response, priced per endpoint, user or asset. The bigger difference is what you are buying: an alert, or an attack stopped. The MDR pricing guide covers that side in detail.
What should be in the contract?
The actions the provider may take without contacting you, the coverage hours and how they are staffed, what is excluded from the monthly fee (incident response is the usual one), what happens to your data if you leave, and whether evidence from an incident is yours.
How do we get a real number?
The pricing wizard takes a verified work email and routes MSPs to the partner portal and enterprises to a scoped conversation. If you are running a formal procurement, send the RFP instead and a security engineer will map every requirement to a service.
Bring your asset count
and how much authority you want to delegate.
Those two answers shape the quote more than anything else. The pricing wizard routes MSPs to partner rates and enterprises to a scoped conversation, with no sales call to get started.