Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
The Embedded Linux Security Handbook

You're reading from   The Embedded Linux Security Handbook Fortify your embedded Linux systems from design to deployment

Arrow left icon
Product type Paperback
Published in Apr 2025
Publisher Packt
ISBN-13 9781835885642
Length 278 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Matt St.  Onge Matt St. Onge
Author Profile Icon Matt St. Onge
Matt St. Onge
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Part 1:Introduction to Embedded Systems and Secure Design
2. Chapter 1: Welcome to the Cyber Security Landscape FREE CHAPTER 3. Chapter 2: Security Starts at the Design Table 4. Chapter 3: Applying Design Requirements Criteria – Hardware Selection 5. Chapter 4: Applying Design Requirements Criteria – the Operating System 6. Part 2: Design Components
7. Chapter 5: Basic Needs in My Build Chain 8. Chapter 6: Disk Encryption 9. Chapter 7: The Trusted Platform Module 10. Chapter 8: Boot, BIOS, and Firmware Security 11. Chapter 9: Image-Based Deployments 12. Chapter 10: Childproofing the Solution: Protection from the End-User and Their Environment 13. Part 3: The Build Chain, Appliance Lifecycle, and Continuous Improvement
14. Chapter 11: Knowing the Threat Landscape – Staying Informed 15. Chapter 12: Are My Devices’ Communications and Interactions Secure? 16. Chapter 13: Applying Government Security Standards – System Hardening 17. Chapter 14: Customer and Community Feedback Loops 18. Index 19. Other Books You May Enjoy

Hard costs versus soft costs

This discussion might pose a tricky situation for your company, yet it’s a discussion that must take place. This will definitely impact design decisions and future support structures. Ultimately, what you charge for your solution must be reasonably above what it costs to design, build, and support it. I must strongly advise you and your team to work out all cost models extensively in the design phase of your project. Feature creep, training costs, logistics costs, technical debt, delays, research and marketing budgets, and other factors are all deeply in play here. Simply, this ties into security in that if not all costs are planned for beforehand, it’s more than probable you will operate on a fixed budget, and something may not get the attention it fully deserves, thereby creating a situation where maybe something gets overlooked and, in itself, becomes a security vulnerability.

Cost models drive everything in the modern world. Profit...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime