Skip to main content
Comparisons · Five vendors, sourced from their own published material

How ShadowMap compares to the vendors you are actually evaluating.

Two things decide these evaluations, and neither of them is a feature grid. The first is where a platform sits on two axes: how much of your external estate it watches, and how far past “we found it” it is able to go. The second is how the requirement was written before anyone was invited, which settles some of these before a demo is booked.

Both maps are below.

The first map

Coverage is one axis. What happens next is the other.

Most category maps plot one dimension and call it a landscape, which flatters whoever covers the most ground. Two axes are needed here, because a platform that watches everything and only ever tells you about it is a different purchase from one that watches less and acts. Horizontally: how much of the external estate is under coverage. Vertically: how far a finding travels. Observed, scored, routed to somebody, or tested and removed.

Where the five vendors sit on external coverage and depth of action
VendorBreadth of external-risk coverage Depth of actionNote
Cyble Several exposure surfacesRoute and orchestrate Broad coverage
CloudSEK Several exposure surfacesRoute and orchestrate First on exposed AI
SecurityScorecard Ratings and postureRoute and orchestrate Questionnaire automation
UpGuard Several exposure surfacesRoute and orchestrate Data-leak detection
RiskRecon Ratings and postureRoute and orchestrate Published methodology
ShadowMap — us Several exposure surfacesValidate and remove Validation and removal
External risk coverage against depth of action, ShadowMap and the five vendors we meet in evaluations Positions are our reading of each vendor’s published capability as of August 2026, not a score.

On the horizontal axis, Cyble and CloudSEK sit close to us. That is the correct reading: the overlap is real across most of what we do, and both are well funded and growing. The three ratings vendors sit further left not because they are weaker but because they are instruments for a different job.

The vertical axis is where the set separates, and it separates in one place. All five alert, and several route and orchestrate properly: RiskRecon publishes vendor-visible action plans with continuous remediation verification, SecurityScorecard has an established integration surface, UpGuard automates risk workflow. None of the five publishes anything that tests whether a discovered exposure can actually be used. That is what Continuous Automated Red-Teaming does, where it is safe and authorised, and it is the reason the top of the vertical axis is otherwise empty.

The second map

The frame decides more of this than the product does

How a requirement is written determines which vendors are in the room and which capabilities get scored. The first two framings below score a comparable number and a questionnaire workflow, which is what ratings vendors sell. The last three score coverage, validation and removal.

How the requirement is framed, who else is in the room, and who leads
How the requirement is framedWho you meetWho leads
Security ratings / board scorecard BitSight, SecurityScorecard, RiskRecon, UpGuard Ratings vendors lead
The requirement is a comparable number across a vendor portfolio, which is what a ratings vendor sells. Depth of action is not scored.
Third-party risk / vendor assessment UpGuard, SecurityScorecard, RiskRecon Ratings vendors lead
Questionnaire workflow and vendor-network reach are what is scored, and both are what ratings vendors sell.
Digital risk protection / external exposure Cyble, CloudSEK Genuinely even
Comparable breadth. The decision turns on whether the buyer values validation and removal.
Attack surface management Cyble Odin, CloudSEK BeVigil Genuinely even
Comparable discovery. Origin-behind-WAF discovery and validation are the separators.
Find what attackers can reach, and prove what they can use Nobody Nobody else is in this frame
No vendor in the set combines this breadth of coverage with validation and removal.

How the requirement is framed, who else is in the room, and who leads

Security ratings / board scorecard

Who you meet
BitSight, SecurityScorecard, RiskRecon, UpGuard
Who leads
Ratings vendors lead

The requirement is a comparable number across a vendor portfolio, which is what a ratings vendor sells. Depth of action is not scored.

Third-party risk / vendor assessment

Who you meet
UpGuard, SecurityScorecard, RiskRecon
Who leads
Ratings vendors lead

Questionnaire workflow and vendor-network reach are what is scored, and both are what ratings vendors sell.

Digital risk protection / external exposure

Who you meet
Cyble, CloudSEK
Who leads
Genuinely even

