Book Image

Windows APT Warfare

By : Sheng-Hao Ma
5 (2)
Book Image

Windows APT Warfare

5 (2)
By: Sheng-Hao Ma

Overview of this book

An Advanced Persistent Threat (APT) is a severe form of cyberattack that lies low in the system for a prolonged time and locates and then exploits sensitive information. Preventing APTs requires a strong foundation of basic security techniques combined with effective security monitoring. This book will help you gain a red team perspective on exploiting system design and master techniques to prevent APT attacks. Once you’ve understood the internal design of operating systems, you’ll be ready to get hands-on with red team attacks and, further, learn how to create and compile C source code into an EXE program file. Throughout this book, you’ll explore the inner workings of how Windows systems run and how attackers abuse this knowledge to bypass antivirus products and protection. As you advance, you’ll cover practical examples of malware and online game hacking, such as EXE infection, shellcode development, software packers, UAC bypass, path parser vulnerabilities, and digital signature forgery, gaining expertise in keeping your system safe from this kind of malware. By the end of this book, you’ll be well equipped to implement the red team techniques that you've learned on a victim's computer environment, attempting to bypass security and antivirus products, to test its defense against Windows APT attacks.
Table of Contents (17 chapters)
1
Part 1 – Modern Windows Compiler
5
Part 2 – Windows Process Internals
9
Part 3 – Abuse System Design and Red Team Tips

The memory of the static contents of PE files

In Chapter 1, From Source to Binaries – The Journey of a C Program, we mentioned the process by which the compiler produces a complete executable program. It is clear that the C/C++ source code, after being compiled, is mainly split into blocks and saved. These blocks must be placed on the correct address during dynamic execution. Then, we can start figuring out what the linker would produce as an executable file. Figure 2.1 shows a simplified PE static structure that you need to understand:

Figure 2.1 – Simplified PE static structure

Figure 2.1 – Simplified PE static structure

The author has listed some of the key fields to which the application loader will refer. First, the entire memory arrangement starts with the DOS Header area (IMAGE_DOS_HEADER), where.e_magic must always be equal to the MZ string (that is, IMAGE_DOS_SIGNATURE), which is a valid DOS Header. Most of the fields in the DOS structure are no longer used in the current...