Google Case Study: Becoming Unphisable: Towards Simpler, Stronger Authentication -FIDO Alliance...

Proprietary + Confidential

Becoming UnphishableTowards Simpler, Stronger Authentication

Christiaan Brand, Google

Largest and most secure infrastructure

Proprietary + Confidential

Mobile UI Application

Network

SoftwareHardware

Google Security Stack

Tomorrow We work on

Quantum resistant encryption

Abuse & Spam Used machine

learning to solveToday less than 0.001% spam in your Gmail inbox

Security Supply ChainBuilt from the

ground upManufactured our own components

Today we tackle authentication

Proprietary + Confidential

Protect Yourself And Your UsersIt's easier than you think for someone to steal a password

Password Reuse Phishing Interception

Social MediaBANK

Proprietary + Confidential

123456Most popular password in 2015

Source: SplashData: https://www.teamsid.com/wor

st-passwords-2015/

password2nd most popular password in 2015

Proprietary + Confidential

76%of account vulnerabilities were due to weak or stolen passwords

43% success rate for a well designed phishing page

goo.gl/YYDM79

Proprietary + Confidential

SMS UsabilityCoverage Issues, Delay, User Cost

Device UsabilityOne Per Site,

Expensive, Fragile

User ExperienceUsers find it hard

PhishableOTPs are increasingly

phished

$?

Today: The reality of One Time Passwords

Proprietary + Confidential

Based on FIDO U2F standardSafe: Protects against phishingEasy: Insert and press buttonCompact: One device, many services

Introducing FIDO U2F

Your Password

Security Key

Account Data

Core idea - Standard public key cryptography

● User's device mints new key pair, gives public key to server● Server asks user's device to sign data to verify the user.● One device, many services, "bring your own device" enabled

Based on Asymmetric Cryptography

Security Supply ChainBuild from the ground upManufacture our own components

Abuse & Spam Used machine learning to solveToday less than 0.001% spam in your Gmail inbox

Google’s Experience

● Enterprise use case○ Mandated for Google employees○ Corporate SSO (Web)○ SSH

○ Forms basis of all authentication

● Consumer use case○ Available as opt-in for Google consumers○ Adopted by other relying parties too: Dropbox, Github

Deployment at Google

Time to authenticate

Time to authenticate

Second factor support incidents

Second factor support incidents

Security Supply ChainBuild from the ground upManufacture our own components

Abuse & Spam Used machine learning to solveToday less than 0.001% spam in your Gmail inbox

We’re not quite done

Proprietary + Confidential

Does this work with a mobile?

How do we deploy this at scale?

What if they lose their key?

We are not there yet for the Enterprise

Proprietary + Confidential

Making progress towards stronger authenticationProductizing FIDO U2F

Proprietary + Confidential

DemoDemo: Bootstrapping account

Security Supply ChainBuild from the ground upManufacture our own components

Abuse & Spam Used machine learning to solveToday less than 0.001% spam in your Gmail inbox

How can you get started?

Proprietary + Confidential

● Internal enterprise authentication (B2B)Authenticate to your own web applications, mobile applications, etc

● Authenticate to your service providers (“token necklace”)

U2F works well in a non-federated environmentComplete isolation between various RPs

● External customer authentication Authenticate your high-value customers using U2F

FIDO U2F use cases

Proprietary + Confidential

Resources● To use with Google

Enable 2-Step Verification on your accountGo to: https://security.google.com Click: 2-Step VerificationClick on the Security Keys tab

● Also use with GitHub, Dropbox, SalesForce

● And / or play with some code https://github.com/google/u2f-ref-code https://developers.yubico.com/U2F/Libraries/List_of_libraries.html

Proprietary + Confidential

Questions?