Biometric Identity Verification RFP Checklist: Requirements, Scoring and Red Flags
Ask any vendor whether its system supports biometrics and the answer is yes. That answer cannot be scored. The biometric identity verification guide covers what to require. This page is how to run an identity verification request for proposal (RFP) so every answer can be checked, phase by phase, from writing the RFP to signing the contract. The full checklist sits at the end in one block you can paste.
What factors should be considered when comparing identity verification vendors?
Compare vendors on evidence you can check, not features they list. Eight factors decide most selections:
- The identity assurance level (IAL) the service is certified to, and against which revision of NIST SP 800-63.
- Independent test reports for presentation attack detection (PAD), plus a written description of the fraud controls against injection attacks, deepfakes and synthetic identities.
- Independent results for the matching algorithm, including demographic results where applicable.
- Who controls the capture device, and who supervises the session.
- Document authentication that reads the chip, not only an image of the page.
- Whether the session record would satisfy an assessor.
- Implementation, integration with your existing systems, and throughput.
- Data handling, price and exit terms.
Every factor should map to a listing, a lab report or a live test, not a slide. The guide explains what each one means.
Before the RFP: set the assurance level and write the requirements
State your target assurance level in the RFP itself. Do not let offerors choose it. Then paste requirements language. “Shall” is mandatory: a missing item disqualifies the offer. “Should” is desirable: it moves the score only. Make a requirement mandatory only when your program actually needs it, and ask for every attachment in the proposal itself, so nothing has to be collected after proposals are due.
Assurance and certification
Level Requirement Attachment Shall The offeror shall state the identity assurance level its identity proofing service is certified to, the NIST SP 800-63 revision assessed and the certifying body. Attach: the public listing URL and scope line. Shall Where fingerprint capture is in scope, the offeror shall identify each capture device by model number. Attach: the FBI Certified Products List entry per model. Should The offeror should state a date for assessment against SP 800-63 revision 4. Attach: a signed schedule. Capture and attack resistance
Level Requirement Attachment Shall / should Where remote collection is in scope, the offeror shall provide presentation attack detection results for each modality proposed. For attended collection, make the same report a should. Attach: the full ISO/IEC 30107-3 report from an accredited lab. Shall The offeror shall describe how the system confirms media came from a genuine sensor. Attach: a technical description of injection defenses. Should The offeror should provide independent test results for those injection defenses, such as testing against CEN/TS 18099. Shall / should The offeror shall name the face and iris matching algorithms for each modality in scope and should attach independent results, such as NIST FRTE or IREX, including demographic results where applicable. Shall Where passports are in scope, the offeror shall read the machine-readable zone (MRZ) and the RFID (NFC) chip and validate the chip’s certificates. Where PIV cards are in scope, the offeror shall read the chip and validate its certificates. Supervision and evidence
Level Requirement Attachment Shall / should Where your program requires attended or supervised proofing, as IAL3 and PIV issuance do, the offeror shall describe who supervises each session, their training and what they can override. For an IAL2 program without that requirement, make it a should. Attach: the training outline and a sample override log. Shall The offeror shall produce an exportable, tamper-evident record of each session. Attach: a redacted sample. Should The offeror should support a trained operator at a central location connected to an issuer-controlled station, the supervised remote model in FIPS 201-3 Section 2.7.1. Should The offeror should offer an alternate path, at the same assurance level, for applicants who cannot present a functional biometric. Data handling
Level Requirement Attachment Shall The offeror shall state what is stored (templates or images), for how long, how it is encrypted, who holds the keys and where it resides. Attach: a data flow diagram and retention schedule. Shall The offeror shall state whether customer data trains any model, and list all sub-processors with locations. Attach: a signed statement and the list. Should The offeror should delete an individual’s data on request and prove it. Implementation and integration
Level Requirement Attachment Shall The offeror shall describe how verified identities and credential bindings reach your identity management system (IDMS), physical access control system (PACS) and HR system. Attach: interface documentation. Shall The offeror shall state its expected failure-to-enroll rate, abandonment rate and throughput: sessions per station per hour, or completed sessions per hour for a remote flow. Attach: the basis for each. Should The offeror should provide an implementation plan with timeline, staffing and responsibilities. If you are a federal buyer, add these
Where they apply, ask for the following reference documents:
- GSA FIPS 201 Approved Products List status of any PIV card or card reader in scope. GSA no longer tests enrollment stations.
- The FedRAMP authorization or ATO path for any cloud component.
- The fingerprint submission path for background investigations.
- Section 508 conformance documentation.
- Relevant documents in support of your Privacy Act system of records notice and privacy impact assessment.
When responses arrive: check each answer yourself
Never score a certification from a datasheet. Open the source. The certifications section of the guide explains what each list proves; this is how to read the evidence.
Kantara Trust Status List
Find the service by name and record four fields: assurance level, SP 800-63 revision, service type and scope line. “All applicable criteria in scope” means the full set for that level was assessed. “Partial Service, not all applicable criteria in scope” means the listing covers part of the service. For a Component Service, it describes that component’s scope, not a lower grade. The listing does not say which criteria were out of scope, so do not guess: ask the offeror whether the scope covers the part of the process you are buying.
For example, NextgenID’s entry records IAL3; NIST SP 800-63-3; Component Service; and the scope line “Partial Service, not all applicable criteria in scope.” Evaluate every offeror’s entry in the same way.
ISO/IEC 30107-3 report
Check the lab’s accreditation, the modality, the attack types and the impostor attack presentation accept rate (IAPAR). For remote collection, SP 800-63A-4 Section 3.11 calls for testing to ISO/IEC 30107-3:2023 with an IAPAR below 0.07. The report does not test injection attacks.
FBI Certified Products List
Search the exact model number. Appendix F covers fingerprint image quality only, not liveness, face or iris performance, or the proofing process.
NIST FRTE and IREX
Find the named algorithm in NIST’s face (FRTE) or iris (IREX) results, confirm the tested version matches the proposed one, then read its demographic results.
Red-flag answers
These answers are not evidence. If the named attachment is not in the proposal, score that item as missing.
Answer you receive Why it fails Ask for instead “NIST compliant” NIST publishes guidelines; it does not certify vendors The list, level and revision “IAL3-ready” No list records it What the listing shows today A vendor-wide HSPD-12 certificate No vendor-wide HSPD-12 certificate exists What was tested, and by whom “Certified” with no list or lab Uncheckable The listing URL or lab report A liveness score as injection defense An injected stream can look live The written injection defense No answer on training with customer data A data gap you will own A signed statement One answer is a gap, not a red flag: a revision 3 listing with no date for revision 4. Many certifications in force today were assessed against revision 3. Score it as partial and put the revision 4 date in the contract.
Score the responses in two stages
Stage 1, the gate. Check that every “shall” item and its attachment is in the proposal. A missing item disqualifies the offer.
Stage 2, the technical score. For offers that pass the gate, score each row 2 (pass), 1 (partial) or 0 (fail) on the quality of the evidence. Divide each row’s score by 2, multiply by its weight and add the rows, for a total out of 100. Write a definition for each cell before proposals arrive, and have every scorer use the same packet and demo results.
Requirement Pass (2) Partial (1) Fail (0) Weight IAL2 Weight IAL3/PIV Certification Listed at target level and revision, scope covers what you buy, revision 4 date Revision 3 with no date, or scope unclear Listed below target level 10 15 Presentation attack detection Accredited report for every modality; IAPAR below 0.07 where remote Some modalities, or IAPAR not stated Report from an unaccredited lab or self-test 15 10 Injection defense Written method, independent test results, demo attempt caught Written method, demo attempt caught Demo attempt passes 15 15 Matching algorithm Independent results for the proposed version, demographics included Results for an older version, or no demographics No independent results 15 10 Chip reading Certificates validated live in the demo Validation documented, not shown live Read fails in the demo 5 10 Supervision Trained operator, logged overrides, alternate path Overrides not logged, or no alternate path Operator cannot override or explain a decision 5 15 Session record Tamper-evident, complete, timestamped, exported live Complete but not exported live Missing items an assessor would request 10 10 Data handling Provable deletion, no training on customer data, sub-processors named Deletion not provable Customer data trains models with no opt-out 15 10 Implementation and integration IDMS, PACS and HR interfaces documented, dated plan Interfaces documented, no plan Undefined custom work 10 5 CertificationWeight IAL210Weight IAL3/PIV15- Pass (2)
- Listed at target level and revision, scope covers what you buy, revision 4 date
- Partial (1)
- Revision 3 with no date, or scope unclear
- Fail (0)
- Listed below target level
Presentation attack detectionWeight IAL215Weight IAL3/PIV10- Pass (2)
- Accredited report for every modality; IAPAR below 0.07 where remote
- Partial (1)
- Some modalities, or IAPAR not stated
- Fail (0)
- Report from an unaccredited lab or self-test
Injection defenseWeight IAL215Weight IAL3/PIV15- Pass (2)
- Written method, independent test results, demo attempt caught
- Partial (1)
- Written method, demo attempt caught
- Fail (0)
- Demo attempt passes
Matching algorithmWeight IAL215Weight IAL3/PIV10- Pass (2)
- Independent results for the proposed version, demographics included
- Partial (1)
- Results for an older version, or no demographics
- Fail (0)
- No independent results
Chip readingWeight IAL25Weight IAL3/PIV10- Pass (2)
- Certificates validated live in the demo
- Partial (1)
- Validation documented, not shown live
- Fail (0)
- Read fails in the demo
SupervisionWeight IAL25Weight IAL3/PIV15- Pass (2)
- Trained operator, logged overrides, alternate path
- Partial (1)
- Overrides not logged, or no alternate path
- Fail (0)
- Operator cannot override or explain a decision
Session recordWeight IAL210Weight IAL3/PIV10- Pass (2)
- Tamper-evident, complete, timestamped, exported live
- Partial (1)
- Complete but not exported live
- Fail (0)
- Missing items an assessor would request
Data handlingWeight IAL215Weight IAL3/PIV10- Pass (2)
- Provable deletion, no training on customer data, sub-processors named
- Partial (1)
- Deletion not provable
- Fail (0)
- Customer data trains models with no opt-out
Implementation and integrationWeight IAL210Weight IAL3/PIV5- Pass (2)
- IDMS, PACS and HR interfaces documented, dated plan
- Partial (1)
- Interfaces documented, no plan
- Fail (0)
- Undefined custom work
These are weighted evaluation criteria, not standards. If your solicitation states evaluation factors and their relative importance, map the above rows into those. The IAL3 column lends weight to supervision and certification factors, because FIPS 201-3 places PIV proofing at IAL3, and revision 4 of SP 800-63A describes IAL3 as an attended session.
Evaluate price separately from this technical score. Prices should be expressed per session or per station, with every fee listed and the total cost over the term.
At the demo: make them prove it live
Send this script with the RFP so every finalist runs the same tests on your documents. Fail the demo if any test is refused.
- Injection attempt. Your tester feeds a virtual camera or replayed stream into the session. Pass: the system refuses or flags it, and the vendor names the control. (See: Liveness detection isn’t enough.)
- Chip read with certificate validation. Present a passport, a PIV card, or both, as your program requires. Pass: the chip is read and the certificate validation result is shown.
- Exception handling. Run a real exception, such as a poor capture or a mismatch. Pass: you can see how it was decided and by whom, and any override is logged with an identity and a reason.
- Exported session record. Export the demo record on the spot. Pass: it holds timestamps, captures, the chip result and every decision.
While the tests run, watch the user experience: the prompts, how exceptions are handled and how long the applicant spends in the session.
During the pilot: acceptance criteria
Pilot with real applicants, including those most likely to fail capture. Set the pass lines before the first applicant. Use the rates the offeror stated in its proposal, but never looser than a maximum you set yourself or the baseline from your current process.
Criterion How to compute it Pass Fail Failure-to-enroll rate Could not enroll on any path, divided by started; report alternate-path completions separately At or below the pass line, alternate paths at target level Above it, or an alternate path drops the level Throughput at peak Completed sessions per station, or per hour for a remote flow, in your peak window At or above the pass line and your capacity need Below either Abandonment Not finished, divided by started, reason logged At or below the pass line, reasons logged Above it, or reasons missing Assessor evidence package Produced at pilot close All items present Any item missing Time sessions with your own enrollment package. One published reference point: enrollment on NextgenID kiosk workstations averages 8 minutes, and 10 minutes or more for DHS, HHS and Well Hive, whose package includes full fingerprint capture and iris. Use figures like these to model peak demand, not as a promise for every site. Form factor changes how many stations you need. (See: Kiosk, desktop or mobile.)
The evidence package is the audit evidence an assessor or agency auditor would request: recorded sessions; the date and time of each; enrollee names against completion status, matched to your list; the accuracy thresholds used for biometric capture; whether chips or 2D barcodes were read; and how the credential is bound to the enrollee.
At contract: clauses that keep the evaluation true
Fill the bracketed values with your own terms.
- Revision 4 date. A committed date for assessment against SP 800-63 revision 4.
- Listing notice. Notice within [X] days if a listing lapses or its scope changes.
- SLAs. Uptime and support response, with service credits.
- Price. Per session or per station, every fee listed, total cost over the term.
- Model training. Customer data does not train models, or the conditions under which it may.
- Exit plan and data return. Data returned in a stated format within [X] days.
- Proof of deletion. Written certification after return.
- Breach notice. Within [X] hours of a suspected breach.
- Sub-processors and data location. Named, located, with advance notice of change.
Copy-ready checklist
BIOMETRIC IDENTITY VERIFICATION RFP CHECKLIST
Download the checklist (PDF)(SHALL = mandatory, a missing item disqualifies the offer; SHOULD = scored only)
(All attachments due with the proposal)
Frequently asked questions
How do identity verification vendors work?
They capture an identity document and a live biometric, check both are genuine, compare them one to one and record the result. At high assurance, a trained operator supervises the session before the identity is bound to a credential.
Does “certified” mean IAL3?
No. Look the claim up on the public list that names the company, and then be sure to read the level, revision and scope line. If the vendor cannot name a list or a lab, treat the claim as missing.
Should a vendor without a revision 4 assessment be allowed to bid?
Yes. Many certifications in force were assessed against revision 3. Score the gap and require a dated revision 4 schedule in the contract.
What should a pilot prove that a demo cannot?
Failure-to-enroll, peak throughput, abandonment and a complete assessor evidence package, on real applicants, against pass lines you set before the pilot.
Index
Guide pages
- Biometric Identity Verification Systems: How They Work and What to Require
- Liveness Detection Isn’t Enough: How Injection Attacks Beat Selfie Biometrics
- Biometric Verification vs Biometric Authentication: Why You Need Both
- Fingerprint, Face or Iris: Which Biometric for Which Assurance Level
- Kiosk, Desktop or Mobile: Choosing Biometric Capture Hardware
Terms
- FBI Certified Products List (CPL)
- Identity assurance level (IAL)
- Identity management system (IDMS)
- Impostor attack presentation accept rate (IAPAR)
- Kantara Trust Status List (TSL)
- Machine-readable zone (MRZ)
- NIST Face Recognition Technology Evaluation (FRTE)
- NIST Iris Exchange (IREX)
- Physical access control system (PACS)
- Presentation attack detection (PAD)
Run the evaluation, then see it live
Put every finalist through the same script. To watch this demo script run on a controlled device, book a demo of NextgenID Identity Stations.