Preconfigured Security Contexts

A security context is the definition of the overall security environment that is required in order to protect your secure IoT product. This basis of this is the implementation of a Root of Trust (RoT), which is generally the minimal set of software, hardware and data that you can trust.

On the hardware side, the MCU being used needs to have the ability to disable debug (at time of production), have the capability of locking the memory, and providing a unique identity. On the software side, a Secure Boot Manager builds upon the underlying MCU hardware capabilities to provide a robust root of trust for a device, securing the overall boot process, protecting the device against the injection of malicious software and enabling and protecting a secure update mechanism. Adding in security data, such as Public Key Infrastructure (PKI) keys and certificates, provides the MCU system with its Security Contexts which should be provisioned into each device.

What are Preconfigured Security Contexts?

During a full development workflow based on IAR Embedded Workbench with Embedded Trust or C-Trust, the Security Context will typically be created using Embedded Trust. However to assist with evaluating or starting early prototype work more quickly with our secure development workflow, we also have a set of preconfigured Security Contexts available.

A preconfigured Security Context comes with a Secure Boot Manager executable which you can flash directly to the target. You can then import, build and master the Getting Started application for your target MCU against the supplied Security Context. If you use a preconfigured Security Context, you do not need to run the Embedded Trust Security Context wizard nor create and build a Secure Boot Manager project yourself. Instead, you can immediately start working on your actual application.

Download available Preconfigured Security Contexts

The available Preconfigured Security Contexts for a variety of MCUs on standard evaluation boards can be downloaded from the links below. Please refer to the readme.txt file included in the package and also to the Embedded Trust/C-Trust User Guide for more details of how to use these.

C-Trust / Embedded Trust, v. 1.50

Preconfigured Security Contexts

C-Trust, v. 1.44

Preconfigured Security Contexts – STMicroelectronics STM32L552xE

Preconfigured Security Contexts – NXP MIMXRT1064

Preconfigured Security Contexts – Renesas R5F572NN

Preconfigured Security Contexts – Renesas R7FA6M3AH

C-Trust, version 1.40

Preconfigured Security Contexts - STMicroelectronics STM32L552xE

Preconfigured Security Contexts - Microchip SAML11

C-Trust, version 1.30

Preconfigured Security Contexts – Microchip SAML11

Preconfigured Security Contexts – NXP MK66FN2M0xxx18

Preconfigured Security Contexts – Renesas RX65NE

Preconfigured Security Contexts – STMicroelectronics STM32F412ZG

Preconfigured Security Contexts – STMicroelectronics STM32H7

Preconfigured Security Contexts – STMicroelectronics STM32L4X5XI

Preconfigured Security Contexts – STMicroelectronics STM32L475

Preconfigured Security Contexts – STMicroelectronics STM32F407

Questions?

Please contact the FAE team if you have questions or need assistance regarding the Preconfigured Security Contexts.

© IAR Systems 1995-2020 - All rights reserved.

We use cookies on this website to provide you with a better experience. You need to accept cookies to continue using this site. Cookies