The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.

Protecting Software through Obfuscation: Can It Keep Pace with Progress in Code Analysis?

The work

AuthorsSebastian Schrittwieser; Stefan Katzenbeisser; Johannes Kinder; Georg Merzdovnik; Edgar R. Weippl
Editors
Typearticle
Year2016
Citekeyschrittwieser2016protecting

Where it appeared

Published inACM Computing Surveys
PublisherAssociation for Computing Machinery
Volume49
Issue1
Pages1--37

Identifiers

DOI10.1145/2886012
OpenAlexW2314464932

From OpenAlex, which stores abstracts as an index of words and their positions: what is shown is rebuilt from that, and reads fluently whether or not it is what the author wrote.

Abstract

Software obfuscation has always been a controversially discussed research area. While theoretical results indicate that provably secure obfuscation in general is impossible, its widespread application in malware and commercial software shows that it is nevertheless popular in practice. Still, it remains largely unexplored to what extent today’s software obfuscations keep up with state-of-the-art code analysis and where we stand in the arms race between software developers and code analysts. The main goal of this survey is to analyze the effectiveness of different classes of software obfuscation against the continuously improving deobfuscation techniques and off-the-shelf code analysis tools. The answer very much depends on the goals of the analyst and the available resources. On the one hand, many forms of lightweight static analysis have difficulties with even basic obfuscation schemes, which explains the unbroken popularity of obfuscation among malware writers. On the other hand, more expensive analysis techniques, in particular when used interactively by a human analyst, can easily defeat many obfuscations. As a result, software obfuscation for the purpose of intellectual property protection remains highly challenging.

How it got here

How it got hereagent via openalex
Added2026-10-28 21:56 UTC
Not denied bya person 2026-10-29 17:12 UTC

Cite it as

@article{schrittwieser2016protecting,
  title        = {Protecting Software through Obfuscation: Can It Keep Pace with Progress in Code Analysis?},
  author       = {Sebastian Schrittwieser and Stefan Katzenbeisser and Johannes Kinder and Georg Merzdovnik and Edgar R. Weippl},
  year         = {2016},
  journal      = {ACM Computing Surveys},
  publisher    = {Association for Computing Machinery},
  volume       = {49},
  number       = {1},
  pages        = {1--37},
  doi          = {10.1145/2886012},
}

This record lives at https://refs.drheap.org/schrittwieser2016protecting/ and will keep doing so.