In-vehicle communications and entertainment system hosts high-value or sensitive applications. API libraries facilitate communication and sharing of vehicle data. These API libraries are vulnerable to reverse engineering and tampering attacks and may even result in loss of passenger safety. Attackers can inject malware that may be able to migrate to other in-car networks such as the controller-area-network (CAN) bus which links to the vehicle’s critical systems. Software provided for dealers to interface with cars through the OBD2 port is vulnerable to reverse engineering and tampering attacks. Hackers may be able to abuse these tools to inject malicious code into the ECUs and CAN bus. Attackers can lift the cryptographic keys used, and use that to build their own rogue apps/software. Their cloned version of the original app/software may have altered functionality, and may intend to gain access to other in-car networks.

The physicians needed to be able to: Securely read and monitor patient data provided by medical devices and control and monitor the medical devices using a mobile application. The medical device company, however, faced a security challenge from potential tampering by hackers — including the injection or hooking of malicious code and/or attacks on memory — which could compromise the run-time operation of the application, and thereby cause unsafe or improper operation and a potential danger to patient safety

Years of research and development were invested by the company into their biometric sensor technology. They wanted to ensure that their unique, patented intellectual property (IP) was not compromised or cloned through application attacks, such as reverse-engineering or code tampering. This was particularly important given the increased competitive pressures in the wearables market and the customer’s distribution model of working in partnership with consumer product manufacturers and potentially third party developers. Although patented and protected under NDA, the company’s code and IP could potentially be exposed during the sharing of their technology (in the form of an SDK/library) during integration as partners work to turn their wearable products into biometric wearables. The customer also required ease of use and flexibility such that their proprietary technology could first be easily protected and then be leveraged within another 3rd party application. As such, the solution needed to meet stringent resource consumption requirements of diverse mobile / IoT platforms.