Book Image

Malware Analysis Techniques

By : Dylan Barker
Book Image

Malware Analysis Techniques

By: Dylan Barker

Overview of this book

Malicious software poses a threat to every enterprise globally. Its growth is costing businesses millions of dollars due to currency theft as a result of ransomware and lost productivity. With this book, you'll learn how to quickly triage, identify, attribute, and remediate threats using proven analysis techniques. Malware Analysis Techniques begins with an overview of the nature of malware, the current threat landscape, and its impact on businesses. Once you've covered the basics of malware, you'll move on to discover more about the technical nature of malicious software, including static characteristics and dynamic attack methods within the MITRE ATT&CK framework. You'll also find out how to perform practical malware analysis by applying all that you've learned to attribute the malware to a specific threat and weaponize the adversary's indicators of compromise (IOCs) and methodology against them to prevent them from attacking. Finally, you'll get to grips with common tooling utilized by professional malware analysts and understand the basics of reverse engineering with the NSA's Ghidra platform. By the end of this malware analysis book, you’ll be able to perform in-depth static and dynamic analysis and automate key tasks for improved defense against attacks.
Table of Contents (17 chapters)
Section 1: Basic Techniques
Section 2: Debugging and Anti-Analysis – Going Deep
Section 3: Reporting and Weaponizing Your Findings
Section 4: Challenge Solutions


In this chapter, we've discussed what MITRE's ATT&CK framework is all about, and how it can help us describe the behaviors of both adversaries and malware, and how to do so.

Not only does the framework allow us the ability to describe things very succinctly, but it also enables us to further describe the behaviors we are seeing in consistent language with sufficient technical depth for those who may hold an interest in such technical knowledge.

We've also learned how it may enable us to write better reports, and have enough information for everyone involved, from those who may be less technical than us as analysts, to those who will be taking action during or after a security incident caused by a piece of malware we are studying.

The next section focuses on practical, example driven application of the findings from previous parts where we will be looking at the solutions to the previously posted challenges.