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

Examples of signature steganography

In the previous section, we achieved signature verification spoofing by falsifying the system functions in memory. However, up to this point, the spoofing was only done by patching the function from memory. Now that we understand the details of the hash calculation in the Microsoft white paper, we will try to find flaws in the calculation process and bypass the signature verification perfectly.

As we mentioned earlier, in the final section of the Microsoft white paper, Calculating the PE Image Hash, three items are deliberately avoided in the hashing process: Checksum, which can be altered by implanting a signature message, the Security Directory field, which is used for post-filling, and the structure of the signature message block itself. Since the signature message itself cannot be used as part of a fingerprint hash process, and the signed and valid program is considered safe by the Windows trust system (e.g., anti-virus vendors or the system...