Skip to content

About

A repo for example workflows using SOLVE-IT techniques that can be rendered in the SOLVE-IT builder

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

15 Commits

Folders and files

Repository files navigation

solveit-workflows

Example workflows built from SOLVE-IT techniques, held as JSON files that the SOLVE-IT Workflow Builder can open and render as a diagram.

Each entry below has an Open link that loads the file straight into the builder, so a workflow can be looked at without downloading anything.

Drafts

Linear workflows describing a process from start to finish. These are working versions and are expected to change.

Workflow What it covers
find_files_by_hash.json Seized media through to a tag-based automated report, with hash-based identification of the relevant files. Open

Illustrations

These are not linear workflows and make use of the Workflow Builder to create diagrams of bigger systems.

Workflow What it covers
recreation-of-abstract-forensic-tool-figure-1.json Figure 1 of Hargreaves, Nelson and Casey (2024), redrawn using SOLVE-IT techniques. Open
modern-forensic-tool-architectures.json The processing a current tool suite performs on a disk image or mobile extraction, in regions covering operating system artefacts, application artefacts, artefact aggregation and dynamic search. Open
use-an-ai-based-prompt-for-interrogating-case-data.json The same architecture with an AI layer added on top, showing which underlying techniques an AI-driven query of the case data depends on. Open

Imaging

Workflows for the acquisition of a disk image and the checks that show the stored image matches what was read from the source device. They model the separation of hash verification techniques proposed in SOLVE-IT issue #462: DFT-1042 compares a hash of the data read from the source with a hash of the data as stored, while DFT-1204 compares a hash of the stored data with a hash recorded when the image was written.

Workflow What it covers
imaging_with_hash_verification.json Write blocking and reading the source device, writing the image to a forensic container and recording the acquisition hash in it (DFT-1208), then hash verification both during imaging (DFT-1042) and afterwards against the recorded hash (DFT-1204). Open
image_hash_verification.json Verifying a stored forensic image container against the hash recorded in it, at any point after imaging has finished (DFT-1204). Open

Demonstrators

Workflow What it covers
simplified_imaging_demo.json Removing a disk from a device, choosing between a hardware and a software write blocker, and storing the result in a forensic container format. Open

legacy/simplified_imaging_demo.json is an earlier version of the same workflow, kept in the older file format (short keys such as tt, n and e). The builder still imports it and converts it the first time it is saved.

Opening a workflow

The Open links use the builder's #fetch= form, which takes the address of a workflow file and loads it:

https://workflows.hargs.co.uk/#fetch=https://raw.githubusercontent.com/chrishargreaves/solveit-workflows/main/<path>.json

The workflow opens as an unsaved session, so use Save to library in the builder to keep any edits. Alternatively, download the .json file and use Import on the welcome screen, or paste a GitHub file address into Load from URL…, which converts it to the raw address for you.

Proposing a change

Open the workflow in the builder, edit it, then use Export workflow ▾ → JSON. Submit the updated file through GitHub in the usual way, by editing the file in the repository and choosing Propose changes to open a pull request.

Licence

Apache License 2.0. See LICENSE.

About

A repo for example workflows using SOLVE-IT techniques that can be rendered in the SOLVE-IT builder

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors