BAM / DAM
Also called Background Activity Moderator, Desktop Activity Moderator.
Registry record of program execution per user with last-run timestamps.
What it is
The Background Activity Moderator and Desktop Activity Moderator, Windows components whose registry entries record the full paths of executables run per user along with the last time each ran.
Where it lives
HKLM\SYSTEM\CurrentControlSet\Services\bam\State\UserSettings\<SID> (DAM is a separate, Connected-Standby-only artifact under \dam\State\UserSettings\<SID>)
Why it matters
BAM/DAM give a clean, user-scoped list of recently executed programs with timestamps, often capturing malware execution that other artifacts missed and providing an independent corroboration point for an execution timeline.
In practice
A BAM entry tied execution of a malicious binary to a specific user SID and a timestamp matching the intrusion window.
What to look for
- Executable paths with last run times per user SID.
- Tools run from temp or removable media.
- Entries for programs later deleted.
Common mistake
Expecting long history. BAM entries are cleaned up after about a week.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Autopsy Open source
A graphical forensics platform that parses file systems and common artifacts. Our notes.
-
Eric Zimmerman's tools Free
Command line parsers for Windows artifacts such as the MFT, Prefetch and the Registry. Our notes.
-
Plaso Open source
Builds a super timeline from many artifacts in one image. Our notes.
-
Velociraptor Open source
Collects the same artifacts remotely, without pulling a full disk image. Our notes.
Read next
- UserAssist: Per-user registry record of GUI program launches, counts, and last-run time.
- AmCache: Registry hive recording executed/installed programs with hashes and timestamps.
- SRUM: Windows database logging per-app resource and network usage over time.