CoreTEETM supports a variety of use cases that are common across all kinds of devices regardless of their application. Regardless of the industry you represent and the types of products you are developing, chances are that one or more of these use cases are relevant to you.

Runtime Application Integrity

The Problem

We get it.

You are worried about your embedded application being compromised by malware.

You are concerned about the impact this will have on your business and on your customers.

You are concerned whether this malware can turn your device into a trampoline to attack other connected (potentially higher value) assets.


How CoreTEE Solves This Problem

The first step is to ensure that you have the right SoC selected. Using a TrustZone enabled SoC allows creating secured and normal (unsecured) domains. Your application would run in the normal domain (a.k.a. "Normal World") but you can write the application in such a way as to use the security capabilities of TrustZone.

CoreTEE makes it easier for you to do so. The CoreTEE Runtime Application Integrity Checker is an optional component of CoreTEE that enables Normal World applications (e.g. Linux executables) to be secured by CoreTEE.

When at rest in the file system, protected applications are encrypted and are unusable/unreadable. Thus, it cannot be modified by malware.


At runtime, a Trusted Application decrypts the code and loads the executable into RAM.


An application can be securely bound to a single device or a class of devices as the use case may require, and the keys are only available in CoreTEE.


Preventing Product Recalls Related to Cryptographic Failures

The Problem

If you have deployed an external cryptographic part to provide security functions, then you are already serious about security.

But there is one nagging concern.

The cryptographic algorithms residing in such elements are not updatable. So if someone cracks the cryptography or finds a vulnerability, then you have no recourse but to recall your products.


How CoreTEE Solves This Problem

A TEE, such as CoreTEE, has a fully programmable environment with services to update various aspects of the TEE. To maintain security, it also implements secure processes to update Trusted Applications and the TEE itself, utilizing CoreTEE’s Secure Firmware Update Service.

The entire TEE image must be replaced in order to update the cryptographic algorithms.


When the new payload is sent, CoreTEE first checks the signature of the payload to verify its source.


Upon verification, CoreTEE decrypts the payload and proceeds to install the new image.


Secure Firmware Update

The Problem

Any update to your product’s firmware is an opportunity for malware to attack the device and compromise its integrity. Depending upon the size and nature of the compromise, your business could be at severe risk.

So how do you ensure that every update is safe from compromise?


How CoreTEE Solves This Problem

CoreTEE’s Secure Firmware Update Service is an optional component on the device that provides the verification necessary to ensure a safe and secure firmware update.

When the new payload is sent, CoreTEE first checks the signature of the payload to verify its source.


Upon verification, CoreTEE decrypts the payload and proceeds to install the new image.


Keeping Critical Processes Secure

The Problem


What if you are building a device that controls a sensitive process, which if tampered with, could lead to a disaster and cost millions in damages?

Your primary objective is to make sure that this process is secured and isolated from malware or any kind of tampering.

How CoreTEE Solves This Problem

CoreTEE delivers two capabilities to help you solve the problem: Static Trusted Applications (TAs) and a Preemptive Scheduler.

Create a Static Trusted Application (TA)

CoreTEE lets you create a Static Trusted Application (TA) that controls your sensitive process. The static TA resides in the TEE and is isolated from the rich operating environment that may be vulnerable to malware. In other words, malware doesn’t see your static TA.

Preemptive Scheduler

The Preemptive Scheduler enables multiple TAs to execute concurrently while isolating them from each other. So you can have more than one secure process running.

Reliable Execution

Static TA execution is independent of events happening in the non-secure side of the device. It keeps running even of the rich OS fails or is compromised in some way.


Trusted Remediation = Good User Experience

The Problem


User experience is a critical aspect of IoT devices.

How does your device behave under adverse conditions? Does it recover in a graceful manner or does it “brick”?

It is important to address these issues because an unresponsive device will generate negative sentiment towards your business and cost you future customers.

How CoreTEE Solves This Problem

CoreTEE can be implemented in a way as to provide a graceful remediation to a failure in the rich operating systems. This improves security and user experience of the product.

Implementation Flexibility

CoreTEE can be implemented so that it loads after the initial boot but prior to loading the rich operating system.

Watchdog Detection Function

CoreTEE also implements a “watchdog” function to monitor the rich OS. The watchdog detects any interruptions or failures of the rich OS.

Verified Boot Image

Security is improved because CoreTEE verifies the boot image of the rich OS prior to it booting up.

Failure Remediation

CoreTEE can be programmed to remediate any failures it detects. For example, CoreTEE can restart the rich OS in case it fails.

For more information about the CoreTEE and its capabilities please Email us.

CoreTEE Demo for Secure IoT

CoreTEE Product Overview