Lesson 8 of 8
Building the business case
The strongest business case for validation is built from your own pilot results. Published prices and what the tool replaces fill in the rest.
What it costs, from published figures
Most vendors in this category quote rather than publish prices. A few list figures on cloud marketplaces or their own sites, and those give a range for a first budget. All figures below were read on 3 November 2026; each vendor note links its source.
| Listing | Published price |
|---|---|
| AttackIQ Flex, monthly unlimited testing (vendor site) | USD 4,995 |
| Cymulate Exposure Validation, 1,000-scenario package (AWS Marketplace) | USD 13,000 per 12 months |
| AttackIQ Flex, 100 credits (AWS Marketplace) | USD 15,000 per 12 months |
| Validato Starter Edition (vendor-supplied on G2) | USD 20,000 per year |
| Horizon3.ai NodeZero Core Package, 500 assets (AWS Marketplace) | USD 25,000 per 12 months |
| Pentera (AWS Marketplace SaaS contract) | USD 120,000 per 12 months |
| Validato Enterprise Edition (vendor-supplied on G2) | from USD 148,500 per year |
| Picus Security Control Validation entry bundle (AWS Marketplace) | USD 150,000 per 12 months |
| XM Cyber CEM, Medium Enterprise Network (AWS Marketplace) | USD 350,000 per 12 months |
The spread is wide because the listings are not like for like. A 1,000-scenario package, a credit bundle, an asset-count licence and an enterprise network contract buy different things. Use the figures to set an order of magnitude, not to compare vendors. SafeBreach, SCYTHE and Mandiant Security Validation publish no prices.
Add the costs that do not appear on a price list: staff time to run the tool and act on results, agent deployment, and any professional services for onboarding. For many teams the staff time is larger than the licence.
What it replaces or reduces
Validation rarely replaces a budget line outright, but it changes several.
Third-party penetration tests. Automated pentesting can take over the routine, repeatable part of annual internal tests, leaving human testers for scoped, harder work. Ask your current testing firm what share of its report covers findings a tool would have found.
Red team time. Breach and attack simulation automates the technique-by-technique coverage that red and purple teams find slow to repeat.
Wasted patching effort. If validation shows that a share of high-severity findings are not reachable or are blocked by existing controls, the hours saved on those patches are a real saving. Your pilot will tell you roughly what that share is in your environment.
Tool consolidation decisions. Evidence of which controls actually work is the best input to a decision about which ones to renew.
Build the case from the pilot
A pilot of two to four weeks, scoped as in lesson 4, produces the evidence the case needs. Bring four things from it:
- The most serious finding, with evidence: a reachable crown-jewel asset, or a key control that missed a common technique.
- One fix made during the pilot and the retest that confirmed it.
- The share of top-ranked scanner findings that validation showed were blocked or unreachable.
- A drift event, if one occurred, with its cause.
Four concrete results from your own environment will carry more weight than any industry statistic. They also answer the question budget holders ask most: what would we have missed without this?
Frame it as a programme
Present validation as the evidence stage of the exposure programme your organisation already runs, not as another tool. Lesson 3 explains where it sits. Tie the request to decisions that are already being made: which findings to fix first, which controls to renew, how to answer the auditor's question about control testing.
Regulation helps in some sectors. Validato, for example, aims its product at evidence for the EU's DORA and NIS2 rules. If your organisation falls under either, check what testing evidence your compliance team already has to produce and how it is produced today.
Answer the objections in advance
"It will break production." Bring the vendor's written safety controls and your rules of engagement from the pilot.
"We already have a pentest." Show the drift event or the retest. A yearly test cannot catch either.
"We cannot staff it." Price a managed option alongside the platform. Lesson 2 and the managed validation note cover the trade-off.
"Which vendor is best?" The honest answer is the one whose documented type fits your question and whose pilot result you trust. That is what the finder is for.
Compare cost over three years
A one-year price hides most of the cost. Multi-year terms, renewal uplifts, extra modules and added agents or assets change the total, and some vendors charge one-time onboarding fees; SafeBreach's licensing, for example, includes a one-time onboarding fee according to its Gartner Peer Insights product information. Ask each vendor for a three-year figure at your expected size, in writing, with what triggers a price change. Add your own staff time for the same three years. It is also the figure finance will ask for.
End of the course
You now have the vocabulary and the questions. Run the finder, print the worksheet for your result, and take it into a pilot.
Previous: Metrics that hold up. That is the end of the course. Run the finder with what you now know.