Point/Counterpoint

Gu, Yuan; Wyseur, Brecht; Preneel, Bart; Aussel, Jean-Daniel; Sailer, Reiner

doi:10.1109/ms.2011.39

Cited by 1 publication

(1 citation statement)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For those, software-only protection is the only available option. Moreover, hardware-based protection is considered a risk by some, because it is expensive and at the same time not renewable [35]. The reason for this is that when a hardware defense mechanism is broken at some point, e.g., because implementation bugs are discovered, it is typically very hard-if not impossible-to fix it, so all systems relying on that hardware are vulnerable from then on.…”

Section: Attack Modelmentioning

confidence: 99%

Code Renewability for Native Software Protection

Abrath

Coppens

Broeck

et al. 2020

ACM Trans. Priv. Secur.

Self Cite

View full text Add to dashboard Cite

Software protection aims at safeguarding assets embedded in software by preventing and delaying reverse engineering and tampering attacks. This paper presents an architecture and supporting tool flow to renew parts of native applications dynamically. Renewed and diversified code and data belonging to either the original application or to linked-in protections are delivered from a secure server to a client on demand. This results in frequent changes to the software components when they are under attack, thus making attacks harder. By supporting various forms of diversification and renewability, novel protection combinations become available, and existing combinations become stronger. The prototype implementation is evaluated on a number of industrial use cases. CCS Concepts: Security and privacy → Software reverse engineering; Digital rights management.

show abstract

Section: Attack Modelmentioning

confidence: 99%