Belkasoft Evidence Center 9.5 Aims To Help In Corporate Investigations

Belkasoft releases a major update to Belkasoft Evidence Center, the company’s flagship digital forensic solution. The new release adds a number of features to help IT security staff analyze incidents and perform remote investigations, investigate hacking attempts and analyze evidence across case boundaries. With this update, Belkasoft Evidence Center aims to help companies investigate incidents occurred on their corporate network or corporate mobile devices.

More details: https://belkasoft.com/bec95-press-releaseRemote Acquisition of Corporate Computers and Smartphones

Belkasoft Evidence Center 9.5 adds a major new feature to enable IT security personnel investigate incidents without leaving premises. Remote acquisition helps investigators obtain full device images of corporate servers or workstations running in a distributed environment. By using centralized deployment, IT security staff may install an acquisition agent to any computer running on the corporate network. This agent will then obtain full images of the computer’s volatile memory, hard drives and connected smartphones without preventing normal operation and without the need to remove the hard drive(s). Whether the organization has one or multiple locations, this new feature allows non-invasive incident investigations in distributed environments.

Analyzing Hacking Attempts with Incident Investigation

Get The Latest DFIR News!

Top DFIR articles in your inbox every month.


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

Incident Investigation is another new feature that further expands how Belkasoft Evidence Center is used in corporate environments. Incident Investigation helps companies investigate hacking attempts of Windows-based computers by performing an automated analysis of numerous sources. The tool analyzes the Windows registry, event logs and memory dumps to discover traces of successful and unsuccessful remote attacks that are commonly used to break in to the company’s infrastructure.

Read the entire press-release at https://belkasoft.com/bec95-press-release

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