Mentor Graphics — Technical Presentation (2016)
35 slides from Mentor Graphics's technical presentation, 2016
Slide 1: ARM TrustZone: How to use it to make devices secure and safe
ARM TrustZone® How to use it to make devices secure and safe Felix Baum mentor.com/embedded Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Qt is a registered trade mark
Slide 2: Agenda
Agenda Objectives Results Describe the need for hardware Provide a better understanding of how enforced security to secure embedded devices by Outline the use cases for the ARM utilizing the ARM Cortex-A hardware TrustZone deployments and software capabilities Mentor Embedded products Highli
Slide 3: Recent Security Incidents in the News
Recent Security Incidents in the News Blast Furnace – via plant’s business network — Caused “massive” damage to blast furnaces Jeep Grand Cherokee – via vehicle connectivity — Malicious code allowed access to vehicle’s CAN bus Medical Devices – via medical network — Devices accessed to steal p
Slide 4: Growing threat of attacks
Growing threat of attacks 4 mentor.com/embedded
Slide 5: Consolidation on the SoC level
Consolidation on the SoC level 5 mentor.com/embedded
Slide 6: Security and Safety via Separation
Security and Safety via Separation Safety: Protecting the world Security: Protecting the from the device device from the world Mixed criticality: Protecting of security or safety critical parts of the device from other parts of the device ISO26262-6 requires “freedom from interference”. If two syste
Slide 7: Starting point: Chain of Trust
Starting point: Chain of Trust App 1 App 2 Before loading any software, ask: • Did it come from the OEM? App N • Has it been tampered with? Operating System(s) Signature Second Crypto Key Stage Boot Loader Signature First Stage Crypto Key ARM TrustZone can be used for: Boot Loader • Crypto Key Stora
Slide 8: Use Case 1: Physical Separation aka AMP
Use Case 1: Physical Separation aka AMP 8 mentor.com/embedded
Slide 9: Physical Separation aka AMP
Physical Separation aka AMP Graphics or Web Real Time App Linux A9 A9 Multicore Device running one Operating System — Migrating to multicore device for the next generation or project — Need to consolidate applications that require real time and determinism with applications requiring Linux networkin
Slide 10: Physical Separation aka AMP
Physical Separation aka AMP Graphics or Web Real Time App Linux RTOS A9 A9 or M4 Multicore Device running multiple Operating Systems — Single user interface for Configure, Edit, Debug, Optimize work — Framework to configure, boot, execute and communicate across cores and Operating Systems — Take ful
Slide 11: Remote CPU Lifecycle Management
Remote CPU Lifecycle Management Used by master OS to boot remote OSs on remote CPUs remoteproc user API for Application Application processor lifecycle management rpmsg rpmsg rproc virtio Conformance to upstream virtio Nucleus RTOS Linux remoteproc Linux or Bare metal or or Bare metal or imple
Slide 12: Inter Processor Communications
Inter Processor Communications For inter-processor communications between IPC using rpmsg OS/software contexts Application Application rpmsg user API for Inter Processor Communication rpmsg rpmsg Conformance to upstream Linux rpmsg implementation virtio virtio Linux or Stand alone OS agnosti
Slide 13: OpenAMP Use Cases
OpenAMP Use Cases Separation of Resource constrained for example power management Offload work for Computationally intensive operations such as processing, encryption of secure, sensitive data 13 mentor.com/embedded
Slide 14: How this could be accomplished
How this could be accomplished Sourcery™ CodeBench IDE Core Lifecycle Management Remote Firmware Patient Sensor Data Acquisition User Applications Application Webserver Qt® HMI Mentor® Embedded Multicore Patient Framework Name: Jan rpmsg Facility: Clinic rpmsg remoteproc virtio Floor 5 Room 304 virt
Slide 15: Use Case 2: Virtualization Enforced Separation
Use Case 2: Virtualization Enforced Separation 15 mentor.com/embedded
Slide 16: Separation via Virtualization
Separation via Virtualization Cluster App Infotainment App ECU App OS OS Autosar SoC SoC SoC Multiple boards running various Operating Systems and dedicated applications — Migrating to multicore device for the next generation or project — Need to consolidate applications that require real time with
Slide 17: Separation via Virtualization
Separation via Virtualization Cluster App Infotainment App ECU App RTOS Linux Autosar Hypervisor Cortex A Cortex A M4 Consolidation to a single Heterogeneous Multicore SoC running multiple Operating Systems and Applications — Virtualizing GPU to either control multiple displays per application or la
Slide 18: Separation via Virtualization
Separation via Virtualization Infotainment Display Cluster Display FPD-Link Display 12” (1280x480 ) FPD-Link Touch Display 10” (1280x800 ) CAN AUTOSAR IVI Linux Nucleus USB BUS & CAN BusMaster CAN 2CAN stack Hypervisor (2x CortexA) Vehicle on M4 + GPU sharing Simulator AXSB 18 mentor.com/embedded
Slide 19: Use Case 3: Hardware Enforced Separation
Use Case 3: Hardware Enforced Separation 19 mentor.com/embedded
Slide 20: Separation via ARM TrustZone
Separation via ARM TrustZone ARM TrustZone® can be thought of as a hardware-based solution that can be used to define a subset of the SoC for access by software. Software that is designated as Secure World software has access to ALL of the SoC, while software that is designated as Normal World c
Slide 21: Separation via ARM TrustZone
Separation via ARM TrustZone ARM TrustZone® can be thought of as a hardware-based solution that can be used to define a subset of the SoC for access by software. Software that is designated as Secure World software has access to ALL of the SoC, while software that is designated as Normal World c
Slide 22: Separation via ARM TrustZone
Separation via ARM TrustZone ARM TrustZone® can be thought of as a hardware-based solution that can be used to define a subset of the SoC for access by software. Software that is designated as Secure World software has access to ALL of the SoC, while software that is designated as Normal World c
Slide 23: Separation via ARM TrustZone
Separation via ARM TrustZone ARM TrustZone® can be thought of as a hardware-based solution that can be used to define a subset of the SoC for access by software. Software that is designated as Secure World software has access to ALL of the SoC, while software that is designated as Normal World c
Slide 24: GlobalPlatform and TEE
GlobalPlatform and TEE GlobalPlatform identifies and develops technical specifications which facilitate the secure and interoperable deployment and management of multiple embedded applications on secure chip technology. Its proven technology is regarded as the international industry standard for b
Slide 25: GlobalPlatform and TEE
GlobalPlatform and TEE GlobalPlatform identifies and develops technical specifications which facilitate the secure and interoperable deployment and management of multiple embedded applications on secure chip technology. Its proven technology is regarded as the international industry standard for b
Slide 26: Separation via hardware enforcement
Separation via hardware enforcement App 1 App 2 App 1 App 2 RTOS RTOS RTOS A9 A9 A9 One or more cores running applications of various security or robustness levels — Migrating to multicore or more powerful device for the next project — Need to consolidate applications that require secure and non sec
Slide 27: Separation via hardware enforcement
Separation via hardware enforcement Secure nonSecure App Secure App nonSecure App App RTOS RTOS Linux A9 A9 A9 One or more cores running applications of various security or robustness levels — Migrating to multicore or more powerful device for the next project — Need to consolidate applications that
Slide 28: Separation via hardware enforcement
Separation via hardware enforcement Secure App nonSecure App Secure App nonSecure App Data Data RTOS RTOS RTOS RTOS or Linux or Linux Control Control TrustZone TrustZone A9 A9 A9 Using the ARM TrustZone capabilities of the SoC separating secure or robust applications from the rest of the system — Co
Slide 29: ARM TrustZone & MultiCore
ARM TrustZone & MultiCore ARM TrustZone® can be thought of as a hardware-based solution that can be used to define a subset of the SoC for access by software. Software that is designated as Secure World software has access to ALL of the SoC, while software that is designated as Normal World can
Slide 30: Separation via hardware enforcement
Separation via hardware enforcement Non-certified Certified Single Core Complex Instrument Logic Safe Instrument Logic Complex Graphics Render Safe Graphics Render Safe Graphics Driver draws content Dual Core to separate graphics plane managed by safe driver planes blended in hardware, also managed
Slide 31: Separation via hardware enforcement
Separation via hardware enforcement Floodgate Cellular Security Manager Cloud Secure Floodgate Floodgate Floodgate CSP World Agent Audit FW Update Agent Floodgate Secure Boot Floodgate Floodgate Media IP Tables Daemon Tail Server Nucleus RTOS MEL Kernel Firewall Trust Zone Normal World CoAP/MQTT/XMP
Slide 32: ARM TrustZone limitations
ARM TrustZone limitations TrustZone includes features that may be helpful to Multi-Core and Multi- OS support, but it alone fails to provide some fundamental capabilities typically required by an embedded system: — No separation of Normal World resources from Secure World — It only allows for 2 payl
Slide 33: Bring it all together
Bring it all together Secure App Safe App Graphics/Vision/Web App App Secure Safety Cert Linux RTOS RTOS RTOS BME TrustZone Hypervisor Cortex A Cortex A Cortex A Cortex A Cortex M 33 mentor.com/embedded
Slide 34: The World of Embedded Devices
The World of Embedded Devices The is no silver bullet or one single button to push to adequately protect an embedded device! Consider using ARM TrustZone and Mentor Graphics products to meet security and regulatory requirements! 34 mentor.com/embedded
Slide 35: Q & A
Q&A 35 Proprietary and Confidential ©2016 Mentor Graphics mentor.com/embedded