嵌入式系统安全实践：打造可靠与安全的软件开发指南

2星需积分: 16 127 浏览量更新于2024-07-21 1 收藏 12.08MB PDF 举报

《嵌入式系统安全：实践方法与可靠软件与系统开发》是一本由David Kleidermacher和Mike Kleidermacher合著的专业书籍，它深入探讨了在现代信息技术环境中，嵌入式系统的安全性及其关键要素。本书的核心内容围绕着系统安全法则、常见的安全漏洞以及如何通过有效的技术和策略来降低风险，确保嵌入式系统的稳定性和数据保护。书中涵盖了多个重要的安全领域，包括但不限于数据保护协议（如SSL/TLS、SSH等）、新兴的嵌入式系统设计、网络安全防护措施（防火墙、入侵检测系统等），密码学原理在系统中的应用，以及系统体系结构、操作系统和存储技术的安全设计。作者强调了在构建安全可靠的嵌入式系统时，系统架构的优化、选择适合的安全操作系统（如RTOS）、管理程序的安全性、网络通信的加密、以及存储设备的数据加密等各个方面的重要性。作者不仅提供了理论知识，还通过实际案例和开发实例，让读者了解如何将安全理念融入到嵌入式系统的设计和开发过程中，从而避免或减少安全漏洞的发生。对于初学者而言，这本书提供了入门级的安全指南，而对于经验丰富的从业者来说，则是深入理解和应对复杂安全挑战的实用手册。值得注意的是，版权方面，本书受到Elsevier公司的严格保护，任何复制或传播行为均需获得书面许可。读者可以在该出版社的官方网站上找到获取许可的详细信息和相关政策，以遵循版权法规。《嵌入式系统安全：实践方法与可靠软件与系统开发》是一本全面而实用的参考书，对于那些希望在嵌入式系统领域建立安全基础或寻求提高安全设计能力的读者来说，是一本不可或缺的工具书。通过阅读这本书，读者不仅能掌握最新的安全技术，还能了解到在实际项目中如何实施这些原则，从而打造出更加安全、可靠和有保障的嵌入式系统。

In an embedded system, this protection responsibility may apply to resources within or

resources of the overall system to which the embedded system is connected or in which it is

subsumed. As we discuss later in this chapter, the protective properties of a component or

system are embodied in its security policy.

1.2 What is an Embedded System?

Attempts to deﬁne “embedded system” are also often fraught with controversy. For the

purposes of this book, we deﬁne embedded system as follows:

Key Point

An embedded system is an electronic product that contains a microprocessor (one or more) and

software to perform some constituent function within a larger entity.

Any deﬁnition of embedded system must be augmented with examples. We do not claim an

aircraft is an embedded system, but its ﬂight control system; trafﬁc collision avoidance system

(TCAS); communication, navigation, and surveillance system (CNS); electronic ﬂight bag

system (EFB); and even in-ﬂight entertainment system are all examples of embedded systems

within the aircraft (see Figure 1.1).

We do not claim the automobile is an embedded system. But its infotainment “head-unit,” anti-

lock breaking system, powertrain engine control unit, digital instrument cluster, and a plethora

of other electronic subsystemsddozens in the typical modern cardare all examples of

embedded systems (see Figure 1.2).

Embedded systems are often characterized by what they are not: the antithesis of the embedded

system is the desktop personal computer whose main Intel Architecture (IA)-based

microprocessor powers the human interface and application environment that serves as the

entity’s sole purpose. Similarly, a rack-mounted server’s main microprocessor performs

a dedicated service, such as hosting a website.

A gray area causes the aforementioned controversy. Some argue whether a smartphone is an

embedded system or just a miniature desktop computer. Nevertheless, there is little debate that

individual components within the phone, such as the radio with its own baseband

microprocessor and software, are embedded systems. Similarly, some servers contain auxiliary

daughter cards that perform health monitoring and remote management to improve overall

availability. Each card contains a microprocessor and software and hence meets our deﬁnition of

embedded system.

The scope of this book liberally includes smartphones whose overall security is highly

dependent upon embedded hardware and software.

2 Chapter 1

Of course, this book is concerned about embedded systems that are involved in some security-

critical function, and some embedded systems lack security requirements altogether. This

book generally does not concern itself with a standalone, battery-powered thermostat run by an

8-bit microcontroller and a few kilobytes of software programmed in assembly code. The

largest security challenge in embedded systems lies in network-connected, sophisticated

electronic products that are managed by an embedded operating system running signiﬁcant

software applications written in high-level programming languages such as C, Cþþ, Ada,

and Java.

1.3 Embedded Security Trends

The MP944, what many consider to be the world’s ﬁrst microprocessor, ran the ﬂight control

system aboard the U.S. Navy’s F-14 Tomcat ﬁghter jet and began what has been more than 40

years of advancement in embedded systems technology. Depending on the particular analyst

