The method
Requirements first, then proof
DEVI tests its tools the way the NIST Computer Forensics Tool Testing program tests forensic tools: write down what the tool must do, build test cases from that list, run them on known data, and record every result.
CFTT is a NIST program. This is DEVI's own testing, following the same approach. What CFTT testing shows
Write down every function
Each release starts from a written inventory of everything the tool does, taken from its source: every button, menu, setting, message and command-line option.
Test each one on screen
Every row of that inventory is exercised in the installed, signed build, on screen, and the result is recorded with proof.
Check against known answers
Every hash is compared with an independent tool, such as Windows Get-FileHash, and record hashes are recomputed separately.
Use public and synthetic data
Public forensic test images and generated files, including the hard cases: empty and very large files, Unicode names, long paths, locked files and malformed hash lists. Never case data.
Fix, retest, then release
Anything that fails is fixed and tested again in a new signed build before that release is published.
Built in
A test in every tool
Run it on your own computer, under your own procedures, before you rely on a release.
DEVI Validate self-test
Runs from inside the app, so a lab can check a release on its own computer. See DEVI Validate
DEVI Decrypt self-test
Checks decryption against an embedded synthetic package before you trust a run. See DEVI Decrypt
DEVI Registry check script
verify_registry.py recomputes the content hash and checks every reference. The app checks that hash before it shows a record. See DEVI Registry
Every download
Verification on every download
The file you run is the file DEVI published. You do not have to take our word for it.
A SHA-256 for every file
Every release file has a published SHA-256. Check it with Get-FileHash or certutil. How to check
Signed apps and installers
Authenticode signatures with a timestamp. Windows shows the signer in the file's Properties. Check a signature
Signed updates
Updates come from a signed feed, and each update is checked against its SHA-256. Nothing downloads until you confirm it. Read the release notes
In your lab
Validate it your way
Labs validate every tool before they rely on it. DEVI is built to make that quick.
- Check the download's SHA-256 and signature.
- Run the tool's built-in self-test or check script.
- Hash a public test image with DEVI Validate and with the tool you use today, and compare.
- Keep the PDF verification record with your validation file.
Request a demo
See the testing for yourself
A live walkthrough on synthetic data, for verified examiners and agencies. We review every request, usually within the same business day.