Google's Adrian Ludwig Explains What Google Does To Protect Android Users And Their Devices


In more recent times, security has become more of a prevalent issue for android users. Almost routinely now we are hearing new stories of data breaching, data loss and identity theft and as smartphones become more entwined with our living and working lives, these reports are likely to increase in frequency and attract more debate. Very recently, Google hit the headlines for what seemed to be a known security flaw (that Google were made aware of) to which they did not seem to be providing a fix for. This fueled debate as to who should be responsible for patching security flaws. Google's argument (which is a good one, to be honest) is that they cannot apply fixes to devices of a certain age without the manufacturers rolling out the updates. As we know, virtually all manufacturers abandoning device updates once a device reaches the two-year marker. Well, in spite of Google explaining their position they did receive a lot of flack at the time.

To continue to help android devices understand the situation and how Google approach the issue of security with their devices Android Central managed to get a bit of a sit down with Google's Android Security Lead Engineer, Adrian Ludwig. Most of the chat seems to focus around reassuring android users that Google takes security extremely seriously. This was largely explained by Google advising of the various levels of security they employ from hardware features up to the more commonly thought of, Google applications and services. Each level has its own degree of security resulting in a multi-tiered approach. The next issue on the agenda was that of the long-lasting support (which was the issue which caused the headlines a couple of weeks ago). In this respect, Ludwig points out that Google will also endeavor to update fixes and security patches directly through their services and applications if that is possible. Not to mention, that they work with third party partners to provide fixes for the last two generations of the android operating system. With WebKit (the issue from a few weeks ago) being the one exception. Lastly, pointing out that Google continually do (and will) continue to provide third party developers with the information and tools to help combat any and all known security issues.


Following on from this, Ludwig talks about how Google try to help with security issues when it comes to third party apps and custom ROMs. Both of these again are protecting as much as possible through the Google security systems and users are always provided with information on any issues they might have in terms of harmful, malicious or threatening apps or features. It is also worth noting, that the Google Security Services were also continually offered to android users above and beyond any lapse in support for devices from their respective manufacturers. These security features include warnings to the user before they download certain app/services, warnings during downloading of such material and further warning when the content is downloaded and running. As such Google highlights that do try to keep as much support in terms of security as they possibly can. You can read the article in full by clicking the source link below. In the meantime, let us know what you think of the security issue in general and what manufacturers and Google need to do to make sure you and your android device are better protected?

Share this page

Copyright ©2015 Android Headlines. All Rights Reserved.

This post may contain affiliate links. See our privacy policy for more information.

John has been writing about and reviewing tech products since 2014 after making the transition from writing about and reviewing airlines. With a background in Psychology, John has a particular interest in the science and future of the industry. Besides adopting the Managing Editor role at AH John also covers much of the news surrounding audio and visual tech, including cord-cutting, the state of Pay-TV, and Android TV. Contact him at [email protected]

View Comments