Mobile Driver's License Criteria
Full Title or Meme
The Mobile Driver's License Criteria for a high level of Identity and Authentication Assurance.
Context
- The issuance of ISO 18013-5 for a Mobile Driver's License an increasing level of trials towards getting driver's licenses installed on Smartphones.
- The US Office of Strategy, Policy and Planns, of the Department of Homeland Security (DHS) has issued a RFC for security standards and requirements to enable Federal agencies to accept them if compliant with the REAL ID.
- There are 49 states that accept driver's license on smartphones for some purposes.
- Report from the Privacy & Identity Protection in mobile Driving License ecosystems Discussion Group working draft.
- Google announced (2020-11-04) privacy-preserving features in Android's Mobile Driving License framework including the credential API in Android 11.
- The Kantara's discussion group on Privacy and Identity in the mobile driver' license aka PImDL focus is now on North America where individual provinces and states are responsible for issuing Identity Cards based for a wide variety of purposes beyond just the attributes present on a driver's license.
Actors
- Holder - the subject of the Mobile Driver's License
- Reader - a device that can read and verify the mDL, which is presumably hosted in a native smart phone app
- Issuing Authority - typically a state motor vehicle agency.
- Trust Authority - some sort of wide ranging list of valid participators - not well defined at this point.
- Caution on terms. mDL and mDL app get conflated in the specs. The full mDL is seldom/never released by the app to the reader/verifier.
- Compare there terms Verifiable Credential and Presentation Exchange from the DIF folk. The VC (like the mDL or mdoc) may be in the smartphone, but only a part is "presented" to the reader.
Use Cases
- TSA acceptance at transportation check-in lines.
- Building access for many Federal buildings.
- Mobile_Driver's License in Healthcare
- State Issued ID for Healthcare on this wiki lists other uses states might have for the mDL standard format.
- Currently kiosks have been deployed that accept ISO 18013 compatible Driver's License cards. The same capability is likely to be required for ISO 18013-5 Mobile Driver's Licenses.
Problems
- REAL ID has yet to approve a single state's Mobile Driver's License for Federal access.
Solutions
- NIST pilot run by Thales This page has a list (20201-10) of states that have mDL tests in progress.
- AAMVA page dedicated to Mobile Driver's License (mDL)
Privacy Considerations
- Google Privacy-preserving features in the Mobile Driving License (2020-10-28) Which depends on the following Android 11 API3 0 Identity Credential features, However a keystore backed version will run on API 24 and later.
- IdentityCredentialStore first available in API 30.
- Android Jet-pack (2020-08-19) Security-Identity-Credential Version 1.0.0-alpha01 (and later), compatible with the data structures in the ISO 18013-5 Personal identification — ISO-compliant driving license — Part 5: Mobile driving licence (mDL) application
Consent and Notice
The spec is unclear how exactly how the mDL in a smartphone would provide notice or consent. The following are an expectation of a user.
- Who wants to know - hopefully this would be a trustworthy statement of the reader's owner.
- What will they do with the information?
- What data is requested. Most interesting is the picture and ID #.
Notice in a case like this is difficult as the standard does not even require the mDL reader from reporting the name of the entity requesting the id. Assuming that it did the question is whether that would constitute notice or if some sort of consent receipt would be required.
References
- Also see the companion document on Mobile Driver's License Criteria for a high level of assurance.
- nice description on Medium
- Pew Research mobile fact sheet
- review the mDL resources available from the Secure Technology Alliance on the mDLConnection website
- What does REAL-ID Act “enforcement” really mean? The Identity Project.
- Va Code Chapter 50. Electronic Identity Management Act
- Va § 2.2-436. Approval of electronic identity standards.
- Va § 2.2-437. Va Identity Management Standards Advisory Council.
- Identity Management Standards Advisory Council (IMSAC) with links to the parts.
- Rules for Virginia special ID cards.