German implementation of eIDAS will require an Apple/Google account to function
Germany's eIDAS implementation outlines a robust Mobile Device Vulnerability Management (MDVM) concept for its eID Wallet, detailing the technical mechanisms to secure digital identities on smartphones. The document reveals a reliance on proprietary platform security features like Apple's App Attest and Google's Play Integrity, raising questions about centralized control over national digital infrastructure. Hacker News readers will find this a fascinating deep dive into the technical challenges and implications of building secure digital identity systems on commercial mobile platforms.
The Lowdown
The German eIDAS implementation's eID Wallet requires stringent mobile device security, leading to the development of a Mobile Device Vulnerability Management (MDVM) concept. This detailed technical document outlines how the system aims to ensure the integrity of cryptographic keys and user authentication when handling high-assurance digital identities like the PID on various smartphones.
- Security Motivation: The core objective is to protect the Wallet Unit's authentication means and linked identification credentials (PID) from duplication and tampering, meeting the high assurance level requirements of eIDAS. This involves safeguarding key stores and user authentication mechanisms, particularly for two-factor authentication.
- Vulnerability Management: Recognizing the impracticality of pre-certifying all mobile devices, the MDVM continuously monitors known vulnerabilities in hardware-backed key stores (HKS) and mobile operating systems. This proactive approach aims to prevent the use of compromised devices for high-stakes digital identity transactions.
- Android Security Signals: For Android devices, the MDVM gathers signals from Google's KeyAttestation (to identify device models and validate attestation signatures) and PlayIntegrity Verdict (to confirm the device meets strong integrity requirements, including recent security patches). It also specifies requirements for Runtime Application Self-Protection (RASP) solutions to detect rooting and runtime hooking.
- iOS Security Signals: On iOS, the system utilizes Apple's DCDeviceCheck.AppAttest for device attestation and assertions. Similar to Android, RASP solutions are deemed essential for detecting jailbreaks and other runtime compromises not covered by Apple's platform security alone.
- Challenges and Limitations: The document acknowledges specific limitations, such as the infrequent updates of Google's key revocation lists and the vagueness of Apple's DeviceCheck risk metrics. These point to the ongoing challenges of relying on third-party security frameworks in a national digital identity context.
In essence, the MDVM strategy is designed to dynamically assess the security posture of user devices, thereby maintaining the integrity and trustworthiness of the eID Wallet by attempting to mitigate the inherent risks associated with deploying high-assurance digital identity on diverse and often-targeted mobile platforms.