Trusted Referee
A trusted referee is a person vetted and trained to make risk-based decisions about an applicant's identity proofing case when that applicant cannot meet the normal requirements of an Identity Assurance Level (IAL). NIST SP 800-63A-4 defines the role as an agent of the credential service provider (CSP), a third-party service, or a relying party, and lets CSPs offer referees in on-site or remote attended sessions.
Referees are the exception path for people the automated flow rejects: no accepted ID document, a recent name change that breaks attribute matching, a failed face comparison, or a failed fraud check in an unattended remote session. NIST says CSPs SHOULD offer them for IAL1 and IAL2, and when they do, the CSP must tell the public the service exists, document which failures qualify, train referees in document inspection, facial comparison and social engineering, reassess them annually, and record every decision. A referee is not an applicant reference, who vouches for the applicant rather than deciding for the CSP. The design tension is plain: the path that keeps proofing accessible is also the one a fraudster will aim for, so the training and logging requirements are the control.
See also: IAL, identity verification, NIST 800-63, identity verification vendors
Related on Start with Identity
- GlossaryIdentity Proofing
Identity proofing is the process of confirming that an applicant is a specific, real person before issuing them an account or credential; [NIST SP 800-63A-4](ht
- GlossaryAge Verification
Age verification is a check that establishes a user's exact age, or that they are over a threshold such as 18, from an authoritative source like a government ID
- GlossaryBiometric Authentication
Biometric authentication confirms a person by comparing a live measurement of a physical characteristic, such as a fingerprint or face, against a template captu
- BlogLXD and MicroCloud flaw let attackers pose as any trusted client using only its public certificate
Canonical's CVE-2026-112816 let an attacker authenticate to the LXD and MicroCloud HTTPS API as any trusted client by attaching that client's public certificate
- BlogSlugFest: npm trusted publishing trusted repository names, so reclaimed names could publish
Bloom Security found npm trusted publishing matched GitHub repositories by owner/name until first publish, letting anyone who reclaimed a renamed or deleted slu
- VendorThales SafeNet Trusted Access
strong