Below is a quick guide for dumping and analyzing windows and linux memory. If you wish to utilize the volitility framework it can be found at volatilityfoundation.org. This guide will help you with some of the challenges available on CyDefe Labs. Check those out at Labs.CyDefe.com
Check back frequently for more guides, tips, and trick with DFIR, pentesting, reverse engineering and much much more. Many of the guides and tips we will be post will help you in real world environments and with our platform. Happy hacking everyone.
MEMORY ACQUSITION
WINPMEM/LINPMEM
a. C:> winpmem_.exe -o F:\mem.aff4
b. C:> winpmem_.exe F:\mem.aff4 -e PhysicalMemory -o mem.raw
a. ./linpmem_.post4 -o F:\mem.aff4
b. ./linpmem_.post4 F:\mem.aff4 -e PhysicalMemory -o mem.raw
a. sudo dd if=/dev/fmem of=/tmp/memory.raw bs=1MB
VOLATILITY USAGE
Example usage: ./volatility__lin64_standalone --profile= -f
LISTING AVAILABLE PROFILES
a. ./volatility__lin64_standalone --info
ROGUE PROCESS IDENTIFICATION
a. # ./volatility__lin64_standalone --profile= pslist -f
a. # ./volatility__lin64_standalone --profile= psscan -f
a. # ./volatility__lin64_standalone --profile= pstree -f
ROOTKIT IDENTIFICATION
a. # ./volatility__lin64_standalone --profile= psxview -f
a. unlinked drivers
i. # ./volatility__lin64_standalone --profile= modscan -f
a. -p Operate only on specific PIDs
b. -Q Only scan critical processes and DLLS
i. # ./volatility__lin64_standalone --profile= apihooks -f
a. # ./volatility__lin64_standalone --profile= ssdt | egrep –v ‘(ntoskrnl|win32k)’ -f
a. -r Analyze drivers matching REGEX name pattern
i. # ./volatility__lin64_standalone --profile= driverirp –r tcpip -f
a. # ./volatility__lin64_standalone --profile= idt -f
NETWORK ARTIFACTS
a. # ./volatility__lin64_standalone --profile= connections -f
a. # ./volatility__lin64_standalone --profile= connscan -f
a. # ./volatility__lin64_standalone --profile= sockets -f
a. # ./volatility__lin64_standalone --profile= sockscan -f
a. # ./volatility__lin64_standalone --profile= netscan -f