Hardware Security Was Embedded In One-Third of the Smartphones Sold In 2019: Report

In 2019, one-third of all the smartphones sold worldwide had security embedded in their hardware. An overall 39 percent year-on-year increase was seen in sales of such smartphones, revealed the latest report by Counterpoint Research.

A secure element (eSE/inSE) was used by Apple and Huawei to embed the hardware security whereas a physically unclonable function (PUF) was used by Samsung.

Satyajit Sinha, Research Analyst at Counterpoint said more and more people are now using smartphones to store their personal and professional data like online banking, financial information, payment details etc. It is the major reason that cyber-attacks are becoming more common, resulting in loss of personal data, money, and privacy is at risk. Therefore, smartphone companies should prioritize securing smartphones.

IoT Security Service of Counterpoint revealed that 89 percent of the smartphones’ shipped had a system based on secure element and only 10 percent of the smartphones out of these were secured through PUF.

Neil Shah, Counterpoint Research Vice President, while talking about the security system of smartphones said SOC’s coreprocessor is a secure element that is well with tamper-resistance and can host applications securely.



Apple, from the launch of A5s onwards, has been embedding a secure enclave (eSE) that was powered by Global Platform.


Huawei embedded integrated secure element (inSE) on SOCs, the HiSilicon Kirin 960, 970, 980, 990 and 710. Smartphone brands like Xiaomi, OnePlus, Oppo, LG, Sony, Vivo, Google, and Samsung were able to embed the hardware security after Qualcomm took a secure element as the secure processing unit (SPU) in Snapdragon 845,855 and 855+.

It is now the need of the time that smartphones become more secure as they hold most of the private data of the user and thus, should provide more security and risk-free privacy.



Read next: Global Tech Consultancy Urges Companies to Protect User Privacy or Face the Consequences

No comments:

Post a Comment