Comparable breadth. The decision turns on whether the buyer values validation and removal.

Attack surface management

Who you meet
Cyble Odin, CloudSEK BeVigil
Who leads
Genuinely even

Comparable discovery. Origin-behind-WAF discovery and validation are the separators.

Find what attackers can reach, and prove what they can use

Who you meet
Nobody
Who leads
Nobody else is in this frame

No vendor in the set combines this breadth of coverage with validation and removal.

The table is for noticing which row you are in before the shortlist is drawn, not for arguing with a scoring sheet after it has been written. If the deliverable is a comparable number across a vendor portfolio, you are in the first two rows, and that is the instrument a ratings vendor sells.

The last row is the one nobody else in the set occupies, and it is a requirement you can write down: find what an attacker can reach from outside, prove which of it can actually be used, and remove what should not be there. If that is the question, the evaluation guide turns it into criteria you can put in an RFP without naming a vendor.

The removal third of that requirement is the one a scoring sheet rarely tests, so it is published, not asserted: what each provider type can actually remove, twelve of them, with the evidence each will accept and the point at which each one refuses. Ask for the same from anyone else on the shortlist.

The two groups

Five vendors, two kinds of evaluation.

The five sort cleanly into two groups that behave nothing alike in an evaluation. Treating them as one shortlist is how a scoring sheet ends up with columns that mean different things for different vendors, and how a ratings vendor gets marked down for not doing something it never claimed to do.

01 Two of the five

Broad digital-risk platforms

Who is in it
Cyble and CloudSEK. Both overlap most of what ShadowMap covers, and the overlap is real, not a marketing claim: Cyble ships nine named products across intelligence, attack surface, brand protection and endpoint, and CloudSEK covers external monitoring, mobile and API exposure, supply chain and, newly, exposed AI infrastructure.
What the evaluation feels like
A breadth conversation. Coverage maps get compared surface by surface, everybody ticks most boxes, and the shortlist is decided on things a datasheet cannot show: how a finding arrives, who acts on it, and what the second year costs. Neither of these vendors is a point tool, and an evaluation that treats them as one ends badly.
Where the decision actually turns
Whether the buyer values validation and removal. Nothing in either product line tests whether a discovered exposure can be used. That is the question that changes what a team does on Monday. If that is not being scored, the evaluation is missing the question that separates these platforms.
02 Three of the five

Security-ratings and third-party-risk companies

Who is in it
SecurityScorecard, UpGuard and RiskRecon. They sell a different instrument: a comparable score across a vendor portfolio.
What the evaluation feels like
A procurement conversation, usually already scoped. The requirement names a score, a vendor count and a board report, and the scoring sheet was written around those. Depth of action is not on the scoring sheet, so it does not measure what ShadowMap adds.
Where the decision actually turns
Whether the programme is a portfolio instrument or a first-party exposure programme. If a vendor score is the deliverable, that is what a ratings vendor sells. If the question is what an attacker can reach in your own estate and what they could actually use with it, a rating does not answer it and was never meant to.

The five pages

One page each

Each page sets out what that vendor sells and where the two products differ, sourced from the vendor’s own published material. The column below is what each vendor is known for, and the note under each row is how it positions itself and what it publishes on price.

The five vendors ShadowMap meets in evaluations
VendorWhich groupWhat they are known forWhere we differ
Cyble Digital-risk platform Broad coverage: the overlap with ShadowMap spans most capability groups Evidence over prediction: a tested key is an answer, a predicted risk is a better alert
A broad digital-risk platform spanning nine product lines and covering most of the same capability groups, not just one. Publishes no pricing anywhere.
CloudSEK Digital-risk platform AIVigil is first to market: exposed AI infrastructure, MCP servers, leaked AI credentials, vector databases, shadow AI Correlation that terminates in a tested finding, not a predicted path
AIVigil covers exposed AI infrastructure (MCP servers, leaked AI credentials, vector databases) alongside social-media data-leak monitoring. Publishes no pricing anywhere.
SecurityScorecard Ratings / TPRM Questionnaire automation, widened by two 2026 acquisitions: HyperComply and Driftnet Ratings-platform-deep, not exposure-platform-deep: four capability groups are absent from their line
Questionnaire automation with a self-serve entry rung, and TITAN as the current threat-intelligence line. Published pricing: Vendr median ~US$23,619; reported list US$25,000-50,000 (Ratings).
UpGuard Ratings / TPRM Data-leak detection: exposed storage, public repositories, exposed file services UpGuard detects; it does not validate and it does not remove
Ratings plus Trust Exchange, which answers the inbound security-assurance problem, not the outbound one. Published pricing: US$21,000/yr published list (Standard, 50 vendor slots).
RiskRecon Ratings / TPRM Asset attribution independently certified at 99.1% by a third party. Nobody else in the set has that Their published refresh cycle: asset profiles update every two weeks. Ours is continuous.
Asset attribution carries third-party certification, and the scoring methodology is published in full, so a buyer can audit how a score was reached. Publishes no pricing anywhere.

The five vendors ShadowMap meets in evaluations

Cyble

Which group
Digital-risk platform
What they are known for
Broad coverage: the overlap with ShadowMap spans most capability groups
Where we differ
Evidence over prediction: a tested key is an answer, a predicted risk is a better alert

A broad digital-risk platform spanning nine product lines and covering most of the same capability groups, not just one. Publishes no pricing anywhere.

CloudSEK

Which group
Digital-risk platform
What they are known for
AIVigil is first to market: exposed AI infrastructure, MCP servers, leaked AI credentials, vector databases, shadow AI
Where we differ
Correlation that terminates in a tested finding, not a predicted path

AIVigil covers exposed AI infrastructure (MCP servers, leaked AI credentials, vector databases) alongside social-media data-leak monitoring. Publishes no pricing anywhere.

SecurityScorecard

Which group
Ratings / TPRM
What they are known for
Questionnaire automation, widened by two 2026 acquisitions: HyperComply and Driftnet
Where we differ
Ratings-platform-deep, not exposure-platform-deep: four capability groups are absent from their line

Questionnaire automation with a self-serve entry rung, and TITAN as the current threat-intelligence line. Published pricing: Vendr median ~US$23,619; reported list US$25,000-50,000 (Ratings).

UpGuard

Which group
Ratings / TPRM
What they are known for
Data-leak detection: exposed storage, public repositories, exposed file services
Where we differ
UpGuard detects; it does not validate and it does not remove

Ratings plus Trust Exchange, which answers the inbound security-assurance problem, not the outbound one. Published pricing: US$21,000/yr published list (Standard, 50 vendor slots).

RiskRecon

Which group
Ratings / TPRM
What they are known for
Asset attribution independently certified at 99.1% by a third party. Nobody else in the set has that
Where we differ
Their published refresh cycle: asset profiles update every two weeks. Ours is continuous.

Asset attribution carries third-party certification, and the scoring methodology is published in full, so a buyer can audit how a score was reached. Publishes no pricing anywhere.

There is a sixth comparison that names no competitor at all. Assembling coverage of this shape out of point tools has a published price, and the arithmetic is on its own page, built from published list prices and transaction medians.

Four further pages cover vendors that appear on international shortlists, each written from that vendor’s own public pages with the sources listed: Bitsight, Recorded Future, ZeroFox, SOCRadar.

Why these five

The vendors enterprises shortlist alongside ShadowMap

These are the five vendors that appear most often opposite ShadowMap in enterprise evaluations. Evaluating a vendor that is not listed? Ask us for a direct comparison.

Where these comparisons come from As of August 2026
  • The five vendors are the ones ShadowMap meets in live evaluations, taken from our own records.
  • Every figure comes from the vendor’s own published material: product pages, pricing pages, methodology documents and listings they cite themselves.

The fastest way to settle this is your own estate

One apex domain, two business days, a written account of what is reachable from outside. No call, no procurement, and the result is yours whichever platform you end up buying.