ByteCase
Documentation
Installation guidance, module documentation, storage behavior, output details, release information, and known limitations for ByteCase Tools.
Documentation that explains what the tools actually do
ByteCase documentation is intended to help examiners understand how each module works, what it creates, where it stores information, and where its responsibilities end.
Documentation will expand alongside each public release. Features that are still planned will be labeled accordingly rather than documented as though they already exist.
Start here
Explore the modules
ByteCase Intake
Build a structured digital forensics request and submit it to the assigned analyst.ByteCase Acquire
Create consistent documentation for forensic acquisition activity.ByteCase Verify
Generate saved hash manifests, rehash files later, compare results, and preserve integrity-verification records.ByteCase Notes
Planned workspace for structured forensic analysis notes.
Review the development direction
Documentation structure
As modules reach public release, each tool will receive documentation covering the following areas.
Getting started
- Purpose of the module
- Intended workflow
- Supported use cases
- Current development status
- Known limitations
Installation
- Supported operating systems
- Download location
- Release verification
- Installation or extraction steps
- Application startup
- Required dependencies
Module guides
- Creating or selecting a case
- Entering required information
- Saving work
- Generating outputs
- Reopening saved records
- Correcting or updating information
- Troubleshooting common issues
Output formats
Documentation will identify:
- Which files a module creates
- The purpose of each generated file
- Which outputs are human-readable
- Which outputs can be reopened by ByteCase
- Which outputs are intended for reports or case attachments
- How version and timestamp information is recorded
Storage behavior
The shared default ByteCase storage model is:
Path.home() \ "ByteCase" \ <case_number> \ <tool_subfolder>