English
Designing for safety and security in a connected system
Dan Smith and Andrew Girson, Barr Group
embedded.com (September 06, 2017)
Good embedded software has always been designed for both safety and security. However, connectivity has introduced intolerable levels of security vulnerability in safety-critical applications such as medical, autonomous vehicles, and Internet of Things (IoT) devices.
The tight coupling of safety and security, combined with heightened threat levels, requires developers to fully understand the difference between safety and security; also, to apply industry best practices to ensure that both are designed into a product, right from the start (Figure 1).
|
E-mail This Article | 
|
|
Printer-Friendly Page |
Related Articles
- Designing AI enabled System with SOTIF (Safety Of The Intended Functionality)
- Enabling security in embedded system using M.2 SSD
- Designing an Effective Traffic Management System Through Vehicle Classification and Counting Techniques
- No Safety without Security on the IoT
- System Security: A Model from Medieval History
New Articles
- Reducing Debug time for Scan pattern using Parallel Strobe Data (PSD) Flow
- PUF based Root of Trust PUFrt for High-Security AI Application
- RISC-V's CPU Verification Challenge
- How a voltage glitch attack could cripple your SoC or MCU - and how to securely protect it
- The Answer to Non-Volatile Memory Security Issues at Advanced Nodes: Go Volatile!