OS X Auditor is a free Mac OS X computer forensics Tool
OS X Auditor parses and hashes the following artifacts on the running system or a copy of a system you want to analyze:
- The kernel extensions
- The system agents and daemons
- The third party's agents and daemons
- The old and deprecated system and third party's startup items
- The users' agents
- The users' downloaded files
- The installed applications
- The users' quarantined files
- The users' Safari history, downloads, topsites, LastSession, HTML5 databases and localstore
- The users' Firefox cookies, downloads, formhistory, permissions, places and signons
- The users' Chrome history and archives history, cookies, login data, top sites, web data, HTML5 databases and local storage
- The users' social and email accounts
- The WiFi access points the audited system has been connected to (and tries to geolocate them)
It also looks for suspicious keywords in the .plist themselves.
It can verify the reputation of each file on:
- Team Cymru's MHR
- your own local database
- /var/log (-> /private/var/log)
- the user's ~/Library/logs
- rendered as a simple txt log file (so you can cat-pipe-grep in them… or just grep)
- rendered as a HTML log file
- sent to a Syslog server
How to installJust copy all files from GitHub.
If you plan to run OS X Auditor on a Mac, you will get a full plist parsing support with the OS X Foundation through pyobjc:
- pip install pyobjc
If you can't install pyobjc or if you plan to run OS X Auditor on another OS than Mac OS X, you may experience some troubles with the plist parsing:
- pip install biplist
- pip install plist
These dependencies will be removed when a working native plist module will be available in python
How to run
- OS X Auditor runs well with python >= 2.7.2 (2.7.9 is OK). It does not run with a different version of python yet (due to the plist nightmare).
- OS X Auditor is maintained to work on the lastest OS X version. It will do its best on older OS X versions.
- You must run it as root (or via sudo) if you want to use is on a running system, otherwise it won't be able to access some system and other users' files.
- If you're using API keys from environment variables (see below), you need to use the sudo -E to use the users environment variables.
eg. [sudo -E] python osxauditor.py -a -m -l localhashes.db -H log.html
Author of the Tool
Jean-Philippe Teissier - @Jipe_ & al.
Download OS X Auditor