No evidence without a hash
The evidence record and its first hash are created in one transaction, with format and length checks per algorithm. A truncated value therefore shows up at intake rather than years later at comparison time.
The module manages the evidence, not the tool
After an incident, whether a piece of evidence holds up later is rarely decided by the analysis but by the documentation of the first hour. This module provides the control layer: it creates no disk images, reads no media and analyses nothing. That stays with your own or your provider’s forensic tooling. The module holds metadata, hashes and supporting documents, in a form that cannot be altered afterwards. That covers the management duties of BSI IT-Grundschutz DER.2.2, ISO/IEC 27037 and ISO 27001:2022 A.5.28.
The evidence record and its first hash are created in one transaction, with format and length checks per algorithm. A truncated value therefore shows up at intake rather than years later at comparison time.
Taking an original into custody requires a second person, and that cannot be switched off, because DER.2.2.A10 leaves no discretion here. For working copies the witness requirement is configurable and off by default.
Origin, time, custodian, witness, seal number and acquisition method are immutable from intake onwards. A sealed investigation stays sealed via the console, the API and the AI tools too, and every rejected write attempt is logged.
The work order, legal basis and purpose become mandatory from the status "running"; in draft they may be missing. That lets an investigation be opened at three in the morning, before legal is reachable, without leaving a gap in the file later.
A file that still holds up when someone asks two years later who had the medium in their hands, and when.
Schedule a no-obligation demo – we will show you the module with your own use cases.