SOLVE-IT is intended to be built from the collective knowledge of the digital forensics community. To see what has already been contributed see the People page.

Overall process

The majority of updates to the knowledge base start in the GitHub issue tracker. There are different forms below that can be used. After submission, your suggested update will be reviewed by one of the SOLVE-IT technical reviewers. The issue tracker allows public, auditable discussion about refinements to the knowledge base. For new content this will involve issuing an ID for the new technique, weakness or mitigation.

Add new content

Add new techniques

If you have a new technique you can provide the details in a form the GitHub issue tracker. The GitHub bot will autogenerate JSON data for you ready for the repository, and once the proposal is reviewed you will be allowed a technique ID (with updated JSON data).

Add a new technique

Add new weakness

If you have identified a weakness or potential problem that those using the technique should be aware of you can add it here using a GitHub issue tracker form.

Add a new weakness

Add new mitigation

If you think there is a mitigation to an identified weakness, including linking a mitigation back to a technique, you can add it here using a GitHub issue tracker form.

Add a new mitigation

Update existing content

If you find that some content needs updating, you can also complete update forms on the GitHub issue tracker. These will also generate JSON showing the before and after representations of hte content.

Update a technique

Update a weakness

Update a mitigation

Other updates

If the updates needed do not fit within any of these please feel free to submit a general issue:

Submit a general issue