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

Executive Summary

Login.gov now widely accepts mobile driver's licenses (mDLs) — supporting Google Wallet and Samsung Wallet — for federal identity verification. This policy change, which aligns with recent OMB mandates requiring federal agencies to adopt Login.gov, adds cryptographic verification measures to defend against AI-generated deepfakes. The change has direct technical and compliance implications for contractors who integrate with Login.gov or provide identity verification, authentication, and related cloud/mobile services.

Affected market segments include Digital Identity, Identity and Access Management, Authentication Services, Cryptographic Services, Mobile Application Development, Cloud Services, Cybersecurity, and IT Services. Contractors should prioritize updating integrations, encryption/verification stacks, and compliance postures (see compliance surfaces in Tags) to remain eligible for agency work and to capitalize on new procurement demand; specific opportunities are tied to the NAICS codes and contract vehicles listed in the Tags and to agency adoption driven by OMB direction.

Impact Matrix

Cybersecurity

• Risk Level: Medium-High
• Opportunity: Increased demand for security assessments, anti-spoofing controls, and threat modeling around mDL flows. Specific opportunities tied to NAICS codes and contract vehicles in Tags (NAICS: 541512, 541519, 541511, 541513, 541990, 518210, 541690; Vehicles: OASIS+, 8(a) STARS III, Alliant 2, GSA (General Services Administration) Schedule 70, VETS 2).
• Timeline: Now widely accepted — agencies adopting Login.gov should begin integrating/validating immediately.
• Action Required: Review and update threat models for mDL-enabled flows; validate cryptographic verification chains; test defenses against AI-generated deepfakes in identity flows; align security documentation with the compliance surfaces listed in Tags.
• Competitive Edge: Offer specialized deepfake-resilience assessments and remediation playbooks tailored to mDL/Login.gov flows and demonstrate experience aligning to the listed compliance regimes.

IT Services

• Risk Level: Medium
• Opportunity: System integration, modernization, and support work to connect agency systems with Login.gov mDL authentication. See NAICS/vehicles listed in Tags for positioning.
• Timeline: Now widely accepted.
• Action Required: Inventory systems that rely on Login.gov authentication; plan and execute integration updates; update runbooks and support SLAs to include mDL use cases.
• Competitive Edge: Bundle integration, operations, and compliance support (FedRAMP (Federal Risk and Authorization Management Program)/FISMA alignment) into proposals to reduce agency lift.

Identity and Access Management

• Risk Level: High
• Opportunity: Upgrades to IAM architectures and workflows to accept mDL assertions and cryptographic verification. Contract/NAICS/vehicle opportunities are indicated in Tags.
• Timeline: Now widely accepted.
• Action Required: Update identity proofing and assertion-processing pipelines to parse and verify mDL data; ensure compatibility with Login.gov authentication flows and cryptographic verification mechanisms.
• Competitive Edge: Provide mDL-ready IAM modules or middleware that plug into Login.gov and map to agency IAM policies and the compliance regimes in Tags.

Digital Identity

• Risk Level: High
• Opportunity: Product and services demand for mDL validation, lifecycle management, and integration with federal identity platforms.
• Timeline: Now widely accepted.
• Action Required: Update digital identity products to support mDL formats from Google Wallet and Samsung Wallet; validate cryptographic proof elements; document compliance mapping to NIST 800-63 and related surfaces.
• Competitive Edge: Ship an mDL-compatible identity verification offering with clear compliance traceability to the listed standards and OMB guidance.

Authentication Services

• Risk Level: High
• Opportunity: Revise authentication stacks to accept mDL assertions and cryptographic attestations; opportunity to retrofit existing authentication services to work with Login.gov.
• Timeline: Now widely accepted.
• Action Required: Implement mDL verification, adjust enrollment and recovery flows, and test end-to-end authentication with Login.gov.
• Competitive Edge: Provide turnkey authentication adapters for Login.gov that handle mDL verification, error handling, and logging for audit/compliance.

Cloud Services

• Risk Level: Medium
• Opportunity: Cloud-hosted connectors, services, and FedRAMP-ready hosting to support Login.gov integrations and cryptographic verification workloads. See Tags for relevant compliance surfaces.
• Timeline: Now widely accepted.
• Action Required: Ensure cloud service offerings can securely store and process mDL-related assertions per listed compliance regimes (FedRAMP, FISMA, NIST 800-53) and that SLAs reflect new processing needs.
• Competitive Edge: Position FedRAMP-aligned cloud connectors and managed services that simplify agency adoption of mDL-enabled Login.gov flows.

Mobile Application Development

• Risk Level: Medium-High
• Opportunity: Build or update mobile apps and SDKs to integrate mDL consumption and interaction patterns with Login.gov; potential to develop secure UX flows using Google Wallet and Samsung Wallet compatibility.
• Timeline: Now widely accepted.
• Action Required: Update mobile codebases and SDKs to support mDL interactions, cryptographic verification APIs, and privacy-preserving data handling for Login.gov integrations.
• Competitive Edge: Provide certified mDL SDKs and secure UX templates that streamline agency mobile implementations.

Cryptographic Services

• Risk Level: High
• Opportunity: Demand for cryptographic verification, key management, and attestation services tied to mDL verification and anti-deepfake measures. Compliance surface alignment will be important.
• Timeline: Now widely accepted.
• Action Required: Validate cryptographic verification workflows for mDLs; ensure key management and attestation processes align with agency expectations and the compliance standards listed in Tags.
• Competitive Edge: Deliver turnkey cryptographic verification services or modules that integrate with Login.gov and document compliance to the listed standards.

Cross-Segment Implications

• Cryptographic Services and Digital Identity must coordinate tightly: cryptographic verification is central to mDL trust, and identity lifecycle processes must consume those cryptographic assurances.
• Mobile Application Development and Authentication Services will need to align APIs and UX flows so that mDL assertions collected on-device (Google Wallet, Samsung Wallet) are reliably transmitted, verified, and logged by cloud-hosted services.
• Cloud Services and Cybersecurity teams must ensure hosting and processing of mDL data meet FedRAMP/FISMA/NIST controls indicated in Tags; operations and incident response playbooks should incorporate mDL-specific threat scenarios (including AI deepfakes).
• IT Services and IAM teams should jointly plan migration and backward-compatibility strategies so agency systems using Login.gov can accept mDLs without disrupting existing authentication channels.
• Proposal and capture strategies should reference the NAICS and contract vehicles in Tags where appropriate to target work driven by agency adoption of Login.gov per OMB mandates.