A low overhead hardware technique for software integrity and confidentiality

Abstract

Abstract

Energy Efficient Memory Authentication Mechanism in Embedded Systems

“…They achieve significant success in measuring the current consumption of the system while limiting the power overhead to less than 12% of the total power. In [20], Roger et al describe an efficient hardware mechanism to protect integrity of softwares by signing each instruction block during program installation with a cryptographically secure signature. This technique serves as a secure and performance efficient alternative to conventional memory integrity verification module.…”

Security extensions for integrity and confidentiality in embedded processors

“…This architecture remains vulnerable to splicing attacks, since signatures in all programs use the same key. The vulnerability to splicing attacks and code confidentiality have been addressed in [42]. However, the proposed architecture only addresses instruction integrity and confidentiality and does not support any form of data protection.…”

Compras públicas como instrumento de política de inovação orientada à demanda

“…For instance, in some ARM processors [3], first level instruction caches work with virtual addresses, however, first level data caches work with physical addresses. In addition to that, working with virtual address space needs special care about repeated addresses to memory blocks that happen when the operating system set the same virtual address to different processes [43]. Moreover, a large virtual address space will require PTAGs to be stored in secondary memory, which will require help of the operating system to manipulate them.…”

“…The literature abounds with secure architectural designs [63,52,43,58,26] that aim at providing local security. However, many of these works have some relevant drawbacks: they overlook systems with less processing power and/or impose a large number of design modifications, from instruction sets to operating systems, requiring sometimes the redesign of the whole tool-chain [63,52].…”

“…However, many of these works have some relevant drawbacks: they overlook systems with less processing power and/or impose a large number of design modifications, from instruction sets to operating systems, requiring sometimes the redesign of the whole tool-chain [63,52]. Some works do not handle authenticity [26], while others deal with device-intrinsic identification, but they do not take into consideration some important practical limitations of that [43,58].…”