Imager Pro

Please add the functionality to export/dump the processed data via REST API into Python dictionaries. This data will be utilized for analysis within our AI engine as part of subsequent analytical processes.

Currently, the link generated for each custodian to navigate to their compliance portal is unique / custodian specific. This commonly results in two issues: 1) Distrust: Our employees are trained to identify potential phishing emails, and the navigation to an external link directly from their email causes them concern. 2) Difficult to Navigate: In general, needing to direct individuals to go find a specific link in their emails causes a burden. Even if a small percentage of the notified population asks questions, that actual number can overwhelm the responding Legal Hold team. By creating a common link, we can create a short link internally that can appear on help pages and show up in the intranet search.

As forensic images are created that will be segmented, those segments are recorded on the TXT log; however, they aren’t individually and independently hashed. Transportation and transfer of these segmented images can’t be verified independently and require the full image be loaded into Imager Pro for “verification.” Should just ONE segment file be corrupted in the transfer, users wouldn’t know which one to resend. It would be optimal for individual hashed segments referenced in the log so only those corrupted few could be retransmitted.

Our forensic unit in collaboration with others have decided that if a drive has over 5% of bad sectors then they have to report it to the investigator. Would you be able to run that calculation and output the percentage in the log file e.g. 'there are a total of x bad sectors which represent n% of the total sectors reported'. For units that do not require this calculation it could give them a clearer picture as to how much of the drive is unreadable. It is much more impactive to see that 25% of the drive is unreadable rather than sectors x-y

After establishing IPP for the required datasources via legal holds, we observe that some of the datasources are merged with newer accounts after the former datasources getting decommissioned. In this case, we are unsure if the former datasources are valid/Active until a new hold is placed on them. Thus, we have to manually "Synchronize" at random intervals to know about the changes in datasources. Hence if there is an option of 'Auto-Sync' at user defined time period at the IPP module, it can benefit us from knowing what datasources are changed.