Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Plaso is the forensic engine that extracts timestamps from hundreds of artefact types, and log2timeline is the tool that drives it to build a single super timeline of a system.

What Are Plaso and log2timeline?
Ask a forensic examiner what happened on a compromised laptop and the honest answer is that the evidence is scattered. Event logs hold one part, the registry another, prefetch files a third, browser databases a fourth, and the file system itself records four timestamps per entry. Plaso is the engine that reads all of them and normalises every timestamp into one sorted stream; log2timeline is the tool that drives it.
The original log2timeline was a Perl project released in 2009. Plaso is the Python rewrite that replaced it, and the name of the modern command line tool, log2timeline.py, preserves the lineage. The output is what practitioners call a super timeline: every dated event from every supported source, in order.
| Tool | Job |
|---|---|
log2timeline.py | Extracts events from an image, directory, or file into a .plaso storage file |
psort.py | Sorts, filters, deduplicates, tags, and exports the storage file |
pinfo.py | Reports what was processed, which parsers ran, and what errors occurred |
psteal.py | Runs extraction and output in one step for quick triage |
Splitting extraction from output is deliberate. Parsing a 500 GB image is expensive and happens once; after that, analysts run psort.py repeatedly with different date ranges, filters, and formats without touching the evidence again.
Plaso ships with well over a hundred parsers. The ones that carry most investigations are Windows event logs, registry hives including shellbags and UserAssist, prefetch files, the $MFT and $UsnJrnl, link files and jump lists, scheduled tasks, browser history and cache, antivirus and application logs, Linux syslog and systemd journals, and macOS property lists and unified logs. It reads raw images, E01 and other forensic container formats, VMDK and VHD disks, and mounted directories, so acquisition format rarely dictates the workflow.
Because file system metadata contributes four timestamps for every record, output volume climbs fast. A single workstation image routinely yields several million events, which is why filtering is not optional.
Analysts narrow the problem in three ways. First, time: if the suspected intrusion window is 10 to 14 March, a date filter cuts the dataset by orders of magnitude. Second, source: restricting the parser set to event logs, registry, and prefetch during initial triage is far quicker than a full run. Third, tagging: Plaso applies tag files that label events as logins, file executions, document opens, or application installs, so an analyst can pull out only the categories that matter.
Output formats cover the usual destinations. The dynamic CSV format opens in a spreadsheet or Timeline Explorer, JSON feeds a SIEM, and direct export into Timesketch gives a collaborative, searchable timeline that several investigators can annotate at once.
Timestamps lie more often than beginners expect. Record whether output is in UTC or local time and keep one standard across the case. Watch for systems whose clock was wrong or was changed, which the registry will usually show. Remember that file system timestamps can be altered deliberately, a technique known as timestomping and covered under anti-forensic techniques: when $STANDARD_INFORMATION and $FILE_NAME timestamps disagree, that disagreement is itself a finding.
Interpretation also requires knowing what an artefact means. A prefetch entry proves a program ran; it does not prove who ran it. A registry key proves configuration existed at the time of acquisition. Corroborating two independent sources for the same event is what turns a timeline into evidence that survives scrutiny, alongside a documented chain of custody.
Super timelines answer questions that log review alone cannot: when did the first malicious file appear, what ran immediately before it, which account was active, what was opened afterwards, and when did the attacker come back. In ransomware cases they establish dwell time, which matters for UK GDPR breach assessment and for the report you give the Information Commissioner’s Office.
Plaso is slow on large images and needs real memory, so most teams run it on dedicated analysis hardware and pair it with faster triage collection from a tool such as Velociraptor. Our Digital Forensics and Incident Response Services build timelines of exactly this kind when establishing what an attacker did and for how long.
A super timeline merges every dated event from every available source into one chronological list: file system metadata, event logs, registry keys, browser history, application logs, and more. Instead of pivoting between separate tools, the analyst reads a single sequence and can see that a download, an execution, and a service creation happened within the same two minutes.
Hours rather than minutes for a full workstation image, and considerably longer for servers or multi-terabyte volumes. Processing is CPU and memory bound, so analysis machines with many cores and plenty of RAM help. Targeted runs that restrict parsers to event logs, registry, and prefetch finish far faster and are the normal choice for early triage.
No. Plaso works on file system and log artefacts, not on physical memory captures. Memory analysis uses a dedicated framework such as Volatility, which extracts processes, network connections, and injected code from a RAM image. Investigations usually run both and correlate the results, since memory shows what was running and the timeline shows how it got there.
Yes. Plaso is open source under the Apache 2.0 licence and is included in forensic distributions such as SIFT Workstation, as well as being installable from packages and containers. There is no licence cost, which makes it a standard part of most incident response toolkits alongside commercial suites rather than a replacement for them.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.