Case EE51B1 · Blue team / DFIR · L2 Practitioner

Prefetch, Amcache and Shimcache

Practise as: Explain itLevel: L2 Practitioner
  1. 01 What is it?
  2. 02 How is it abused?
  3. 03 How do you stop it?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Prefetch (.pf in C:\Windows\Prefetch): run count and up to 8 last run times on Win8+; often disabled by default on servers.
  2. Amcache.hve records path, SHA1 and metadata of programs present or run; strong for hashes, weaker as proof of execution.
  3. Shimcache (AppCompatCache, SYSTEM hive) shows a file existed; on Win10+ it does not prove execution and writes at shutdown.
  4. Attackers delete .pf files, rename tools and timestomp; deletion itself leaves gaps you can spot in $UsnJrnl and SRUM.
  5. Corroborate across artifacts (BAM, UserAssist, 4688, EDR) and collect early; one artifact alone rarely proves execution.

If the interviewer pushes back

  • Shimcache lists a renamed psexec on a server where Prefetch is off. How do you prove whether and when it ran?

More Blue team / DFIR cards

All Blue team / DFIR cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09