Atola Technology Sets A New Bar For Acquisition Tools With Atola TaskForce

Today Atola Technology announced the launch of Atola TaskForce, the next generation of evidence acquisition tools. Having optimized its imaging algorithm in 2016 to match maximum speeds drives operate at, Atola now presents a system that further solves the market’s number one issue: time required for evidence acquisition. TaskForce’s robust hardware, which includes multi-core Xeon CPU, supports 8+ concurrent imaging sessions at overall speed of 15 TB/hour.

“We are thrilled to have beaten our own speed record,” says CEO Dmitry Postrigan. “Our previous flagship product, Atola Insight Forensic acquired up to 1.8 TB/hour, which secured its place as the most efficient forensic imager in the world. With Atola TaskForce, our clients are able to image up to 15 TB/hour when running 8 or more concurrent imaging sessions, and it makes this device a uniquely fast and mighty acquisition tool. Certainly, our signature damaged drives capability is supported in this tool”.

Source evidence drives can be imaged to up to 5 targets each. Targets may include other drives or E01/RAW files located on a network server. TaskForce is equipped with two 10Gb Ethernet ports, thus enabling high data transfer rates.

All 18 ports of the hardware unit can be used as either a source or a target thanks to the Source/Target switch. In Source mode is enabled, write protection is enabled.
The 18 ports include
– 6 SATA
– 6 SATA/SAS
– 4 USB
– IDE
– Extension slot (for Atola Thunderbolt, Apple PCIe SSD and M.2 PCIe/SATA SSD extension modules).

Get The Latest DFIR News!

Top DFIR articles in your inbox every month.


Unsubscribe any time. We respect your privacy - read our privacy policy.

Atola Technology’s focus is on creating reliable and forensically sound acquisition process for forensic experts dealing with substantial volumes of evidence data.

About Atola Technology
Atola Technology is a hardware and software development company founded in 2003 and based in Vancouver, Canada. The company’s software engineers, including its founder and CEO Dmitry Postrigan have deep expertise in data and firmware recovery, and focus on creating highly efficient and user-friendly hard drive imaging tools for the global forensic market.

Leave a Comment

Latest Videos

Quantifying Data Volatility for IoT Forensics With Examples From Contiki OS

Forensic Focus 22nd June 2022 5:00 am

File timestamps are used by forensics practitioners as a fundamental artifact. For example, the creation of user files can show traces of user activity, while system files, like configuration and log files, typically reveal when a program was run. 

Despite timestamps being ubiquitous, the understanding of their exact meaning is mostly overlooked in favor of fully-automated, correlation-based approaches. Existing work for practitioners aims at understanding Windows and is not directly applicable to Unix-like systems. 

In this paper, we review how each layer of the software stack (kernel, file system, libraries, application) influences MACB timestamps on Unix systems such as Linux, OpenBSD, FreeBSD and macOS.

We examine how POSIX specifies the timestamp behavior and propose a framework for automatically profiling OS kernels, user mode libraries and applications, including compliance checks against POSIX.

Our implementation covers four different operating systems, the GIO and Qt library, as well as several user mode applications and is released as open-source.

Based on 187 compliance tests and automated profiling covering common file operations, we found multiple unexpected and non-compliant behaviors, both on common operations and in edge cases.

Furthermore, we provide tables summarizing timestamp behavior aimed to be used by practitioners as a quick-reference.

Learn more: https://dfrws.org/presentation/a-systematic-approach-to-understanding-macb-timestamps-on-unixlike-systems/

File timestamps are used by forensics practitioners as a fundamental artifact. For example, the creation of user files can show traces of user activity, while system files, like configuration and log files, typically reveal when a program was run.

Despite timestamps being ubiquitous, the understanding of their exact meaning is mostly overlooked in favor of fully-automated, correlation-based approaches. Existing work for practitioners aims at understanding Windows and is not directly applicable to Unix-like systems.

In this paper, we review how each layer of the software stack (kernel, file system, libraries, application) influences MACB timestamps on Unix systems such as Linux, OpenBSD, FreeBSD and macOS.

We examine how POSIX specifies the timestamp behavior and propose a framework for automatically profiling OS kernels, user mode libraries and applications, including compliance checks against POSIX.

Our implementation covers four different operating systems, the GIO and Qt library, as well as several user mode applications and is released as open-source.

Based on 187 compliance tests and automated profiling covering common file operations, we found multiple unexpected and non-compliant behaviors, both on common operations and in edge cases.

Furthermore, we provide tables summarizing timestamp behavior aimed to be used by practitioners as a quick-reference.

Learn more: https://dfrws.org/presentation/a-systematic-approach-to-understanding-macb-timestamps-on-unixlike-systems/

YouTube Video UCQajlJPesqmyWJDN52AZI4Q_i0zd7HtluzY

A Systematic Approach to Understanding MACB Timestamps on Unixlike Systems

Forensic Focus 21st June 2022 5:00 am

This error message is only visible to WordPress admins

Important: No API Key Entered.

Many features are not available without adding an API Key. Please go to the YouTube Feed settings page to add an API key after following these instructions.

Latest Articles

Share to...