Embedded Systems Design Europe - October 2007 - (Page 13)

cover feature applications, which traditionally were implemented as discrete functions along with speciﬁc security requirements. For example, consider Apple’s iPhone, which integrates the functions of a cell phone, PC, network client, and media player. Bringing these functions together cohesively provides the user a more feature-rich environment, allowing seamless interaction across multiple applications. However, such integration has potential security implications. The obvious and controversial aspect of digital rights management (DRM) security is that there’s no single standard yet in place. Compound this with the need to provide a trusted computing environment ensuring the protection of the operating system, user data, and digital certiﬁcates. Network security at all levels introduces an evergrowing concern, which is currently leading to the emergence of further standards and security policies. One can’t disregard the trend to enable network devices the ability to conduct ﬁnancial transactions or even act as a digital purse. Once issues as sensitive as those regarding currency and personal identity come into play, a new secure set of standards and certiﬁcation apply. From an equipment manufacturers perspective, it’s not feasible or practical to obtain certiﬁcation of standards compliance for each individual subsystem of a highly integrated system. However, the OEM must be aware of emerging standards and take reasonable steps to implement sensible security policies. Because these issues touch on a signiﬁcant number of security issues, some of the applicable standards and related technologies warrant reviewing. For example, DRM represents one of the most difﬁcult set of standards to implement. Its current implementation has been limited and tied to speciﬁc applications, equipment, and content providers. Although it could continue along that path, nearly all initiatives are heading toward reliance of a digital certiﬁcates. These deﬁne privileges and tie content to a particular user or piece of equipment. In a highly integrated environment, this could lead to problems associated with the management of multiple certiﬁcates, as the storage and veriﬁcation of digital certiﬁcates tied to an individual identity begins to impact other standards. The Trusted Computing Group has a goal of establishing a methodology and deﬁning standards upon which a reliable and secure computing environment can be built. This has led to beyond the scope of this article. Although TPMs have been in volume production for over two years, their function for the most part has laid dormant in most PCs. As next generation operating systems and media software are implemented, the emergence of this security standard will increase in importance to manufacturers and application developers. This will be most apparent when considering the costs associated with deﬁning certiﬁcate attributes and their necessary maintenance. Issues relating to validation will also play an important role, as policy decisions relating to how and if a root of trust or Public Key Infrastructure (PKI) mechanism needs to supported. In the end, OEM, content providers, and software developers will be faced with making decisions with regard to their security policy and the compatibility of their product in applications where security policies may vary. NETWORK SECURITY The concept of network security spans a wide area, as it relates to both hardware and software. From a software perspective, standards are being proposed that deﬁne a set of behavioral characteristics for network servers, clients, and routers. These standards are part of the Trusted Computing Group charter and rely on the presence of a TPM in most network nodes. Many emerging standards and certiﬁcation speciﬁcations are being introduced in network security. Many are proprietary to the larger network systems providers. However, in nearly all cases, these standards are augmented with some level of NIST FIPS (National Institute of Standards and Technology) or Common Criteria security certiﬁcation. Because the complexity of network routers and switches varies considerably, designers must consider ways to 13 the introduction the Trusted Platform Module (TPM). The TPM is a standalone secure processor, which resides separate from the host CPU and handles the veriﬁcation, storage, and management of digital certiﬁcates. It controls the loading of all software from the boot level forward. Thus, when fully implemented, (as it is in Windows Vista), all software executables and data must be digitally signed and veriﬁed by the TPM prior to loading and further processing. There are many controversial aspects to the extent this form of control could lead to. However, that’s www.embedded.com/europe | embedded systems design europe | OCTOBER 2007 012-013-014-016_ESDE.indd 13 9/10/07 13:03:07 http://www.embedded.com/europe

Table of Contents Feed for the Digital Edition of Embedded Systems Design Europe - October 2007

Embedded Systems Design Europe - October 2007 Contents Linux Set to Dominate Torvalds Updates Linux Kernel ARM Establishes Smart Card Foundry Program Emerson Buys Motorola's Embedded Comms Group LynuxWroks and TTTech to Cooperate on Avionics MontaVista CEO Looks for Acquisitions in Europe Ready: Multiprocessing Technology Provides Opportunity Automotive to Drive MCU Market New Supporters Join COM Express Group Analyst Weighs TI Versus Xilinx Versus PicoChip Cover Feature: Embedded Systems Security Has Moved to the Forefront Trace Exposes the Toughest Real-Time Bugs Employ a Secure Flavor of Linux Use an MCU's Low-Power Modes in Foreground/Background Systems Transporting Video Over Wireless Networks New Products Advertising Contacts

Embedded Systems Design Europe - October 2007

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.