Volatility 2 Index: Information, Processes, and Network
This document collects basic commands to begin analysis and investigate system status and connections.
This document compiles the basic commands to begin analysis and investigate system status and connections.
1. System Identification
Sección titulada «1. Identificación del Sistema»imageinfo
Sección titulada «imageinfo»Description: We will analyze the memory image to identify the operating system, Service Pack version, and hardware architecture. This is the first mandatory step in Volatility 2.
What it's for:
To obtain the profile (--profile) that we need for the rest of the commands. It also shows the date and time of the capture.
Example:
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw imageinfo2. Process Analysis
Sección titulada «2. Análisis de Procesos»Description:
We will list all processes running on the system by following the kernel's doubly linked list EPROCESS.
What it's for: To have an overview of what was running. Shows the PID, PPID (parent), and start time.
Example:
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=Win7SP1x64 pslistDescription: We will show processes in a visual tree format, demonstrating the parent-child relationship.
What it's for:
Very useful for detecting anomalies, such as a svchost.exe that does not hang from services.exe or a cmd.exe executed by a web browser (possible exploit).
Example:
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=Win7SP1x64 pstreepsxview
Sección titulada «psxview»Description: We compare the list of found processes using different methods (pslist, psscan, thrdproc, etc.).
What it's for:
To find hidden processes (Rootkits). If a process appears as False in the pslist column but True in psscan, it is likely hiding.
Example:
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=Win7SP1x64 psxviewcmdline
Sección titulada «cmdline»Description: We will show the command-line arguments used to launch each process.
What it's for: Vital to see if malware has been executed with specific parameters, or to see which files a legitimate program was opening.
Example:
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=Win7SP1x64 cmdline3. Network
Sección titulada «3. Red (Network)»netscan
Sección titulada «netscan»Description: We will scan active, listening, or closed network connections. (Available for Windows Vista, 7 and higher).
What it's for: To find communications with malicious IPs (C2), suspicious open ports, or malware listening for incoming connections.
Example:
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=Win7SP1x64 netscanconnscan
Sección titulada «connscan»Description:
Equivalent to netscan but for older systems (Windows XP / 2003). We will look for _TCPT_OBJECT structures.
Purpose: Similar to netscan, but limited to active or recently closed TCP connections in legacy systems.
Example:
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=WinXPSP2x86 connscansockets
Sección titulada «sockets»Description: We will list open sockets (Windows XP / 2003).
Purpose: To see which ports are open and which protocol (TCP/UDP) they use in legacy systems.
Example:
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=WinXPSP2x86 sockets
