Mobile driver’s licenses now widely accepted at Login-dot-gov for ID verification

Overview

Login.gov, the federal government's identity verification platform, now widely accepts mobile driver's licenses (mDLs) for user authentication and explicitly supports Google Wallet and Samsung Wallet. This change implements enhanced cryptographic verification to help defend against AI-generated deepfakes and aligns with recent OMB mandates requiring federal agencies to adopt Login.gov. Contractors that integrate with Login.gov or provide identity verification, mobile apps, cryptographic, or cloud services must evaluate and update technical designs, authentication flows, and compliance artifacts to incorporate mDL authentication methods and the associated cryptographic proofs. Procurement and capture teams should expect changes to agency requirements and solicitations across affected agencies and contract vehicles, and technical teams should validate interoperability and security posture against relevant identity and federal security frameworks. Begin updating proposals, implementation plans, and test plans now to avoid rework when solicitations or agency guidance appear. See the Secure Operations Guide for baseline implementation patterns and the related compliance guides for deeper reference.

Immediate Actions (This Week)

• [ ] Inventory current proposals, contracts, and capabilities that reference Login.gov or identity verification to identify scope for mDL integration.
• [ ] Notify capture, technical leads, and security/compliance owners that Login.gov now supports mDLs (Google Wallet, Samsung Wallet) and that OMB alignment may affect upcoming solicitations.
• [ ] Subscribe to alerts and saved searches for follow-on solicitations and agency guidance related to Login.gov and mobile credential acceptance.

Short-Term Actions (30 Days)

• [ ] Perform a gap assessment of your integration approach: authentication flows, cryptographic verification support, mobile SDKs, and testing plans for mDLs.
• [ ] Update your proposal boilerplate and capability statements to call out mDL-capable authentication, cryptographic verification, and any relevant compliance posture for identity services.

Long-Term Actions (90+ Days)

• [ ] Implement and test end-to-end mDL authentication in a staging environment that mirrors your Login.gov integration, including cryptographic verification and anti-spoofing measures.
• [ ] Update security documentation, system security plans, and operational runbooks to reflect mDL support and procedures for handling identity proofing and cryptographic validation.

Compliance Checklist

• [ ] Assess alignment with NIST 800-63 (digital identity guidelines) for identity proofing and authentication flows.
• [ ] Review FedRAMP (Federal Risk and Authorization Management Program) impact if your cloud-hosted services integrate with Login.gov or host identity verification components.
• [ ] Validate FISMA/Federal security posture implications for systems interacting with federal identity services.
• [ ] Map cryptographic verification requirements against NIST 800-53 control families where applicable.
• [ ] Confirm any applicability of OMB M-22-09 to agency adoption and integration workflows.
• [ ] Verify whether FIPS 201 cryptographic or credential handling guidance applies to your implementation.

(Compliance scope and authoritative mappings TBD — re-evaluate when official agency guidance or solicitation language is published.)

Resources

• OMB M-22-09 — official text (search the OMB website; TBD pending source review)
• Monitor guidance from affected agencies: GSA (General Services Administration), OMB, DHS (Department of Homeland Security), DOD, VA, SSA, Treasury, OPM (check each agency's official guidance pages for Login.gov/mDL updates; TBD pending source review)
• See internal operational guidance: Secure Operations Guide (/insights/secure-operations-guide)
• For related compliance topics: CMMC (Cybersecurity Maturity Model Certification) Compliance Guide (/insights/cmmc-compliance-guide) and CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide)

How Cabrillo Club Automates This

• Cabrillo Signals War Room

Cabrillo Signals War Room already detected this Login.gov mDL acceptance event and delivered this briefing within minutes. It continuously monitors federal policy shifts, OMB mandates, and agency announcements so your team receives immediate alerts when identity verification changes are published. Use War Room to stay ahead of follow-on solicitations and official guidance releases.

• Cabrillo Signals Match Engine

When Login.gov's acceptance of mDLs shifts opportunity relevance, the Cabrillo Signals Match Engine automatically rescopes and rescors your opportunity pipeline. It reprioritizes opportunities where identity, mobile, cryptographic, or authentication capabilities are now more relevant, updating keyword relevance and agency alignment so capture teams focus on the highest-value pursuits.

• Cabrillo Signals Intelligence Hub

The Intelligence Hub tracks affected agencies, NAICS codes, and contract vehicles identified for this event and lets you create saved searches for solicitations mentioning Login.gov, mobile credentials, or OMB mandates. Configure alerts to notify capture and technical leads when matching solicitations or agency guidance appear on SAM.gov (System for Award Management) and related sources.

• Proposal Studio (Proposal OS)

Proposal Studio generates updated compliance matrices and first-draft technical approaches that incorporate mDL authentication, cryptographic verification, and Login.gov integration language using your past performance and win themes. The Proposal OS bid/no-bid engine factors the event into capture decisions and populates capability statements and technical sheets with mDL- and cryptography-focused content.

• Proposal Studio Workflow Tracker

The Workflow Tracker drives a 9-gate capture process for any opportunity affected by Login.gov changes: it routes technical integration reviews, compliance assessments, and legal reviews automatically; tracks supplier certifications and cryptographic component approvals; and produces audit-ready documentation packages for proposals that require evidence of mDL support.

Call to action: log into Cabrillo Signals War Room and the Intelligence Hub to enable saved searches for Login.gov and mDL-related solicitations, then open Proposal Studio to start generating updated technical approaches and compliance matrices.

---

Related guidance: Secure Operations Guide (/insights/secure-operations-guide) | CMMC Compliance Guide (/insights/cmmc-compliance-guide) | CUI-Safe CRM Guide (/insights/cui-safe-crm-guide)