STM32Trust security

ecosystem
 Agenda

1 STM32Trust overview 4 Focus on SFI and SBSFU

2 Customer examples 5 Evaluations & certifications

3 Security functions & ST offer 6 Takeaways

2
STM32Trust overview
 STM32Trust overview

• STM32Trust offers a robust multi-level strategy to enhance security in product designs,

using our STM32 microcontrollers and STSAFE secure elements.

• STM32Trust is our security framework combining our ecosystem and security services.

• STM32Trust solution offers a complete toolset for code and execution protection.

• STM32Trust brings 12 security functions to align with customer use cases and security
standards.

4
Customer examples
 Customer example (1/6)
Focus on secure manufacturing
Bob is CEO of a company designing toys.
He would like to make sure the firmware developed by his team is
protected from theft and will only run on the hardware developed by
his team.

What Bob wants to achieve The Security Functions needed by Bob

• No firmware stealing at production

• No over-production by manufacturer • Secure Manufacturing
• No mean to program other devices
• Software IP Protection
• No firmware stealing in the field • Secure Install / Update
• Silicon Device Lifecycle
• Detection of attacks in the field • Abnormal Situations Handling
• Audit/Log 6
 Customer example (2/6)
Focus on isolation and IP protection
Jon is at the head of a company selling firmware and receives royalty
payments from customers.
The firmware developed by his team is very valuable to him. It features
application options that can be further enabled by the user.

What Jon wants to achieve The Security Functions needed by Jon

• Isolate his firmware from customer one • Isolation

• Software IP Protection

• Ensure that his firmware can

• Secure Install/Update
independently be updated

• Set application macro-state in a way • Application Lifecycle

which cannot be altered
7
 Customer example (3/6)
Focus on secure boot & secure update
Mark sells costly equipment.
He wants to offer a firmware update service.
He wants his service to only update his equipment and would like to
make sure only his firmware runs on his devices.

What Mark wants to achieve The Security Functions needed by Mark

• Ensure only his equipment is targeted • Identification/Authentication/

• Always known product state Attestation
• Ensure the update is handled with
integrity and that authenticity checks are • Secure Install/Update
carried out

• Authenticity of firmware running on • Secure Boot

devices 8
 Customer example (4/6)
Focus on secured communication
Oliver is selling devices that report sensitive data to a central server.
Oliver needs to make sure the data cannot be exposed to people
outside of his company and that it is protected.

What Oliver wants to achieve The Security Functions needed by Oliver

• Ensure transmitted data is not exposed • Crypto Engine

• Ensure secret on data encryption keys • Secure storage

• Ensure data is sent from

authenticated devices
• Identification/Authentication/
• Ensure data is sent to authenticated
Attestation
servers 9
 Customer example (5/6)
Focus on brand protection and identification
Rose controls her fleet of devices from a remote server. She wants to be sure
no counterfeiting or malicious devices are running with her server and would
like to have full control over the devices. Rose needs to be able to check the
identity and access rights of network operating devices at any time.

What Rose wants to achieve The Security Functions needed by Rose

• That every device shows a unique identity

• Be able to authenticate the device • Identification/Authentication/
• Be able to attest the device access rights Attestation

• Secure device communication • Crypto Engine

• Ensure that identities and access • Secure Storage and Secure

right secrets cannot be leaked even Manufacturing (Secure Personalization)
at the manufacturing stage 10
 Customer example (6/6)
Focus on data protection
Jack is collecting user data within his devices as part of a larger
system.
Jack’s devices and system needs to be in line with regulations (such as
GDPR) to be able to promote and sell devices.

What Jack wants to achieve The Security Functions needed by Jack

• Ensure platform integrity • Secure Boot

• Abnormal Situations Handling

• Ensure user data is not exposed • Crypto Engine

while communicating • Identification/Authentication/Attestation

• Ensure user data is stored securely • Secure Storage

11
Security functions and ST offer
 The 12 security functions
• STM32Trust brings 12 Security Functions to align with Customer Use Cases and Security Standards
• STM32Trust brings assets (Documentation, Software, Tools…) to cover those 12 Security Functions

Application Life Cycle Secure Boot

Secure Manufacturing Secure Install / Update

Software IP Protection Secure Storage

Silicon Device Life Cycle Isolation

Identification / Authentication /
Abnormal Situations Handling
Attestation

Audit / Log Crypto Engine

13
 The 12 security functions
Summary of definitions
1- Secure Boot 2- Secure Install / Update 3- Secure Storage 4- Isolation