asked, embedded computers account for 94% to 98% of the world’s computers. Practically every

major multinational corporationdﬁrms such as Lockheed Martin, Exxon, General Motors,

Hewlett Packard, and Johnson & Johnsondbuilds and depends on embedded systems within its

most important products. And, of course, the average consumer depends on the embedded

applications within aircraft, automobiles, games, medical equipment, and so on, constantly.

At the same time, software and hardware complexity, network connectivity, and malicious attack

threat continue to grow in embedded systems, which are increasingly relied upon for consumer

safety and security. The smart griddwith its smart appliances and sensors, smart meters, and

network gateways (all embedded systems)dis a good example, but only one of many. The

complex set of embedded systems and networks in a smart grid is shown in Figure 1.3.

1.3.1 Embedded Systems Complexity

One of the ﬁrst embedded systems within an automobile was the 1978 Cadillac Seville’s trip

computer, run by a Motorola 6802 microprocessor with 128 bytes of RAM and two kilobytes of

ROM. The printed source code could not have occupied more than a handful of pages.

In contrast, even the lowest-end automobile today contains at least a dozen microprocessors;

the highest-end cars are estimated to contain approximately 100 microprocessors. With

infotainment systems running sophisticated operating systems such as Microsoft Windows and

Linux, the total embedded software content can easily exceed 100 million lines of code. The

F-35 Joint Strike Fighter’s avionics is estimated to host approximately 6 million lines of

code, driven by ﬂy-by-wire controls, complex situational-awareness capabilities, sensor

processing, and high-resolution graphical displays for the pilot. Enterprise network switches

and routers routinely contain millions of lines of code for network protocol processing,

management and conﬁguration, anti-virus rate limiting, and access controls.

4 Chapter 1

1.3.1.1 Case Study: Embedded Linux

To help better understand the scope of this complexity problem and motivate the information

in Chapters 2 and 3 regarding software security, let’s take a closer look at the use of Linux

within embedded systems. Embedded Linux has been growing in popularity due to its royalty-

free licensing, open source accessibility, and wide availability of device drivers and

applications. Despite having thousands of contributors worldwide, the strictly controlled

change management process for Linux (especially the Linux kernel) is excellent relative to

general commercial software quality standards. Steve McConnell, in his book Code Complete,

estimates a software industry average of approximately 30 bugs per 1,000 lines of

production code.

Yet the Linux kernel boasts a far better track record of between 1 and 5 bugs

per 10,000 lines of code.

The use of Linux in systems requiring high levels of security has been a frequent topic of

controversy. Supporters have claimed that Linux’s open source approach improves security due

to exposure to a worldwide community of developers and users (sometimes called the “many

eyes” theory). Detractors have maintained that the complexity and architecture of Linux make

it unsuitable for high criticality applications.

Two recent events are shining a bright light on this debate. In August 2009, the Linux

Foundation published a paper, Linux Kernel Development, detailing the massive, rapidly

growing development and deployment of Linux in everything from mobile phones to television

sets and video cameras.

About a year later, researchers published details of a severe kernel

vulnerability, which had existed in Linux for the preceding eight years.

With a Linux lifetime of over 15 years, there are now plenty of public statistics with which to

analyze the operating system’s robustness. This case study looks at the aforementioned recent

events as well as other public sources of information to conclude on the current state and

outlook for Linux in high-security systems.

1.3.1.1.1 Linux in Government Systems

Some powerful organizations have been supporters of Linux in security-critical government

computer systems. Linux is the trusted operating system in HP’s NetTop, the Raytheon/TCS

Trusted Thin Client, and the General Dynamics Trusted Virtual Environment (TVE)d

a product of NSA’s High-Assurance Platform (HAP) program. All these products are designed

to consolidate computers used by government personnel to access classiﬁed and unclassiﬁed

networks. The specialized computer provides multiple “virtual” desktops and is trusted to

protect sensitive information. To prepare it better for the task of becoming the “touching point”

between physically distinct networks, Linux was enhanced by the NSA’s National Information

Assurance Research Laboratory with additional security controls, known as Security-

Enhanced Linux (SELinux). The SELinux extensions have been adopted by the enterprise

Linux community and employed within the aforementioned computer systems.

6 Chapter 1

剩余406页未读，继续阅读

寒酸的教练

粉丝: 0
资源: 2

嵌入式系统安全实践：打造可靠与安全的软件开发指南

嵌入式系统.pdf

嵌入式系统的网络安全性分析.pdf

嵌入式系统功能安全的三个问题的讨论

嵌入式系统安全分析调研报告.pdf

基于网络的嵌入式系统安全性研究

提升嵌入式系统安全性的策略与实践

嵌入式系统安全重构架构：SANES

嵌入式系统安全挑战与法规应对

MISRA C标准与嵌入式系统安全编程

SecureCore家族：嵌入式系统安全与处理器选择

最新资源