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.
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.