Plaso 20180127 released

By Anonymous
Plaso 20180127 released
The Plaso team is pleased to announce its first 2018 release, Plaso 20180127. A few highlights from this release:
  • We’ve updated the Chrome History SQLite plugin to be more strict about which version of the Chrome history file it’s parsing, and produce fewer spurious error messages.
  • Initial support for parsing System Resource Usage Monitor (SRUM) databases (SRUDB.dat) has been added, based on previous work.
  • There’s a new parser for processing MacOs FSEventsd files, from Leopard to High Sierra, inspired by Nicole Ibrahim’s OSDFCon 2017 presentation.
  • A basic sessionize analysis plugin has been added, which we’ll extend in the future to support functionality like Timesketch’s event similarity scoring. This work was catalysed by work like David Gresty’s (et. al) from DFRWS EU 2016.
  • As indicated previously, the ZIP storage implementation has been removed.


As usual, there’s a bunch of cleanups and bug fixes, the full list of which are available in the release milestone. One minor issue made it in to the release, event counts by parser will be incorrect in this release, and we’ll fix it up for the February version.


Where/how to get Plaso 20180127?


See Plaso's Users' Guide. As usual, builds are available for MacOS, Ubuntu, Fedora Core and Windows.

If you run into problems take a look at the Installation Problems page on the Plaso wiki, to see if other people have seen the issue before. If nothing there helps, ask for help on the discuss mailing list: log2timeline-discuss@googlegroups.com  or open an issue on the tracker.

Comments

Post a Comment

Popular posts from this blog

Parsing the $MFT NTFS metadata file

By
Background Numerous articles have been written about parsing the $MFT NTFS metadata file before. Some of these explain the technique itself [ 1 ] and others mostly focus on how to use tools. Rarely do articles mention the pros and cons of the technique from a digital forensics perspective [ 2 ].  What is $MFT parsing?  For readers not familiar with the NTFS file system, MFT stands for Master File Table. This table is stored in a file system metadata file, meaning that as far as the file system is concerned it is a file, however that the file contains file system metadata not “regular” content. The name of this file is “$MFT”.  The MFT consists of a sequence of (predetermined) fixed-size entries (or MFT entries). These entries are typically 1024 bytes in size, however the size is defined in the NTFS volume header and in a “regular” MFT entry itself.  The first 4-bytes of a “regular” MFT-entry (or record) starts with the signature “FILE”. The MFT entry can...
Read more

Incident Response in the Cloud

By
Many organizations have begun moving a majority of their services towards the cloud in recent years. As a result, attackers have shifted their focus towards the cloud. This has resulted in new techniques and methods specifically designed to compromise cloud infrastructure, like the recent SALTSTACK vulnerability that was widely exploited [ 1 ]. Therefore it is critical for these organizations to have an incident response team that understands the new risks attached to cloud and how cloud can make incident response easier or harder.  In this blog post we will walk you through each phase you may encounter in traditional incident response and highlight the differences when adopting cloud computing. It is aimed towards both those who are new to incident response and cloud computing. We’ve included insights that will benefit organizations taking that step towards cloud who want to ensure they are prepared to respond efficiently to cloud incidents.  Traditional Incident Response Be...
Read more

Container Forensics with Docker Explorer

By Anonymous
  Introduction As previous blog posts on cloud forensics have noted, applications are increasingly being deployed using container orchestration frameworks such as Kubernetes, especially in cloud environments.  Similar to traditional deployments on physical servers or virtual machines (VMs), when a containerised application has a security issue it can lead to a compromise of the underlying compute architecture. In the case of container deployments this means a compromise of the container itself, the container host, or even a wider cluster compromise via abuse of orchestration tools. Often digital forensics is required to establish what went wrong and remediate any issues. This article will provide an introduction to container forensics with Docker Explorer by working through a scenario involving a compromised container running within a Kubernetes cluster. Although Kubernetes is briefly mentioned, this article will focus on analysis of an individual container rather than the wi...
Read more