Implement remote IAL2 identity proofing evidence collection and validation per NIST 800-63A-4

domain: pages.nist.gov · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Collect the applicant's identity evidence: for remote IAL2, obtain at minimum one piece of Superior evidence (e.g., a Real ID-compliant driver license or passport) or two pieces of Strong evidence (e.g., a state-issued ID plus a utility bill or financial account document).
  2. Perform document forensic validation: check security features, font consistency, and MRZ (machine-readable zone) checksum on the captured document image using an automated IDV vendor; record the authenticity score and any detected anomalies.
  3. Bind the evidence to the applicant via biometric comparison: capture a selfie, run face match against the document portrait, and run a liveness/PAD check (ISO 30107-3 PAD Level 1 or 2); record the match confidence score and liveness result.
  4. Validate identity attributes against authoritative sources: confirm name and date of birth via a database check (eCBSV for SSN, DLDV for driver license data, or a credit bureau lookup at NIST Fair evidence level).
  5. Conduct identity resolution: confirm the identity presented is unique in your system and not a duplicate of an existing enrolled account by searching on name, DOB, and document number.
  6. Document the complete proofing transaction record: evidence type, strength classification, validation method, binding method, attribute verification results, and timestamp, for audit and compliance review.

Known gotchas

Related routes

Configure an identity proofing flow's evidence requirements to meet NIST SP 800-63-4 IAL2 for a regulated onboarding product
pages.nist.gov · 5 steps · unrated
Verify NIST 800-63B-4 AAL2 compliance for passkey and MFA authenticator implementations
pages.nist.gov · 6 steps · unrated
Map NIST SP 800-63-4 IAL2 and AAL2 requirements to an integrator compliance checklist
pages.nist.gov · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans