Aftermath can be leveraged by defenders in order to collect and subsequently analyze the data from the compromised host. Aftermath can be deployed from an MDM (ideally), but it can also run independently from the infected user's command line.
To build Aftermath locally, clone it from the repository
git clone https://github.com/jamf/aftermath.git
cd
into the Aftermath directory
cd <path_to_aftermath_directory>
Build using XCode
xcodebuild
cd
into the Release folder
cd build/Release
Run aftermath
sudo ./aftermath
Aftermath needs to be root, as well as have full disk access (FDA) in order to run. FDA can be granted to the Terminal application in which it is running. If using an MDM to deploy Aftermath, FDA can be granted through PPPC in your MDM solution.
The default usage of Aftermath runs
./aftermath
To specify certain options
./aftermath [option1] [option2]
Example
./aftermath -o /Users/user/Desktop --deep
-o -> specify an output location for Aftermath collection results
usage: -o Users/user/Desktop
--analyze -> Analyze the results of the Aftermath results
usage: --analyze <path_to_aftermath_collection_file>
--cleanup -> Remove Aftermath Response Folders
--deep -> Perform a deep scan of the file system for modified and accessed timestamped metadata
WARNING: This will be a time-intensive scan.
- Stuart Ashenbrenner
- Matt Benyo
- Jaron Bradley
- Ferdous Saljooki
This project leverages the open source TrueTree project, written by Jaron Bradley.