To Protect And Confirm
summary
Android P replaces FingerprintManager with a unified BiometricPrompt and an AndroidX.biometric compat, lets apps call authenticate with a crypto object and a main executor, and requires keys to be created with user authentication required and an attestation challenge so back ends can verify a hardware-backed key. CDD sets false acceptance rate <0.002% and a 7% spoofing threshold for weak vs strong biometrics. Key attestation uses OEM intermediate certs signed by Google (min ~10,000 devices per intermediate); Protected Confirmation produces a TEE-displayed CBOR prompt and signs prompt text + extra data, but supported devices are not yet in the field.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 0:47New biometrics in Android 9
- 3:19Biometric strength metrics explained
- 7:56Biometric prompt API demo
- 12:32Trust in biometric authentication
- 17:30Key attestation and chain of trust
- 23:49Enrollment flow with attestation
- 29:08Protected confirmation overview
- 34:23Validating protected confirmation data
- 35:30Resources and wrap-up
related talks
33mBuffed up Biometrics
45mOverview of Biometric Auth
30mAdvanced Android Fingerprint Security
32mWhat's new in Android security
39mSecurity on Android: What's next
22mCommunicating Device Confidence Level and Upcoming Re-Authentications in Continuous
22mComplementing Passkeys with Strong Identity Assurance for High-Risk Actions and Account Recovery
53mHow to Know Your Client Is Real: Hardware-Backed Authentication Patterns