Security leaders evaluating Managed Detection and Response (MDR) services often face a complex choice between two primary pricing models: asset-based and ingestion-based. While both approaches aim to provide security monitoring, they rely on fundamentally different metrics that can significantly alter the scope of protection, data visibility, and long-term costs. A direct comparison requires moving beyond simple per-unit pricing to understand how each model handles data volume, log retention, and the operational responsibilities of the provider.
Asset-based pricing ties costs to a defined population of systems, such as workstations, servers, and cloud resources. This model is often favored for its budget predictability, as the cost is linked to the size of the infrastructure rather than the amount of data generated. However, organizations must carefully define how a provider counts these assets and identify any limits on the telemetry sources included in the base price. For example, Rapid7 defines an asset as any physical or virtual endpoint or server running a supported operating system, offering a model that includes unlimited data ingestion to avoid penalizing customers for higher telemetry volumes.
Conversely, ingestion-based pricing scales costs according to the volume of data processed or stored. This model requires organizations to account for daily data allowances, the method of measuring billable volume, and the potential for cost spikes as log generation increases. While this approach can be flexible, it often introduces uncertainty regarding retention periods and search capabilities, as these features may be tied to the total amount of data stored. Organizations must determine how these models handle growth, such as through mergers or acquisitions, where data profiles can shift rapidly.
A critical component of any MDR evaluation is the distinction between raw log ingestion and the actual investigation and response services provided. A simple SIEM ingestion fee cannot be equated to an MDR subscription that includes active threat hunting, containment, and eradication. To perform a like-for-like comparison, security teams should provide each prospective vendor with an identical set of requirements, including the specific asset inventory, necessary data sources, required retention periods, and expected response outcomes.
Visibility gaps often arise when budget constraints force organizations to limit the collection of high-volume logs, such as NetFlow, DNS, or web application firewall data. When these sources are excluded, the effectiveness of security investigations and AI-assisted detection tools can be severely diminished. For instance, transitioning to a model that allows for higher daily ingestion can provide a more comprehensive view of an environment, as seen in cases where organizations moved from limited, volume-dependent retention to standardized, multi-month storage periods.
To assess the true value of an MDR proposal, organizations should request a demonstration that walks through a specific threat scenario. This exercise should verify which data fields are actually collected, how they are normalized, and how the provider uses that context to link suspicious activity to specific users or systems. It is also essential to confirm the scope of the provider’s responsibilities, particularly regarding what actions the security team is expected to perform versus what the vendor handles during an incident.
Finally, long-term cost stability should be a central part of the negotiation. Organizations should ask for written calculations that show how the bill would change under different growth scenarios, such as adding new cloud workloads or enabling previously excluded log sources. In the case of asset-based contracts, some providers, such as Rapid7, offer renewal caps to limit price increases over the term of the agreement. By documenting all assumptions—including implementation effort, licensing requirements, and the division of labor—security leaders can ensure that their chosen MDR partnership aligns with both their operational needs and their financial constraints.