Installation or update of
Ability to ensure the
firmware with initial checks of Isolation between trusted and
authenticity and integrity of an Ability to securely store
integrity and authenticity non-trusted parts of an
application that is inside a secrets like data or keys
before programming and application
device
executing
5- Abnormal Situations 8- Identification /
6- Crypto Engine 7- Audit / Log
Handling Authentication / Attestation
Ability to detect abnormal
Ability to process Unique identification of a
situations (both hardware and
cryptographic algorithms, as Keep trace of security events device and/or software, and
software) and to take adapted
recommended by a security in an unchangeable way ability to detect its authenticity,
decisions like secrets
assurance level inside the device or externally
removals

9- Silicon Device Lifecycle 10- Software IP Protection 11- Secure Manufacturing 12- Application Lifecycle
Initial device provisioning in
Ability to protect a section or Define unchangeable
Control states to securely unsecured environment with
the whole software against incremental states to securely
protect silicon device assets overproduction control.
external or internal reading. protect application states and
through a constrained path Potential secured
Can be multi-tenant assets
personalization

14
 Overview
Security functions versus STM32 & STSAFE
STM32F4/F7/L1/WB/G0/G4/H7/L0/L4 STM32MP1 STM32L5 with TrustZone + STSAFE-A/TPM
Security Function
Silicon Firmware Silicon Firmware Silicon Firmware Silicon
✓
Secure Boot ✓ ✓ ✓ ✓
✓ TF-A ✓
SBSFU ✓ TFM_SBSFU
Secure Install/Update ✓ ✓ ✓ ✓
OPTEE
✓
✓ ✓ ✓
Secure Storage (WB) ✓ ✓ ✓
(L0/L4/H7/G0/G4) OPTEE TFM SPE
SBSFU KMS (L4)
✓ ✓
Isolation ✓ ✓ ✓ ✓
OPTEE TFM

Abnormal situations handling ✓ ✓ ✓

✓
✓ ✓
Crypto Engine ✓ ✓ ✓ Crypto Libraries ✓
Crypto Libraries OPTEE
TFM
✓
Audit/Log ✓
TFM
✓
ID/Auth/Attestation ✓ ✓ ✓ ✓
TFM Attestation

Silicon Device LifeCycle ✓ ✓ ✓

✓ ✓
Software IP Protection ✓ ✓ ✓
OPTEE TFM
✓ ✓ ✓
Secure Manufacturing ✓
SFI (H7/L4) with STM32HSM SSP with STM32HSM SFI with STM32HSM

Application LifeCycle ✓ ✓ ✓ ✓

Firmware to be developed by user

Reference firmware proposed by ST 15
 1. Secure boot
STM32 Firmware / Tool Part Number Benefit for Security Function STM32 Series
Example code implementing both a Secure Boot and a Secure Firmware Update
X-CUBE-SBSFU F4/F7/WB/G0/G4/H7/L0/L4
mechanism
TFM_SBSFU Boot (Part of Example code implementing both a Secure Boot and a Secure Firmware Update
L5
STM32CubeL5) mechanism
TF-A (Part of OpenSTLinux) First stage secure bootloader configuring STM32MP platform MP1

STM32 Silicon Feature Benefit for Security Function STM32 Series

RDP (Read Protection) Prevents a debugger from reading the secure boot
WRP (Write Protection) Prevents an application from altering the secure boot firmware F4/F7/WB/G0/G4/H7/L0/L4/L5
MPU (Memory Protection Unit) Ensures privileged access to some portion of application – task isolations
MMU (Memory Management Unit) Ensures privileged access to some portion of application – task isolations MP1
UBE (Unique Boot Entry) Ensures the silicon always boots at the secure boot location G0/G4/L5
HDP (Hide Protect) Temporal isolation ensuring secure boot is not seen after first execution H7/G0/G4/L5
Secure Boot ROM code Root of trust for loading first bootloader on STM32MP MP1

STSAFE Feature Benefit for Security Function

X509 certificate Allow attest of executed firmware
One-way counter (decrement) Supporting version control management using STSAFE-A

16
 11. 11. Secure manufacturing
STM32 Firmware / Tool Part Number Benefit for Security Function STM32 Series
Hardware security module (HSM) used to secure the programming of STM32
STM32HSM-V1 and V2 STM32 series with SFI or SSP
products, and to avoid product counterfeiting at contract manufacturers' premises
Software tool able to program an HSM with encryption key and counter of
STM32CubeProgrammer NA
permitted programming occurrences
FastROM Programming Services Pre-loading of customer software in STM32 done by ST manufacturing All, except MP1

STSAFE Service Benefit for Security Function

