Secure designs begin with a security model consisting of policies, an understanding of the threat landscape and the methods used to enforce physical and logical security. To protect firmware execution given today’s threat landscape, there must be a policy to only allow execution of authenticated firmware. The methods used to enforce this policy rely on MCU security technology to create a protected boot flow. The boot firmware can contain public key cryptography to authenticate application code. In addition to these components integrated in the end device, there are tools and steps that must be taken in the manufacturing environment. Join this session to explore the design and implementation of a secure boot by making use of the Arm® mbed TLS open source software and protect against firmware attacks. This class will use the recently launched K32W (K3S) for the hands-on portion.