![\"Atola](\"https:\/\/atola.com\/blog\/wp-content\/uploads\/2016\/07\/Atola-booth-2.jpg\")
<\/p>\n<\/p>\n
We were exhibiting with Atola Insight Forensic at Enfuse and Techno Security conferences and received plenty of questions from people visiting our booth. Some of these questions were repeatedly asked,\u00a0so sharing them and their corresponding answers in this blog makes sense. We do hope you find the information provided here helpful!<\/p>\n
You can always observe an actual imaging performance of 30 GB\/min in Atola Insight Forensic v4.5 with a couple of Samsung 850 Pro solid-state drives used as source and target devices.<\/p>\n
We produce the only solution that is specifically designed to support damaged media.<\/p>\n
Our users usually begin with automatic diagnostics for an evidence drive. It takes a couple of minutes yet saves much of time and energy. It detects drive issues such as PCB instability, problems with motor, short circuit, firmware errors, degraded or even nonworking heads, and physical media surface damage. Afterward, you can make a decision on what to do next with the evidence drive.<\/p>\n
Even if you work with severely damaged source device, the imaging engine enables you to:<\/p>\n
Atola Insight has file recovery integrated with imaging. By browsing the target image directory tree, you can always see which source file sectors are bad sectors or even were read with the ReadLong ATA command (without ECC).<\/p>\n
Last but not least, Atola Insight Forensic can clear any unknown ATA password from the hard disk drive in just a minute.<\/p>\n
Atola Insight Forensic supports imaging to three image file types:<\/p>\n
The first two are raw files, bit-to-bit source copies.\u00a0 The 3rd target file type is E01 (Encase). It can be either compressed or not. Imaging to non-compressed E01 is several times faster and does not depend on CPU speed and core count.<\/p>\n
We have two goals here when dealing with severely damaged source drives:
\n1) Get as much data as possible
\n2) Decrease the number of failed read attempts to finish imaging with a still-alive evidence drive<\/p>\n
Atola Insight Forensic uses a fast imaging map, thereby enabling us to run the whole process in multiple passes. The tool uses large blocks with short time-outs on the first few passes and then smaller blocks with longer time-outs on the last pass to image the tough areas. This provides the best possible results in the shortest amount of time<\/p>\n
Atola Insight\u2019s ability to disable damaged heads can just save your evidence! Other imagers merely kill the drive during imaging. Imagine having seven of eight good heads. You can just image with all of them except the damaged one. Afterward, you can begin analysis of 87% of the acquired data and at the same time try to replace the damaged head. A physical head swap is always a risky challenge.<\/p>\n
The imaging engine contains many automatic rules. For example, it resets or power-cycles the source when the source drive freezes. It can apply a reverse imaging direction in particular cases. Here is what is useful when dealing with damaged evidence: Two imaging reports are created before and after the process. Both include not only imaging information but also SMART tables, thus enabling you to see what happened to the source drive during the process.<\/p>\n
All source ports are write-protected:<\/p>\n
On top of that, overcurrent protection detects when the hard drive draws abnormal current and stops the hard drive to prevent any further damage.<\/p>\n
Every action in Atola Insight is followed by automatically created case reports. The case management system gets a new report even if you physically flip the DiskSense unit\u2019s write protection switch. Additionally, every case report includes mandatory information about the device, DiskSense unit, current PC, OS, and user.<\/p>\n","protected":false},"excerpt":{"rendered":"
We were exhibiting with Atola Insight Forensic at Enfuse and Techno Security conferences and received plenty of questions from people visiting our booth. Some of these questions were repeatedly asked,\u00a0so sharing them and their corresponding answers in this blog makes sense. We do hope you find the information provided here […]<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"yoast_head":"\n