Oxygen Forensic Detective 9.5 Now Supports 40 Clouds With Addition Of Telegram

Oxygen Forensics, a worldwide developer and provider of advanced forensic data examination tools for mobile devices and cloud services, announced today that it now supports data extraction from 40 different cloud services with the addition of Telegram cloud for its flagship Oxygen Forensic® Detective 9.5 product.Launched in 2013, Telegram messaging competes with WhatsApp, Messenger, and any other messaging app. Telegram runs on iOS, Android, and Windows Phone mobile devices, and users can access it from a web portal for use on desktops. Telegram runs on open source software and is free for users.

“Oxygen Forensics is very proud to add Telegram Cloud to our list of cloud services from which we can extract data and this capability with Telegram brings our cloud support to 40 regarding the number of services that we can now obtain data,” said Lee Reiber, COO, Oxygen Forensics. “Criminals and terrorists around the world try and use any method they can find to encrypt communication and attempt to keep their evil deeds secret. It will always be Oxygen Forensics’ goal to allow forensics professionals the ability to uncover evidence of their bad acts through real-time data extraction and bring the bad guys to justice.”

About Oxygen Forensics, Inc.

Oxygen Forensics was founded in 2000 as a PC-to-Mobile Communication software company. This experience has allowed the team of mobile device experts to become unmatched in understanding mobile device communication protocols. With this knowledge, the company has built innovative techniques into Oxygen Forensic® Detective allowing examiners to access much more critical information than competing forensic analysis tools. Oxygen Forensics delivers the most advanced forensic data examination tools for mobile devices and cloud services covering the widest range of mobile devices running iOS, Android, Windows Phone, BlackBerry and many others.

For more information about Oxygen Forensics, please visit www.oxygen-forensic.com.

Get The Latest DFIR News!

Top DFIR articles in your inbox every month.


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

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