Call for papers: International Conference on Digital Forensics and Cyber Crime

The International Conference on Digital Forensics and Cyber Crime is now accepting papers. Authors are invited to submit original and unpublished papers, accepted papers will appear in the conference proceedings and some papers may be selected for a journal…Suggested topics for submission of papers are (but not limited to):

* Computer Forensics
* Electronic Money Laundering
* Forensic Accounting
* Watermarking & Intellectual Property Theft
* Incident Response & Evidence Handling
* Network Data Analysis
* Data Analytics, Mining & Visualization
* Identity Theft & Online Fraud
* Mobile Device Forensics
* Digital Forensics and the Law
* Data Log Analysis
* Forensics Training & Education
* Natural Language Processing
* Cyber Crime Investigations
* Continuous Assurance
* Internet Crimes Against Children
* Data Recovery & Business Continuity
* Standardization & Accreditation
* Multimedia Forensics
* Digital Signatures and Certificate

Submissions can be made in a number of categories: Completed research papers, research-in-progress papers, case studies, and panel proposals/round table discussions. Please follow the following guidelines in preparing your submission.

1. Completed Research Papers: Typically 5,000 words long (excluding abstract and references).
2. Research in Progress Papers: Typically 2,500 words (excluding abstract and references).
3. Case Studies: Typically between 3,000 and 5,000 words long.
4. Round Table Discussion: Typically a 1,000 word synopsis of the topic area.
5. Panel Proposals: Typically a 1,000 word description, identifying the panel presenters to be involved.
6. Workshop Proposals: Typically a 1,000 word description of topics, potential speakers, program length, and potential audience. Also, include proposer resume(s).

Get The Latest DFIR News!

Top DFIR articles in your inbox every month.


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

Important dates

Paper Submission Deadline: April 30, 2009.
Reviewer Feedback: May 31, 2009.
Final Paper Submission: June 30, 2009.
Conference Dates: Sep 30 – Oct 2, 2009.

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