Plaso 20171231 released

By Anonymous
Plaso 20171231 released
Squeaking out just before the end of the year, the Plaso team is delighted to release Plaso 20171231. This will be the last release for 2017 😉. A few highlights from this release:
  • We introduced the SQLite Plaso storage file support a back in Heimdall. In 20171231 it’s now the default, and the older ZIP format is deprecated.
    • The biggest changes you’ll notice are that storage files are a bit larger, and extraction speed faster. 
    • If you need to use the old ZIP storage, run log2timeline.py with the ‘--storage-format=zip’ option.
    • We’re planning to remove the ZIP storage completely in the next release in January, which will unblock a few other changes, allowing us to shrink the SQLite storage file size.
  • A new SQLite parser plugin to handle Safari’s newer history format thanks to new contributor @chimau.
  • Updates to dfvfs to support libstk 4.5.0 and multi-member gzip files, needed for upcoming fsevents support.
  • Nicer looking partition and VSS overviews in log2timeline.

As usual, there’s a bunch of cleanups and bug fixes, the full list of which are available in the release milestone.

Where/how to get Plaso 20171231?

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

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

One other note - Richard Davis from the Youtube channel 13Cubed recorded a short introduction to Plaso. While it was produced with Heimdall in mind, it's still largely applicable to this most recent release. If you're looking for a quickstart guide, it's worth a watch.

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