In RAM forensics, which memory region is most likely to contain remnants of…
2026
In RAM forensics, which memory region is most likely to contain remnants of decrypted full-disk encryption keys?
- A.
Session Manager Subsystem (smss.exe) stack
- B.
User-mode process heaps
- C.
Non-paged pool
- D.
None of the above
Show answer & explanation
Correct answer: C
Concept
Windows organizes kernel memory into two broad pool types: the paged pool, whose pages the memory manager can write out to the system pagefile under memory pressure, and the non-paged pool, whose pages the memory manager guarantees stay resident in physical RAM for as long as the allocation is held -- because code that runs at a raised IRQL (as kernel-mode drivers do while servicing I/O) cannot tolerate a page fault. A full-disk-encryption (FDE) filter driver sits inside the kernel I/O stack and must decrypt every sector transparently at exactly those IRQLs, so its working key material has to live in memory that can never be paged out while the encrypted volume stays mounted.
Application
Apply that rule to where a decrypted FDE key can persist during a live session: the key is held by a kernel-mode driver that runs at raised IRQL during disk I/O, so the driver's allocation for that key must come from the non-paged pool -- this is exactly the region that memory-forensics tooling (for example the Volatility Foundation's BitLocker/TrueCrypt key-recovery plugins) scans in a captured RAM image, locating the driver's tagged pool allocation that still holds the resident key structure.
Cross-check
Checking the other regions against the same IRQL/residency requirement confirms the choice:
Session Manager Subsystem (smss.exe) is a user-mode process that performs one-time boot initialization (creating environment variables, mounting device mappings, launching subsystem processes); its stack holds call-frame data for that bootstrap sequence, not a kernel driver's key material.
User-mode process heaps are backed by pages in that process's working set, which the memory manager can write to the pagefile whenever it reclaims physical frames -- the opposite of the residency guarantee an FDE driver's key requires.
"None of the above" would only apply if the key lived in some region other than these three -- it does not, since the non-paged pool satisfies the IRQL/residency requirement directly.
So among the offered options, the non-paged pool is the memory region most likely to contain remnants of a decrypted full-disk-encryption key.