Volatile Memory Analysis


Volatile memory analysis is a live-system forensic technique in which you collect a memory dump and perform analysis in an isolated environment.

  • must first establish a trusted command shell
  • next, establish a data collection system and method for transmitting data
  • compute hash after memory capture
    • don’t need to calculate hash before data acquisition due to volatile nature of memory
  • common to acquire volatile data in a dump file for offline examination
    • dump is a complete copy of every bit of memory or cache recorded in permanent storage or printed on paper
  • data in memory is not consistently maintained during system operation
    • impossible to freeze the machine states in the course of data acquisition
  • there are 2 types of memory:
    • Stack (S)
      • memory is allocated to local variables and parameters within each function
        • allocated based on the last-in, first-out (FIFO) principle
      • when a program is running,
        • program variables use the memory allocated to the stack area again and again
      • this segment is the most dynamic area of the memory process
    • Heap (H)
      • Dynamic memory for a program comes from the heap segment
      • process may use a memory allocator such as malloc to request dynamic memory
      • when this happens, the address space of the process expands
      • data in the heap area can exist between function calls
      • memory allocator can reuse memory that has been released by the process
      • so, heap data is less stable than the data in the data segment
  • when a program is running,
    • code, data, and heap segments are usually placed in a single contiguous area
    • stack segment is separated
      • expands with the memory allocated space
  • memory can be viewed as a large array that contains many segments for different processes
  • memory grows and shrinks depending on system usage
    • due to either
      • growth of heap data
      • or expansion and release of stack data
    • data in code segment is static
    • stack data has greater effect than heap data

Tools

  • PsList
    • use to view process and thread statistics on a system
    • does not reveal the presence of the rootkit or other processes the rootkit has hidden
    • part of PsTools
  • PsInfo
    • from PsTools
    • tells you system uptime, operating system details, and other system info
    • good background info for forensics report
  • ListDLLs
    • allows you to view the currently loaded dynamic-link libraries (DLLs) for a process
    • cannot show DLLs loaded for hidden processes
  • PsLoggedOn
    • helps discover users who have logged on both locally and remotely
    • tells who is logged on to shares on the current machine
    • part of PsTools
  • netstat
    • displays incoming and outgoing network connections
    • displays routing tables and network interface statistics
    • use to view network connections on a machine