Embitel

Search
Close this search box.

Trusted Application Development

Powering Secure Embedded Systems

Tuv nord
Automotive spice
cmmi
certificate
Tisax-2
Ahk
iso 9001
A Trusted Application (TA) is a secure software component that runs within a Trusted Execution Environment (TEE). It ensures isolation and protection for cryptographic processing, secure storage, and access control.
SoCs powering ADAS, telematics solutions, and Infotainment system face persistent cybersecurity threats. Protecting sensitive memory segments and cryptographic keys is crucial to prevent unauthorized access and modifications, ensuring automotive system security.

Trusted Execution Environment (TEE) along with Trusted Applications act as isolated enclave to shield all operations involving sensitive data.

In modern automotive ECUs, a Trusted Application like the Secure OTA Firmware Update Manager ensures system integrity. It decrypts and validates firmware updates by verifying digital signatures and certificate chains. Rollback protection blocks outdated or vulnerable versions, keeping the vehicle secure and reliable.

Our cybersecurity teams in Germany and India develop such Trusted Applications (TAs) that isolate critical operations, safeguard sensitive data, and enforce strict access controls. These TAs are tailored for diverse platforms, including automotive ECUs, industrial IoT gateways, healthcare devices, consumer electronics, and EV charging systems. Some of the common trusted applications include Cryptographic Key Management, Data Encryption, Secure OTA update etc.

How Our Trusted Applications Enable Cybersecurity

Our Trusted Applications address critical challenges for customers requiring secure access, data protection, and cryptographic functionality. The TAs are built for Trusted Execution Environments (TEEs) to tackle critical cybersecurity needs. They secure access to sensitive hardware, protect data from tampering, and handle cryptographic operations without exposing keys.

image1

Access to Restricted Peripherals

Some SoC peripherals, like OTP memory, are only accessible through the TEE. Our TAs enable secure access to manage unique IDs and anti-rollback counters.

image1

Secure Cryptographic Operations

Cryptographic operations such as signing, encryption, and decryption often expose keys. Our TAs perform these securely within the TEE, ensuring keys remain protected.

image1

Protecting Immutable Data

Critical data like certificate hashes or root keys need to be tamper-proof. Our TAs securely store this information to guarantee its integrity for validation processes.

image1

Enforcing Rule-Based Updates

Some data, like anti-rollback counters, must only change under strict rules. Our TAs ensure updates are controlled, preventing unauthorized downgrades or vulnerabilities.

Success Stories: Trusted Applications

Our Trusted Application Development and Integration Services

Development-of-OBD-Driver

Custom Trusted Applications

Custom Trusted Applications to meet unique requirements, including anti-rollback protection, secure logging, and performance-driven compliance.

Development-of-OBD-Driver

Kinibi & OP-TEE Development Expertise

Development of secure TAs for both production hardware and virtual environments, leveraging Kinibi, QEMU, and OP-TEE.

Development-of-OBD-Driver

Cryptography Services

End-to-end encryption, decryption, and key management solutions, secure signing etc. integrated with industry-leading cryptographic libraries such as OpenSSL.

Development-of-OBD-Driver

GlobalPlatform API Integration & Linux-Based Libraries

Implementation of standardized APIs for secure communication, cryptographic operations, and custom libraries to wrap TA functionality for seamless Linux integration.

Custom Trusted Application Development: Value Adds

Picture101
Speed to Market

Rapid development and deployment of Trusted Applications, ensuring quicker delivery of secure embedded solutions.

Picture101
Automotive-Grade Quality

Compliant with ASPICE, ISO 21434, and other industry standards, providing robust, dependable results.

Picture101
Cost Efficiency

Reusable components and best-cost country development practices lower project costs.

Picture101
Ease of Integration

Clean, modular APIs that integrate smoothly with Linux, QNX, Autosar, and other rich OS environments.

Picture101
Comprehensive Support

Fast response times for vulnerabilities, bug fixes, and ongoing system improvements.

Trusted Execution Environment Architecture

image (8)
  1. Rich Execution Environment (REE):
    • Hosts the main operating system (e.g., Linux) and standard applications.
    • Includes the Client Application which interacts with secure functionality through a Wrapper Library.
  2. Wrapper Library:
    • Acts as a bridge between the REE and TEE.
    • Facilitates secure communication by wrapping TEE-specific API calls.
  3. Trusted Execution Environment (TEE):
    • An isolated environment that runs the Trusted Application (TA) securely.
    • Protects sensitive operations and data from the REE.
  4. TEE Implementation:
    • The underlying system (e.g., OP-TEE) that ensures secure execution of the TA and enforces isolation from the REE.

Journey of a Trusted Application​

01

Requirements Definition

The process begins by defining the exact security requirements. What data must be protected? What operations need to be secure? Is the goal to store cryptographic keys, validate firmware integrity, or handle DRM licensing?

02

Choosing a TEE Platform

Trusted Applications are developed to run within a specific TEE. Common TEE implementations include OP-TEE, Kinibi, and others. Selecting the right TEE depends on factors like hardware support, project requirements, and available development resources.

03

API and Interface Design

A TA communicates with the REE through a defined interface, often using standardized APIs such as those provided by GlobalPlatform. This ensures the TA can receive requests from the REE and perform secure operations in the TEE.

04

Implementation in a Secure Language and Framework

Most TAs are implemented in C due to their low-level control and efficiency. Secure coding practices are crucial, as vulnerabilities in TA code could expose sensitive data. Some platforms provide specific SDKs or development frameworks that include libraries, headers, and tools to streamline TA development.

05

Testing and Validation

Before deploying a TA, it undergoes rigorous testing. This includes functional testing to ensure the application behaves as intended, as well as security testing to identify and fix vulnerabilities. Emulators (like QEMU for OP-TEE) are commonly used in early stages to quickly test and debug the TA.

06

Integration and Deployment

Once verified, the TA is integrated into the device’s firmware or OS stack. Deployment involves securely loading the TA into the TEE’s storage and ensuring it can communicate with the REE’s client applications.

Where do you find Trusted Applications?

Automotive Security Media & Digital Rights Management Device & Virtualized System Security Firmware & Over-the-Air (OTA) Protection Data Protection & Cryptography
  • Malware Protection
  • Key Management & Secure Access
  • V2X & Cloud Security
  • Secure Software Updates
  • Software downgrade protection
  • Audio/Video Authentication
  • Widevine DRM
  • Runtime Integrity Verification
  • Secure VM Communication
  • Android Gatekeeper
  • Secure Logging & Monitoring
  • Mutual Authentication Between Hardware components
  • Secure OTA Updates
  • Anti-Rollback Protection
  • Immutable Data Storage
  • Standardized Cryptographic Operations

FAQs on Trusted Applications and TEEs

What is a Trusted Execution Environment (TEE), and why is it important?

A TEE is a secure area within a device’s main processor that isolates sensitive operations and data from the rest of the system.

It’s critical for protecting cryptographic keys, securing boot processes, and ensuring safe firmware updates, especially in automotive and IoT devices.

Can Trusted Applications be customized for specific hardware or applications?
Yes, TAs are highly customizable to meet specific hardware requirements and industry needs. They can integrate with SoC peripherals like OTP memory and secure cryptographic operations. They can adapt to unique use cases like anti-rollback counters or certificate validation.
What hardware and TEEs do you support?
We have extensive experience developing TAs for Kinibi, OP-TEE, and other widely used TEEs. Our expertise covers a range of hardware platforms, including automotive-grade ECUs, IoT gateways, consumer electronics processors, and specialized industrial controllers. By leveraging our understanding of both real hardware environments (Kinibi) and virtualized development platforms (Qemu), we provide flexible solutions tailored to your specific hardware ecosystem.
How do Trusted Applications (TAs) enhance system security?
TAs run within the TEE to handle sensitive operations like encryption, data storage, and access control. They ensure critical data and keys are never exposed to the untrusted environment, protecting systems from unauthorized access and cyber threats.
How do TAs handle cryptographic operations securely?

Trusted Applications (TAs) operate within the Trusted Execution Environment (TEE), an isolated and secure area of the processor. When performing cryptographic operations like signing, encryption, and decryption, TAs ensure that sensitive keys never leave the TEE.

Here’s how they ensure security:

  • Key Isolation: Cryptographic keys are securely stored and accessed only within the TEE. Even if the Rich Execution Environment (REE) is compromised, keys remain protected.
  • Execution Security: TAs use the TEE to execute cryptographic algorithms, ensuring that operations are performed in a tamper-resistant environment.
  • Standardized APIs: TAs leverage GlobalPlatform APIs for consistent and secure cryptographic operations, enabling interoperability and reducing vulnerabilities.
This approach ensures the integrity and confidentiality of cryptographic processes, making TAs an essential component for secure systems.
Can you develop TAs for our specific use case?

Yes, we specialize in custom TA development to meet unique requirements. Whether you need a TA for anti-rollback protection, secure event logging, runtime integrity checks, or digital rights management (DRM), we can design, implement, and integrate a solution that addresses your exact needs.

Our development process involves close collaboration to ensure that the TA aligns with your technical specifications, industry regulations, and performance expectations.

Scroll to Top