Skip to content
Tutorials Center
My learning

Topics

Lesson 8 of 37 ยท Concepts and Safe Lab

The Analyst Toolkit and Note-Taking

Tour the categories of tools used in malware analysis (hashing, strings, PE viewers, monitors, debuggers, disassemblers) and learn a note-taking method that supports reports.

You do not need a hundred tools to analyze malware. You need one good tool for each task, and the discipline to record what each one told you. This lesson groups the tools by task, explains what each category reveals and shows how to keep notes you will still understand three months later.

The tool names below are well-known examples, mentioned read-only: this course never asks you to download or run anything from them. Output shown in later lessons is either reproduced by simulation or clearly labelled as an illustration.

Tools by task

Task What you want to know Example tools
Hashing and identification What exactly is this file? sha256sum, PowerShell Get-FileHash, file, TrID, Detect It Easy
Strings Readable text inside the file strings, FLOSS
Binary viewing Raw bytes and structure Hex editors (HxD, ImHex), 010 Editor
Executable structure Headers, sections, imports PE-bear, CFF Explorer, pefile (Python), PEStudio
Document analysis Macros, scripts, embedded objects oletools, pdf-parser
Process and system monitoring Files, registry, processes at runtime Process Monitor, Process Explorer, Autoruns
Registry and file diffing What changed between two states Regshot
Network Packets, DNS, HTTP Wireshark, tcpdump, fake-internet tools
Sandboxes Automatic behaviour reports Cuckoo-style sandboxes, hosted services
Disassembly and decompilation Read the code Ghidra, IDA, radare2, Binary Ninja
Debugging Step through and unpack x64dbg, WinDbg, gdb
Detection Match patterns across files YARA, ClamAV
Scripting Glue everything and automate Python, PowerShell, Bash

Notice how the table follows the analysis workflow: hashing and strings are cheap and early, debuggers come last.

Python as the analyst's glue

Python is popular because it can parse binaries, call APIs, process logs and generate reports. Libraries commonly used include pefile for Windows executables, yara-python for rules, capstone for disassembly and scapy for packets. In this course the browser Python runner cannot install every library, so the exercises use the standard library to teach the ideas directly.

Choose tools by question

Instead of memorizing tool names, ask the question first.

flowchart TD
    Q["What do I want to know?"] --> A{"What is the file?"}
    Q --> B{"What does it say?"}
    Q --> C{"What does it do?"}
    Q --> D{"How does the code work?"}
    A --> A1["Hashes, file type"]
    B --> B1["Strings, headers, imports"]
    C --> C1["Sandbox, monitors, packet capture"]
    D --> D1["Disassembler, debugger"]

Match the question to a category of tool, then pick whichever tool in that category you know well.

Practice: a tiny tool selector

This script stores a question-to-tool mapping and prints a suggested toolbox for a task list. It is trivial on purpose: the real skill is knowing the mapping.

Python Which tool category for which question?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Taking notes that survive

Analysts forget details quickly. Notes should be written while you work, in a structure you can turn into a report. A good note contains:

  1. What you did: the tool, the command and the time.
  2. What you saw: the exact output (copy it), not a paraphrase.
  3. What you think it means: your interpretation, kept separate from the observation, with a confidence level.
  4. Open questions: what to check next.

Many teams use a text file, a wiki or a notebook per case. The golden rule is to separate observation from interpretation. "The process wrote HKCU...\Run\Updater" is an observation. "It establishes persistence" is an interpretation.

Screenshots and artifacts

Save evidence (screenshots, packet captures, tool exports) next to your notes with file names that include the sample ID and the time. Hash anything you may need to defend later.

Practice: a notes parser

The next example reads a plain-text analysis log and builds a summary grouped by type. The format uses prefixes: OBS, INT, Q. You can adopt something like it.

Python Parse structured analyst notes

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice that each interpretation can be traced to observations made earlier. That traceability is what makes a report credible.

Building skills over time

  • Learn one tool per category deeply.
  • Keep a personal glossary of terms and Windows internals.
  • Write small scripts for jobs you repeat; the next lesson set (Static Analysis) starts one.
  • Review old cases: what would you do faster now?

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which category of tool would you use first on a brand-new sample?

    Identification and hashing are the cheapest, safest steps and tell you what you are dealing with.
  2. 2. Why should observations and interpretations be recorded separately?

    Separating what you saw from what you think it means keeps your evidence trustworthy.
  3. 3. What is Regshot-style registry diffing used for?

    You snapshot the registry before and after running a sample and compare the two to see the changes.
  4. 4. Why is Python popular with analysts?

    Python is quick to write and has libraries for PE files, YARA, disassembly and packets, so it glues the other tools together.

Summary

  • Choose tools by task: identify, read, inspect, monitor, capture, disassemble, debug, detect.
  • Start with cheap tools and move to expensive ones only when needed.
  • Python is the glue that automates repeated jobs.
  • Keep notes while you work and separate observation from interpretation.
  • Save evidence beside the notes with sample IDs and times.

Next: Hashing and Fingerprinting Samples