CyberKit

Console Command History

Also called Command History, Console History Buffer.

Typed commands and console output recoverable from RAM.

What it is

The buffers the console subsystem keeps for command-line sessions, holding the history of commands a user typed and, often, the screen output those commands produced. This state lives in the memory of the process that hosts the console.

Why it matters

Recovering command history from a memory image can reconstruct exactly what an attacker typed and saw at an interactive shell, even when no logging was enabled. It is some of the most direct evidence of hands-on-keyboard activity available.

In practice

Pulling the full sequence of reconnaissance and credential commands an intruder ran from the console history buffers in a RAM capture.

What to look for

  • Commands typed in cmd or PowerShell consoles.
  • Output still in console buffers.
  • Commands from consoles that are already closed.

Common mistake

Waiting too long. Console history disappears when the process ends.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Volatility 3 Open source

    A widely used open source framework for analyzing memory images with plugins. Our notes.

  • Velociraptor Open source

    Can collect memory and query live process memory across many hosts. Our notes.

  • CrowdStrike Falcon Commercial

    EDR agents watch memory activity on the host, such as injection and unbacked code.

Read next

Sources