Reconnoitre from Sanderson Forensics updated

Sanderson Forensics are pleased to announce an update to our most recent software tool Reconnoitre.

Reconnoitre allows the forensic investigator to quickly and easily investigate images containing volume shadow copies, without the need to run VSSAdmin.

This latest version adds facilities that include querying a C4P hash server, import a .c4p export file and identify files that exist only in volume shadow copies.We have what seems to be an unusual policy in the forensic world rather than give our customers what we think they want, we are listening to them and trying to give them what they have asked for.

So when some of our first Reconnoitre users said “Could you get Reconnoitre to identify graphics files in volume shadow copies that have been identified by C4P as ‘somewhere in this SVI file’?”, “can Reconnoitre do a hash comparison using a C4P hash server?”, “could you add graphic file categorisation features” or “can you see just those files in shadow copies that are not present in the live files?” – we listened.

Get The Latest DFIR News!

Top DFIR articles in your inbox every month.


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

The latest version of Reconnoitre does all these things and there are plenty more enhancements planned.

You can get more information and download a demo at the link below:

http://sandersonforensics.com/forum/content.php?168-Reconnoitre

and there are some short support videos highlighting some of these features at this link:

http://sandersonforensics.com/forum/content.php?174-Reconnoitre-support-videos

This is what some of our users are saying about Reconnoitre:

• It looks as if it is going to solve that huge problem no one else seemed to want to tackle except in small segmented ways
• the UI looks like it was designed by someone who doesn’t hate his customers
• it’s flipping amazing
• paid for itself on the first job
• this is exactly the tool that we have been looking for that has been missing for our investigations

Reconnoitre – VSC processing made easy.

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...