viaForensics presents Android Forensics Training May 4 or 5, 2010 in Chicago

viaForensics, a computer and mobile forensic and e-discovery firm, is offering a one-day training course on Android forensics. Two sessions of the course are being offered on May 4 and May 5 from 8:00 a.m. to 4:00 p.m. at Chicago Police Training Academy, 1300 W. Jackson Blvd., in Chicago. The course is open to law enforcement and non-enforcement personnel…The training session is one of several training opportunities offered by Mobile Forensics World 2010 (MFW10) as part of their pre-conference activities. The conference will be held the following weekend, May 5-8, at the O’Hare Marriott. MFW10 brings together experts in various aspects of mobile device forensics to share their information, products and services.

viaForensics’ comprehensive training course provides examiners with an overview of Android, the software development kit (SDK) and the Android file system. Six specific forensic techniques and analysis tools needed to effectively investigate Android phones are explained. The full course outline is provided on the viaForensics website.

Attendees can register through the viaForensics website, www.viaForensics.com, by calling viaForensics at 312-283-0551 or through the MFW10 website, www.mobileforensicsworld.org. The cost is $1,325 for law enforcement personnel and $1,850 for non-enforcement.

viaForensics has been a leader in iPhone forensics technology and has shifted focus to Android forensics, investing significant resource and development efforts into this growing platform. CIO Andrew Hoog has authored a groundbreaking white paper on iPhone forensics and is currently authoring a book on Android forensics. Hoog also manages the Android Forensics Wiki (AFWiki).

Get The Latest DFIR News!

Top DFIR articles in your inbox every month.


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

About viaForensics
viaForensics is an innovative computer/mobile forensic and e-discovery firm focusing on providing proactive services to corporations, law enforcement and law firms. Andrew Hoog is a computer scientist, computer/forensics researcher and Chief Investigative Officer at viaForensics.

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