Reverse engineering is considered one of the most complex areas in information security (IS). In the book, the author suggests opening the veil of secrecy over this topic and using practical examples to consider how applications under Windows work, as well as figure out how to exploit buffer overflow vulnerabilities, place your code in executable files, find useful information in memory dumps and much more. The code of almost any application can contain errors. The easiest way to fix these errors is to find a problem command or function in the source code and make appropriate fixes to the code. But what if, for one reason or another, the source code is not available to us, as is the case with proprietary software? If we only have a compiled executable file - an artifact. For example, to identify vulnerabilities, undocumented capabilities, etc. In this case, we will also need reverse engineering. The result of reverse engineering is the construction of a detailed algorithm for the program, as well as the identification of vulnerabilities and other aspects of the software that interest the researcher. Thus, reverse development is needed for those who search for vulnerabilities in order to improve the security of software - bug hunters. Also, reverse engineering is required for programmers working with low-level programming languages ​ ​ (for example, driver developers), where knowledge of assembler is indispensable.