Security Development Environment, leveraging the secure hardware built into next-generation microcontrollers to provide the low-level trust anchors and secure services needed for trustworthy IoT solutions.
Customized Security Contexts
Embedded Trust uses the innovative Security Contexts technology to help you with protecting your application. A Security Context defines the configuration of a trusted execution environment by describing the security environment that is required to protect an application.The tool allows you to create new or customize existing Security Contexts through a step-by-step wizard.
Unique Device Identity
Embedded Trust enables the creation of a identity chain for unique or class device identity.
Integrated in Standard Flow
Developers inherit the Security Context generated in Embedded Trust. Correct security and encryption settings are automatically enforced in C-Trust according to the Security Context. All developers are aligned and do not need to be security experts.
Integrated Prototyping & Production
Embedded Trust can simply export the production packages to the Secure Desktop Provisioner. This enables a closed-loop development and prototyping, from the creation of production first articles to export to volume production.
Embedded Trust and C-Trust
Embedded Trust and C-Trust deliver a complete security development environment for embedded applications, enabling you to implement foundation security measures such as encrypting the codebase and setting manufacturing limits.
Together, our security tools help companies to substantially reduce the risk of counterfeiting and cloning during production.
IAR Systems security tools and services offer support for a wide range of devices, including Arm-based MCUs from STMicroelectronics, Renesas and NXP, as well as the Renesas RX MCU family devices, enabling you to choose the right MCU for the security and functional needs of your application. In addition, support for the vast majority of MCUs can be achieved through the use of Hardware Abstraction Layer (HAL).
All devices in the list are ported and tested.
IAR Systems are constantly updating their growing list of supported devices. If your device is not listed, contact us to find out when your device will be supported.
Innovative Security Context technology
A Security Context defines the configuration of a trusted execution environment by describing the security environment that is required to protect an application. For simplified development, C-Trust includes Preconfigured Security Contexts. With Embedded Trust, companies can define custom Security Contexts which are able to uniquely service companies’ specific needs.
Details about Security Context
C-Trust enables you as developer to use Preconfigured Security Contexts, ensuring that you remain in control of system operation today, and into the future. With Embedded Trust, companies are able to define custom Security Contexts, which uniquely service their specific needs.
Security Contexts define the configuration of the trusted execution environments. Security Contexts enable organizations to simplify:
- Complex cryptographic device identities and ownership structures
- Creation of a robust Root of Trust, ensuring device authentication, authorization and attestation, the core proofs of identity
- Implementation of security hygiene, dependant on device hardware support
- Secure Boot Manager extensions to support core boot functionality
- Application of patches, updates, and other lifecycle management criteria
- Delegation of identity for onboarding into cloud infrastructure applications
These Security Contexts provide the foundation for a set of core security concepts, enabling Security From Inception, including protection of Intellectual Property, which is about inhibiting IP theft and malware injection, and Production Control, which is about protecting keys across development and production.
The Security Contexts have been designed to enable developers to rapidly protect the high value and critical IP that organizations create, and to provide reassurance that only authorized and authenticated IP can be installed on devices.