NIST IAL3 Identity Proofing for FedRAMP High (Class D): Controlled Kits and Kiosks

For Class D (High), FedRAMP's 2026 Rev5 control guidance says authenticators must comply with the most recent NIST Digital Identity Guidelines at IAL, AAL and FAL level 3, so the users in scope need IAL3 identity proofing. FedRAMP High Rev. 5 IAL3 Requirements gives the full answer, control by control.

Yes. NIST SP 800-63A-4 delivers IAL3 as on-site attended proofing, and the proofing agent may attend through a kiosk or device controlled by the proofing provider (NIST calls it the credential service provider, or CSP). Sessions run at an approved private location, such as a company office or the user's home office, never a public place. Each session runs on a Trust Swiftly-controlled IAL3 Kit or kiosk with a trained agent attending, and kits ship to all 50 US states and 32+ countries.

A specialist scopes your rollout within one business day. Each IAL3 Kit then ships to the user's approved office or home, the user picks a session time, and the attended session typically takes 3 to 10 minutes. Every completed session produces a signed evidence package, and the kit goes back on a prepaid label. Need someone started today? Run the IAL2 pathway now, at its own lower assurance level, and complete IAL3 when the kit arrives.

SP 800-63A-4 requires the provider to collect and retain a biometric sample at IAL3, so each session record keeps one alongside the evidence results. Each customer sets how long its IAL3 evidence is kept, to match its own policy and applicable law. Without customer instructions, the default in our Privacy Policy applies.

Every kit is tracked in transit both ways and inspected when it comes back, and the inspection is recorded. A damaged kit is removed from service. Kits hold no session data, so a lost kit exposes no proofing records.

No, as of October 2026. NIST publishes the IAL3 requirements in SP 800-63A-4 but states that it does not conduct certification or conformity assessment against them; agencies and assessors evaluate each provider directly. We give your assessor the IAL3 conformance mapping under NDA and a signed evidence package for every session.

They pick a new time in the Trust Swiftly user portal and can reschedule without involving HR or security. A trained agent attends whichever session they choose.

Absolutely. Most enterprise clients use kiosks for HQ staff and IAL3 Kits for distributed workers. All data flows into a single dashboard for unified auditing.

Two pieces of STRONG evidence, or one STRONG and one FAIR, also meet the IAL3 evidence requirement, so a REAL ID driver's license paired with a second strong document, such as a Permanent Resident Card, works. A trained agent attends the session either way.

We handle the software and security remotely via our management technology. You designate an on-site custodian, such as an office manager, to ensure physical safety and power. Temporary setups are also available to avoid management on-site.

As a platform license fee plus a fee for each completed IAL3 session, which covers the kit, two-way shipping, the attended session and the signed evidence package. The authenticator is priced separately. That lets you compare full program cost with travel-based proofing instead of per-check fees. See pricing.

Under NIST SP 800-63A-4, IAL3 carries the same evidence threshold as IAL2: one piece of SUPERIOR evidence, or two pieces of STRONG evidence, or one STRONG plus one FAIR. A SUPERIOR document such as an NFC ePassport satisfies the bar on its own, while a Real ID driver's license paired with a second strong document also qualifies. What elevates the process to IAL3 is the on-site attended session on controlled equipment and mandatory biometric retention. Knowledge-based verification is not accepted as proofing evidence.

Once the attended IAL3 proofing session confirms the person, we bind a phishing-resistant hardware authenticator to the verified identity. This anchors every future login to the same cryptographic key, so authentication reaches AAL3 and the verified identity cannot be reused or replayed by someone else. The binding happens inside the same trusted session, keeping the chain of custody intact from proofing through ongoing access.