top of page
Search

Comprehensive Guide to Identifying Application Execution in Windows Forensics

  • Feb 17, 2024
  • 2 min read

Updated: Feb 25



When investigating digital forensics cases, confirming application execution is crucial. Whether analyzing malware execution, tracking user activity, or validating forensic evidence, understanding where and how to find execution artifacts is essential.

Many articles on my website discuss different execution artifacts.

However, putting them all together in a structured way helps streamline investigations.

This article serves as a timeline and reference guide, consolidating various forensic artifacts that indicate application execution, their advantages, disadvantages, and relevant analysis techniques.

------------------------------------------------------------------------------------------------------------


Key Artifacts for Identifying Application Execution

Each artifact provides unique insights, and choosing the right one depends on the investigation’s requirements. Below is a list of the most important artifacts, along with links to detailed articles that explain their forensic significance.



1. ShimCache (AppCompatCache)

ShimCache is a valuable artifact for identifying application execution, especially when prefetching is disabled. However, it does not provide timestamps for execution, only last modification times.




2. TaskBar Feature Usage

This artifact helps track executed applications based on user interactions with the Windows Taskbar.




3. Amcache.hve

Amcache.hve is one of the most reliable sources for identifying program execution, storing detailed information about executed applications, including timestamps.




4. Jump Lists

Jump Lists store data about recently opened applications and files, making them useful for tracking execution history.



5. Prefetch Files

Prefetch files record program execution details, including the exact timestamp of when an application was last run.



6. Program Compatibility Assistant (PCA)

This artifact logs execution history when an application triggers compatibility warnings.



7. CapabilityAccessManager

This registry artifact logs application access to sensitive components like the microphone and camera, indirectly confirming execution.




8. SRUM (System Resource Usage Monitor)

SRUM records extensive details about executed applications, including their network usage and execution time.




9. Last Visited MRU (Most Recently Used)

This registry artifact provides insights into recently accessed applications and files.



10. Run Dialog (RunMRU)

Tracking commands executed in the Windows Run dialog provides additional evidence of application execution.



  1. RADAR and MUICache

RADAR and MUICache provides extensive details about executed applications



----------------------------------------------------------------------------------------------------------

Conclusion

Each of these artifacts plays a unique role in application execution analysis. While some provide direct evidence with timestamps, others offer indirect indicators. Depending on the investigation's requirements, a combination of these sources ensures a more comprehensive analysis.


If you want to dive deeper, refer to the linked articles for detailed explanations and practical analysis techniques.
Happy hunting!

------------------------------------------------------Dean-----------------------------------------


 
 
 

Comments


bottom of page