Text: arm TRUSTZONE (logo).

Arm TrustZone Technology

Arm TrustZone technology offers an efficient, system-wide approach to security with hardware-enforced isolation built into the CPU. It provides the perfect starting point for establishing a device root of trust based on Platform Security Architecture (PSA) guidelines.

The family of TrustZone technologies can be integrated into any Arm Cortex-A processor or processor based on the Armv7-A and Armv8-A architecture, and Cortex-M processors built on the Armv8-M architecture.

TrustZone for Cortex-A

TrustZone is used on billions of application processors to protect high-value code and data for diverse use cases including authentication, payment, content protection and enterprise. On application processors, TrustZone is frequently used to provide a security boundary for a GlobalPlatform Trusted Execution Environment.

Learn more

TrustZone for Cortex-M

The Armv8-M architecture extends TrustZone to Cortex-M, enabling robust levels of protection. TrustZone for Armv8-M has the same high-level features as TrustZone on application processors, with the key benefit that switching between Secure and Non-secure worlds is done in hardware for faster transitions and improved power efficiency.

Learn more

TrustZone for Armv8-A vs. TrustZone for Armv8-M

Feature/Architecture TrustZone for Armv8-A TrustZone for Armv8-M 
Additional security states SEL0 - Trusted Apps SEL1 - Trusted OS EL3 - Trusted Boot and Firmware (Armv8-A) Secure thread - Trusted code/data Secure handler - Trusted device drivers, RTOS, Library managers...
Secure interrupts Yes Yes (Fast) 
State transition (Boundary crossing) Software transition Hardware transition (Fast) 
Memory management Virtual memory MMU with secure attributes Secure Attribution Unit (SAU) and MPU memory partitions
System interconnect security Yes Yes
Secure code, data and memory Yes Yes
Trusted boot  Yes Yes
Software Trusted Firmware-A (and third-party TEEs) Arm Keil MDK, CMSIS, Arm Mbed OS, Trusted Firmware-M and third-party software

Get support

Community Blogs

Community Forums

Not answered MPU_S and cmse_check_address_range 0 votes 1284 views 0 replies Started 4 months ago by EugeneH Answer this
Answered Non-secure configuration of UART1 on Arm Musca-A1
  • Musca-A
  • TrustZone for Armv8-M
0 votes 5794 views 4 replies Latest 5 months ago by Daniel Oliveira Answer this
Suggested answer Limit NSC calls to specified RTOS tasks. 1 votes 4576 views 1 replies Latest 6 months ago by Ken.Liu Answer this
Suggested answer How to write values ​​from secure code to non-secure memory.
  • TrustZone for Armv8-M
0 votes 4664 views 1 replies Latest 7 months ago by Uma Ramalingam Answer this
Suggested answer PendSV target secure state 0 votes 4397 views 1 replies Latest 7 months ago by Uma Ramalingam Answer this
Not answered What is the best location of RTOS ? 0 votes 3146 views 0 replies Started 7 months ago by EugeneH Answer this
Not answered MPU_S and cmse_check_address_range Started 4 months ago by EugeneH 0 replies 1284 views
Answered Non-secure configuration of UART1 on Arm Musca-A1 Latest 5 months ago by Daniel Oliveira 4 replies 5794 views
Suggested answer Limit NSC calls to specified RTOS tasks. Latest 6 months ago by Ken.Liu 1 replies 4576 views
Suggested answer How to write values ​​from secure code to non-secure memory. Latest 7 months ago by Uma Ramalingam 1 replies 4664 views
Suggested answer PendSV target secure state Latest 7 months ago by Uma Ramalingam 1 replies 4397 views
Not answered What is the best location of RTOS ? Started 7 months ago by EugeneH 0 replies 3146 views