Google without passwords...
Google without passwords...
Originally shared by David Amerland
The Trust API and Trust Scores
Google is again using its search technology, applying know-how that's in effect in semantic search to solve the tricky issue of identity and trust in a phone's (or device's) user. As more and more personal information is stored on our devices which are then used to perform tasks like make micropayments, access bank accounts and use our stored details to make larger payments on the web, solving the issue of identity (or Veracity in the usage) is critical to combating fraud and ensuring a secure transactional environment for everyone.
What is critical here is Google's approach. Instead of relying on a perceptually strong level of identification which can be spoofed (like fingerprints, voice or face recognition) it combines a large number of weak indicators to create an end user 'signature' which is unique.
By constantly monitoring those indicators in the background the phone is always aware of who is using it (bad news for couples who share phones ;) ) and whether something may be amiss (like someone trying to pretend they are the device's owner).
The two significant takeaways here are first, by removing the "strong ID indicator" Google makes it difficult for anyone to invest in cracking a phone (no fingerprint to lift, no face recognition or voice to spoof). There is no shortcut to authentication that can be used. Second, by creating an on-going, composite picture of an individual based on their activity with a device Google is bringing into play the affective element that was recently revealed in its I/O (I wrote about it here: http://goo.gl/4USCSv) and is utilizing its knowledge of what works in search (the bit-by-bit driven approach) which creates a trustworthy, unique entity out of the data-dense, picture compiled of an individual.
deep lessons to learn here (and think about) regarding both search (and marketing) and the direction of our digital futures i.e. cherry-picking what information to make available may not always work in our best interests.
https://www.theguardian.com/technology/2016/may/24/google-passwords-android
Originally shared by David Amerland
The Trust API and Trust Scores
Google is again using its search technology, applying know-how that's in effect in semantic search to solve the tricky issue of identity and trust in a phone's (or device's) user. As more and more personal information is stored on our devices which are then used to perform tasks like make micropayments, access bank accounts and use our stored details to make larger payments on the web, solving the issue of identity (or Veracity in the usage) is critical to combating fraud and ensuring a secure transactional environment for everyone.
What is critical here is Google's approach. Instead of relying on a perceptually strong level of identification which can be spoofed (like fingerprints, voice or face recognition) it combines a large number of weak indicators to create an end user 'signature' which is unique.
By constantly monitoring those indicators in the background the phone is always aware of who is using it (bad news for couples who share phones ;) ) and whether something may be amiss (like someone trying to pretend they are the device's owner).
The two significant takeaways here are first, by removing the "strong ID indicator" Google makes it difficult for anyone to invest in cracking a phone (no fingerprint to lift, no face recognition or voice to spoof). There is no shortcut to authentication that can be used. Second, by creating an on-going, composite picture of an individual based on their activity with a device Google is bringing into play the affective element that was recently revealed in its I/O (I wrote about it here: http://goo.gl/4USCSv) and is utilizing its knowledge of what works in search (the bit-by-bit driven approach) which creates a trustworthy, unique entity out of the data-dense, picture compiled of an individual.
deep lessons to learn here (and think about) regarding both search (and marketing) and the direction of our digital futures i.e. cherry-picking what information to make available may not always work in our best interests.
https://www.theguardian.com/technology/2016/may/24/google-passwords-android
Comments
Post a Comment