Making volatility 3 profile - 20/08/2026 Let's assume we are dealing with the compromised system. We first need to find the debugging kernel. This kernel had must been compiled with debugging symbols (volatility 3 need these to find out info) and after compilation, it should not be stripped. Please note, due to the huge size of this file, these are not generally comes now with the OS. On the compromised system run this command: find / -name vmlinu\* -size +100M 2>/dev/null You may get the following: /usr/lib/debug/boot/vmlinux-5.10.0-21-amd64 --> If you find this then this means it is the debugging version. /boot/vmlinuz-5.10.0-21-amd64 --> and if you find this then it is kernel version file /usr/lib/debug/boot/vmlinux-5.10.0-21-amd64 /usr/lib/debug/boot/vmlinux-5.10.0-21-amd64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=5e5d3209033f927baa64…, with debug_info, not stripped --> This on...
Bulk Extractor Using this tool, we will extract data from memory and then analysis during linux or windows IR activities. As a prerequisite, we need a memory image. For example our memory image name is ubuntu.20211208.mem.gz Someday we will show how to capture memory images using avml or lime tool or other. See my medium writeup. ( https://mahimavi.medium.com/linux-memory-forensics-memory-capture-using-lime-avml-and-analysis-using-volatility-5d46c808158a ) From your linux forensic machine, run following commands: gunzip /images/All-Images/HudaksHoneypot/ ubuntu.20211208.mem.gz Now you will have this file - ubuntu.20211208.mem Now we will use bulk extractor tool. This tool available in kali and sans forensics machine as well. bulk_extractor -o be-output /images/All-Images/HudaksHoneypot/ubuntu.20211208.mem (Remember be-output directory should not be created early. This tool will create this directory on its own) You will see various files captured and extracted...