How we source XDR pricing figures
A vendor price on this site is the vendor's own published figure, linked where it appears and dated to the day we checked it. Where a vendor publishes no price, the page says so and explains how the vendor quotes instead; it does not substitute an estimate of someone else's private price. Worked examples are arithmetic on a stated rate, so you can redo them with the rate in your own quote.
Sources
- Vendor pricing pages. CrowdStrike (crowdstrike.com/pricing), SentinelOne (sentinelone.com/platform-packages) and Microsoft (microsoft.com security and Microsoft 365 pricing) publish list prices, and those are the figures we use for them.
- Public procurement and marketplace listings. AWS Marketplace and UK G-Cloud listings, cited by listing and check date, where a vendor or reseller files a price there.
- Vendor documentation. Licensing and entitlement documents for structure (tiers, credits, retention, what each package includes), for vendors that publish no price.
- Standards and regulators. PCI DSS, HIPAA, SOX and similar texts for retention requirements. The full list is on /sources.
What we deliberately do not publish
- Specific customer contract values. Where a specific organisation's XDR contract value is known to us through public reporting, it is described in band terms only.
- Vendor-private discount math. Negotiated discounts are commercially confidential and vary by deal, so we do not publish a discount percentage. Treat a published list price as a ceiling and bid vendors against each other.
- Side-by-side feature grids. We publish positioning notes per vendor but not feature grids. XDR feature parity changes monthly; static grids are stale within weeks.
Update cadence
Site values update only when the underlying reality changes. Triggers:
- Major vendor pricing-model change (e.g. per-endpoint to per-identity, telemetry-source repackaging)
- New entrant publishing pricing materially below the existing band
- Major XDR acquisition or product retirement event
- Vendor-roadmap changes that materially shift the EDR-vs-XDR boundary
Cosmetic date bumps are not made.
Editorial position
This site is operated by Digital Signet, an independent AI-development studio. Digital Signet does not sell XDR software, does not run a managed-XDR practice, and does not act as a vendor reseller. Any sponsorship or affiliate placement is clearly labelled and never affects the cost data, rankings, or calculations. See /about for the operator and the wider network.
Editorial direction is set by the Digital Signet editorial team. Drafts are produced via Digital Signet's autonomous AI development methodology and reviewed against the editorial framework before publication.
Contact
For methodology questions, corrections, or scenarios that don't fit cleanly: [email protected].