SAFE Corporation announces CodeSuite-LT

Software Analysis & Forensic Engineering Corporation (www.SAFE-corp.biz) has announced the release of CodeSuite-LT(R), a “lite” version of CodeSuite offering all of the key functionality for unlimited use over the term of the license.”These days companies are understandably much more cost sensitive than they were in previous years,” said Bob Zeidman, president of SAFE Corporation. “In particular, small companies with smaller budgets are finding themselves to be plaintiffs or defendants in copyright infringement cases. These cases are critical to keeping them in business. When a company’s employees steal code to start new businesses, for example, the company loses a key advantage in its market. When a small company is unfairly accused of code theft, that can drain valuable resources or put it out of business altogether. We’ve been getting a lot of requests for a less expensive version of CodeSuite but with the same high standard of reliability and usability. That’s why we created CodeSuite-LT.” CodeSuite-LT includes the tools BitMatch(R), CodeCross(R), CodeDiff(R), and CodeMatch(R) that can be used in conjunction with SourceDetective(R).

CodeSuite-LT generates detailed reports on its findings and includes the free tools FileCount(TM) and FileIsolate(TM). It is available now at $2,000 for a 6-month unlimited license and $3,800 for a one-year unlimited license.

About SAFE Corporation SAFE Corporation is the leading provider of software forensic analysis tools for discovering software IP theft and measuring software IP changes. Its flagship product CodeSuite has been used in numerous trials involving copyright infringement and trade secret theft. For more information, email [email protected] or call (408) 517-1167.

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