In contrast to other great incident response tools, which are mainly case-based and support the work of CERTs, SOCs etc. in their daily business, DFIRTrack is focused on handling one ore more major incidents with a lot of affected systems as it is often observed in APT cases. It is meant to be used as a tool for dedicated incident response teams in large cases. So, of course, CERTs and SOCs may use DFIRTrack as well, but they may feel it will be more appropriate in special cases instead of every day work.
In contrast to case-based applications, DFIRTrack rather works in a system-based fashion. It keeps track of the status of various systems and the tasks and forensic artifacts associated with them, keeping the analyst well-informed about the status and number of affected systems at any time during the investigation phase up to the remediation phase of the incident response process.
The main entities for incident tracking are:
- notes and reportitems
One focus is the fast and reliable import and export of systems and associated information. The goal for importing systems is to provide a fast and error-free procedure. Moreover, the goal for exporting systems and their status is to have multiple instances of documentation: for instance, detailed Markdown reports for technical staff vs. spreadsheets for non-technical audiences without redundancies and deviations in the data sets.
The following functions are implemented for now:
- quick change of status of systems.
- fast automatic generation for tasks and artifacts to one or more systems
DFIRTrack is developed for deploying on Ubuntu. Other distributions may work but were not tested. At the moment the project will be focused on Ubuntu LTS releases.
For fast and uncomplicated installation on a dedicated server including all dependencies an Ansible playbook and role were written (available in
For information about deployment with Ansible look at the Wiki - Ansible.
For installation with your own setup or for testing look at the Wiki - Installation.
The application was created by implementing the following libraries and code:
There are two main branches:
The master branch is stable and reflects major version releases. New features and changes are added to the develop branch and merged into master after extensive testing. Everything merged into develop should run stable too but might need manual changes. To use the current features, please try an installation of develop.
DFIRTrack uses the OpenAPI specification that is provided by the Django REST framework.
To retrieve the current OpenAPI scheme just visit the the DFIRTrack URL
If you want to use the DFIRTrack API you can use the following API clients:
LICENSE file in the root directory.
Even if some basic error checking is implemented, as of now the usage of DFIRTrack mainly depends on proper handling.
DFIRTrack was not and most likely will never be intended for usage on publicly available servers. Nevertheless some basic security features were implemented (in particular in connection with the corresponding ansible role) always install DFIRTrack in a secured environment (e. g. a dedicated virtual machine or in a separated network)!