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)
- Let's make RISC-V connected systems synonymous with security
- 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
New Articles
- Understanding why power management IP is so important
- Hardware-Assisted Verification: The Real Story Behind Capacity
- Bigger Chips, More IPs, and Mounting Challenges in Addressing the Growing Complexity of SoC Design
- SoC design: What's next for NoCs?
- How to Save Time and Improve Communication Between Semiconductor Design and Verification Engineers
Most Popular
- System Verilog Assertions Simplified
- Hardware-Assisted Verification: The Real Story Behind Capacity
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)
- I2C Interface Timing Specifications and Constraints