How to Compare Asset-Based and Ingestion-Based MDR Pricing

· Original article ↗

Summary

A practical guide to comparing MDR proposals by assets, data sources, retention, investigation and response scope, and how costs may change as an organization grows.

Key points

  • Compare providers using the same asset inventory, required data sources, retention needs, response expectations, and annual budget.
  • Asset-based pricing depends on the defined number of assets; ingestion-based pricing may vary with data volume, included allowances, measurement rules, and retention costs.
  • Request evidence about included data sources and exclusions, collected events and fields, detection dependencies, investigation history, response responsibilities, and cost changes as usage grows.
  • During a proof of concept, test a relevant threat scenario and ask the provider to show the detection, supporting records, evidence gathering, and response—including what happens if a required source is unavailable.
  • Rapid7 says its MDR uses asset-based pricing with unlimited ingestion, 13 months of log retention, and unlimited incident response; the article advises confirming coverage and terms in the proposal.
  • Alan Simpson described Keyloop increasing ingestion from about 250 GB per day with Splunk to 1.4 TB per day with Rapid7, and retention from about 90 days to 13 months; the article says these figures alone do not establish comparable cost savings.

Article Details

Topic
Comparing asset-based and ingestion-based MDR pricing, including data collection, retention, response scope, and cost predictability.

People

Vendors

Products

Related Articles