STSAFE-A pre-personalization (MoQ 5K) Pre-loading of customer secret in STSAFE-A at ST secure manufacturing site

STM32 Silicon Feature Benefit for Security Function STM32 Series

Built-in service callable at reset, ensuring installation of an OEM firmware and
RSS with SFI (Root Security Services
option bytes, with authenticity, integrity, confidentiality, insurance to program a H7/L4/L5
with Secure Firmware Install)
genuine STM32, and possibly limited overall quantity of programmed STM32
Secure Boot with SSP (secure secret Built-in service callable at reset, ensuring secure provisioning of OEM
MP1
provisioning) credentials. Controllability of overall quantity of STM32MP1 provisioned

*: Special part numbers on demand. Contact nearest sales office 17

Focus on SFI and SBSFU
 Focus
Embedded secure firmware install - SFI
Manage STM32 authentication, firmware decryption and installation

Customer premises Untrusted environment Secure Loader

ST ecosystem
SFI embedded services
with
Encrypted provisioned by ST
Encryption, HSM and
FW Encrypted FW
FW Transfer ➔ Mass Market
programming tools
Store encryption
key in HSM
HSM SFI approach
Physical transfer Authenticate target STM32
Trusted Package Creator Generate installation license
ST Hardware Secure
Module (HSM) HSM

STM32
3rd Party premises

SMI
SMI Firmware cloning
Encrypted
Authenticate target STM32
Generate installation license protection on the first Protect 3rd party
Module Encrypted Module
Module transfer installation Software IP
Store encryption via (SMI)
key in HSM HSM
Physical transfer UART / SPI / USB
Trusted Package Creator
ST Hardware Secure
Module (HSM)

19
 Focus
Secure boot secure FW update - SBSFU
Reference library source code for
In-application Programming

Demonstrate SW modules for:

• Secure Boot
• Secure Engine for Crypto and key
• Firmware Update image management

Ensure authentication and secure programing of in

the field products

Reference implementation of STM32 hardware

memory protections

20
Evaluations and certifications
 First solution certified SESIP level 3:
STM32L476 with X-CUBE-SBSFU
• SESIP = Security Evaluation Standard for IoT
Platforms, by Global Platform.

• SESIP describes the security functional and

assurance requirements.

• STM32L476 with X-CUBE-SBSFU package is

the 1st GP MCU platform to pass SESIP level 3.

22
 First solution certified PSA level 2:
STM32L5 with TF-M
STM32L5
• PSA certification is the ARM-based security
assurance scheme for IoT devices and services.

• PSA provides 3 levels of assurance and robustness

and a set of easy-to-use built-in security functions.

• The STM32L5 with TF-M is the 1st GP MCU platform

to pass PSA levels 1 and 2 and PSA functional API.

23
 Certifications summary
Certifications Available Now

ARM PSA ARM PSA Level 1 ARM PSA Level 2

• STM32L4 • STM32L5 (TFM)
• Level 1 (Self Assessment)
• Level 2 (White box – Time Limited) • STM32L5
ARM PSA API Compliant
• Level 3 (Smartcard-like) • STM32L5 (TFM)

SESIP
• Level 1 (Self Assessment) SESIP Level 1 SESIP Level 3
• Level 2 (Black box)
• STM32L4 (SBSFU) • STM32L4 (SBSFU)
• Level 3 (White box – Time Limited)
• Level 4 (White box)
• Level 5 (Smartcard-like EAL4+)

CC EAL5+
COMMON CRITERIA • STSAFE-A110
• EAL5+ Smartcard • STSAFE-TPM

Evaluations Available Now

PCI POS Point of Sale application • STM32L4

• Certification documents and links available at www.st.com/stm32trust

• Evaluations material is not public 24
Takeaways
 STM32Trust security ecosystem
the one stop shop solution to implement security
First solution on the market certified PSA Level 2
First solution on the market certified SESIP Level 3

Isolation Strong certification

Secure Boot
Secure Storage
STM32L5+TFM:
Crypto Engine Level 2
STM32
Identification/Authentication
Secure Manufacturing
…
STM32L4+SBSFU:
Level 3
12 core
Customer Implementation on
security functions STSAFE
security needs STM32 and STSAFE
to address needs
EAL5+

PSA = Platform Security Architecture, by ARM

SESIP = Security Evaluation Standard for IoT Platforms, by Global Platform 26
 Thank you
Up-to-date information available
at www.st.com/stm32trust

© STMicroelectronics - All rights reserved.

The STMicroelectronics corporate logo is a registered trademark of the STMicroelectronics
group of companies. All other names are the property of their respective owners.