Google Wants to Kill Passwords
Change is always difficult. From the most simple things stored in the garage for years that you cannot seem to get rid of, to cultural traditions that have existed for eons. Now, Google is seeking to annihilate, smash, destroy, our beloved password that we all tend to have a love-hate relationship with.
Passwords drive us all crazy. It seems everything you access requires one. It was not that long ago that a person only needed one password to recall. Those were the days of Internet infancy, from 1995- 2003, when hackers and security risks were at minimum because they were just learning their own trade.
Today, in 2018, it is far different. Now, because of rogue hackers becoming highly skilled, nearly everything on your phone or Internet wants a password. Log into a website for something simple, they want a password. Want to buy something, they want a password. Want to just browse some site, need a password. Ugh! I am personally drowning in passwords to recall. To combat this, I always use 3-4 canned passwords when I access or create an account. Even that can be much, as I try to recall which variation I used. Many times, I have to cycle through them all before one works! Crazy!
So, Google is finding a way to end this. The new system being tested and developed is called Trust API, which will use many sensors in your phone to determine if it’s really you trying to login. Many android phones already use Smart Lock that uses sensors to scan your face, voice, movements, and even location to ascertain if the phone should be unlocked without a password. Some phones will learn your walk pattern and if it different than what the phone thinks is normal, your phone is rendered useless. Pretty amazing!
While Trust API would be for all phones, a more narrow use is their Zero-touch.This is used only with company-owned Android phones and IT admin will pre-configure them to save time with provisioning services. Large companies will be able to provision their owned devices easily based upon an employee (who was assigned a company phone) and their data provided. It provides a seamless deployment method for corporate-owned Android devices making large scale roll-outs fast, easy and secure for organizations, IT and employees.
But Trust API will be even more advanced once available. This will always be ON inside your phone in the background. It will combine data from a variety of sensors to decide whether to lock or unlock your phone. If the sensors detect, at any time, anyone besides the owner is using the phone, it will lock it. The phone will be able to even detect the real owner by how a person swipes when using the phone!
Mastercard will offer new security measures allowing customers to authenticate their purchases using selfies or fingerprints. The Apple 5S iPhone was the first ever to use fingerprint technology in 2013, but it has proven to be troublesome.
Google’s new security features for phones might follow the same course of the Apple 5S. One can envision many problems or snafus occurring with it. Your friend picks your phone up to make a simple call and the phone locks. During an emergency, the phone thinks the owner is NOT the real owner because of stress etc. The security simply fails to connect the dots when detecting the real owner of the phone and locks it. Then what?
This might be in the “Good intentions gone awry” category for technology.
This article is accurate and true to the best of the author’s knowledge. Content is for informational or entertainment purposes only and does not substitute for personal counsel or professional advice in business, financial, legal, or technical matters.