Knowledge Base Structure Changelog

Changes to the knowledge base schema.

New objective: Evaluate evidence (2026-07-14)

Added “Evaluate evidence” as a new objective, taking the knowledge base from 23 to 24 objectives. It sits between “Reconstruct events” and “Document digital forensic activities”, and covers techniques concerned with assessing what the recovered material supports rather than recovering it. The objective was introduced alongside its first technique, Generate Alternative Hypotheses (DFT-1195). Anything consuming the objective list, including issue forms and generated views, reflects the additional entry.

Weakness classes migration (2026-03-19)

Migrated weakness ASTM error classification from 6 individual boolean-style fields (INCOMP, INAC-EX, etc.) to a single categories list field. Each class code is now prefixed with ASTM_ (e.g. ASTM_INCOMP, ASTM_INAC_EX). 271 weakness files updated. Issue forms changed from checkboxes to textarea input. Ontology updated to use hasWeaknessClass object property with ASTMErrorCategory named individuals.

References format update to DFCites (2026-03-18)

Migrated references to the DFCite format (PR #325). This changes references to a top level object in the data folder. Uses .txt or .bib to index them. Added citation utilities, reference matching, and updated models. Introduces ‘relevance_summary_280’ field across entire knowledge base as part of DFCite change. 340 files changed.

ID scheme migration (2026-03-11)

Migrated all knowledge base entries to a new ID naming scheme (PR #320). See article here. 1,589 files changed across techniques, weaknesses, mitigations, and references. Follow-up fixes:

  • Patched missing contributors due to ID scheme switch
  • Hotfix for broken deep links due to naming change
  • Restored CASE classes lost in migration
  • Fixed ID scanner and assignment scripts to handle pre-migration formats (PR #337)

CASE/UCO input classes added (2026-02-22)

Added CASE/UCO input class fields to techniques across the knowledge base (PR #274, PR #276). This complemented the existing CASE/UCO output classes, enabling techniques to describe both their required inputs and produced outputs in terms of the CASE/UCO ontology. 170+ files updated.

CASE/UCO classes updated to full IRIs (2026-02-04)

Updated all CASE/UCO output class references to full IRIs and generalised the field to support both input and output classes (PR #258). 106 files changed.

Initial knowledge base upload (2025-01-09)

First commit of SOLVE-IT content — 378 files covering techniques, weaknesses, and mitigations in JSON format.