{"id":18307,"date":"2018-06-09T08:00:53","date_gmt":"2018-06-09T12:00:53","guid":{"rendered":"https:\/\/www.psafe.com\/en\/blog\/?p=18307"},"modified":"2022-04-27T15:07:33","modified_gmt":"2022-04-27T19:07:33","slug":"manufacturers-caught-lying-about-device-security","status":"publish","type":"post","link":"https:\/\/www.psafe.com\/en\/blog\/manufacturers-caught-lying-about-device-security\/","title":{"rendered":"Manufacturers Caught Lying About Device Security"},"content":{"rendered":"

When you purchase a new Android smartphone, you want to feel assured that the company you chose is doing their best to protect your security. Unfortunately, a recent study by a German security firm showed that a majority of manufacturers we\u2019ve instilled with our trust might not deserve it. Over 1,200 different smartphone from over a dozen vendors have security holes that leave your device and your personal information vulnerable to hackers who can exploit these vulnerabilities. <\/span><\/p>\n

Begin Protecting Your Device
\n<\/b>One way to start protecting your Android if manufacturers aren\u2019t doing it is to use a reliable third-party app like dfndr security. Take advantage of a full virus scan feature and anti-hacking technology that fights any malware threats or phishing attempts. With 21 other great features included, you may not be able to control your manufacturer, but you can stay one step ahead of hackers.<\/span><\/p>\n

\"\"<\/a>
<\/center><\/center>
<\/center>
<\/center>
<\/center>
\nWho is Guilty and Why
\n<\/b>The study found that manufacturers who are leaving security gaps in their systems and may be attempting to deceive customers include Google, Sony, Samsung, Wiko Mobile, Xiaomi, OnePlus, Nokia, HTC, Huawei, LG, TCL, Motorola, and ZTE. As you can imagine, these companies are not small players in the Android market. At the top of the charts, <\/span>Samsung holds almost 48% market share\u00a0<\/span><\/a>around the globe, putting nearly half of all Android users at risk. But, how exactly are these manufacturers deceiving their customers?<\/span><\/p>\n

Read More: <\/b>What You Need to Know About Google\u2019s Security Patch Record<\/b><\/a><\/p>\n

According to the study, the manufacturers have been claiming within their devices\u2019 settings that all security and system patches are up to date when they are actually behind. This practice of deceit not only leaves Android phones vulnerable but also calls into question the validity of a manufacturer’s security practices. In order to find the cleverly hidden lie, the firmware of many devices had to be carefully examined.<\/span><\/p>\n

For Some, The Problem is Worse Than Others|
\n<\/b>Companies with a mix of patched and unpatched devices or only behind by a single patch includes Google, Sony, Samsung, and Wiko Mobile. However, of those noted previously, companies HTC, Huawei, LG, Motorola, TCL, and ZTE are at least 3 or more patches behind. While Google is the company that issues patches for the Android operating system, it\u2019s the responsibility of each manufacturer to deliver patches to their line of handsets accurately.<\/span><\/p>\n

Some Light at the End of the Tunnel
\n<\/b>Luckily, there could be a possible solution. Google has begun implementing a new <\/span>project they have dubbed Treble<\/span><\/a>. The project attempts to fix manufacturer patching issues by putting more control of Android\u2019s core back into the hands of Google. What this means is your device could be updated as soon as a patch is released without having to wait for a manufacturer. While Treble has been included in Android 8.0 Oreo, not all devices currently support it. However, the good news is the project will be implemented on all Android devices moving forward.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Like anyone, we want to trust the Android companies we deal with, but a recent study discovered that might not be the case.<\/p>\n","protected":false},"author":83,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","footnotes":""},"categories":[5],"tags":[30,182,358,249,67],"class_list":["post-18307","post","type-post","status-publish","format-standard","hentry","category-security","tag-android","tag-malware","tag-protection","tag-security","tag-smartphone"],"_links":{"self":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts\/18307","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/users\/83"}],"replies":[{"embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/comments?post=18307"}],"version-history":[{"count":7,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts\/18307\/revisions"}],"predecessor-version":[{"id":19322,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts\/18307\/revisions\/19322"}],"wp:attachment":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/media?parent=18307"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/categories?post=18307"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/tags?post=18307"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}