Timeline Analysis Process
Having discussed timeline analysis in a couple of blog posts so far (such as here...), I thought Id take an opportunity to dig a bit deeper into the process Ive been using for some time to actually conduct analysis of timelines that I create during engagements.
Before we get into the guts of the post, Id like to start by saying that this is what Ive found that works for me, and it does not mean that this is all there is. This is what Ive done, and been doing, tweaking the process a bit here and there over the years. Ive looked at things like visualization to try to assist in the analysis of time lines, but I have yet to find something that works for me. Ive seen how others "do" timeline analysis, and for whatever reason, I keep coming back to this process. However, that does not mean that Im not open to other thoughts, or discussion of other processes. Its quite the opposite, in fact...Im always open to discussing ways to improve any analysis process.
Usually when I create a timeline, its because I have something specific that Im looking for that can be shown through a timeline; in short, I wont create a timeline (even a micro-timeline) without a reason to do so. It may be a bit of malware, a specific Registry entry or Windows Event Log record, a time frame, etc. As is very often the case, Ill have an indicator, such as web shell file on a system, and find that in some cases, the time frames dont line up between systems, even though the artifact is the same across those systems. Its this information than I can then use, in part, to go beyond the "information" of a particular case, and develop intelligence regarding an adversarys hours of operations, action on objectives, etc.
When creating a timeline, Ill use different tools, depending upon what data I have access to. As I mentioned before, there are times when all Ill have is a Registry hive file, or a couple of Windows Event Logs, usually provided by another analyst, but even with limited data sources, I can still often find data of interest, or of value, to a case. When adding Registry data to a timeline, Ill start with
regtime to add key Last Write times from a hive to the timeline. This tool doesnt let me see Registry values, only key Last Write times, but its value is that it lets me see keys that have been created or modified during a specific time frame, telling me where I need to take a closer look. For example, when Im looking at a timeline and I see where malware was installed as a Windows service, Ill usually see the creation of the Registry key for the service beneath the Services key (most often beneath both, or all, ControlSets).
When I want to add time stamped information from Registry value data to a timeline, Ill turn to RegRipper and use the plugins that end in
*_tln.pl. These plugins (generally speaking) will parse the data from Registry values for the time stamped information, and place it into the necessary format to include it in a timeline. The key aspect to doing this is that the analyst must be aware of the context of the data that theyre adding. For example, many analysts seem to believe that the time stamp found in the AppCompatCache (or ShimCache) data is when the program was executed, and in several cases (one announced publicly by the analyst), this misconception has been passed along to the customer.
I also use several tools that let me add just a few events...or even just one event...to the time line. For example, the RegRipper
secrets_tln.pl plugin lets me add the Last Write time of the
Policy/Secrets key from the Security hive to the timeline. I can check the time stamp first with the secrets.pl plugin to see if its relevant to the time frame Im investigating, and if it is, add it to the timeline. After all, why add something to the timeline thats not relevant to what Im investigating?
If I want to add an event or two to the timeline, and I dont have a specific parser for the data source, I can use
tln.exe (image to the left) to let me add that event. Ive found this GUI tool to be very useful, in that I can use it to quickly add just a few events to a timeline, particularly when looking at the data source and only finding one or two entries that are truly relevant to my analysis. I can fire up
tln.exe, add the time stamp information to the date and time fields, add a description with a suitable tag, and add it to the timeline. For example, Ive used this to add an event to a timeline, indicating when the available web logs on a system indicated the first time that a web shell that had been added to the system was accessed. I added the source IP address of the access in the description field in order to provide
context to my timeline, and at the same time, adding the event itself provided an additional (and significant)
level of relative confidence in the data I was looking at, because the event I added corresponded exactly to file system artifacts that indicated that the web shell had been accessed for the first time. I chose this route, because adding
all of the web log data wouldve added significant volume to my timeline without adding any additional context or even utility.
When creating a timeline, I start with the events file (usually, events.txt), and use
parse.exe to create a full timeline, or a partial timeline based on a specific date range. So, after running
parse.exe, I have the events.txt file that contains all of the events that Ive extracted from different data sources using different tools (whichever applies at the time), and I have either full timeline (tln.txt) or a shortened version based on a specific date range...or both. To begin analysis, Ill usually open the timeline file in Notepad++, which I prefer to use because it allows me to search for various things, going up or down in the file, or it can give me a total count of how many times a specific search term appears in the file.
Once I begin my analysis, Ill open another tab in Notepad++, and call it "notes.txt". This is where all of my analysis notes go while Im doing timeline analysis. As I start finding indicators within the timeline, Ill copy-and-paste them out of the timeline file (tln.txt) and into the notes file, keeping everything in the proper sequence.
Timeline analysis has been described as being an iterative process, often performed in "layers". The first time going through the timeline, Ill usually find a bunch of stuff that requires my attention. Some stuff will clearly be what Im looking for, other stuff will be, "...hey, what is this..."...but most of whats in the timeline will have little to do with the goals of my exam. Im usually not interested in things like software and application updates, etc., so having the notes file available lets me see what I need to see. Also, I can easily revisit something in the timeline by copying the date from the notes file, and doing a search in the timeline...this will take me right to that date in the timeline.
Recently while doing some timeline analysis, I pulled a series of indicators out of the timeline, and pasted them into the notes file. Once Id followed that thread, I determined that what I was seeing as adware being installed. The user actively used the browser, and the events were far enough back in time that I wasnt able to correlate the adware installation with the site(s) that the user had visited, but I was able to complete that line of analysis, note what Id found, remove the entries from the notes file, and move on.
As timeline analysis continues, I very often keep the data source(s) open and available, along with the timeline, as I may want to see something specific, such as the contents of a file, or the values beneath a Registry key. Lets say that the timeline shows that during a specific time frame that Im interested in, the Last Write time of the
HKLM/../Run key was modified; I can take a look at the contents, and add any notes I may have ("...there is only a single value named blah...") to the notes file.
Many times, I will have to do research online regarding some of the entries in the timeline. Most often, this will have to do with Windows Event Log entries; I need to develop an understanding of what the source/ID pair refers to, so that I can fill in the strings extracted from the record and develop context around the event itself. Sometimes I will find
Microsoft-Windows-Security-Auditing/5156 events that contain specific process names or IP addresses of interest. Many times, Windows Event Log record source/ID pairs that are of interest will get added to my
eventmap.txt file with an appropriate tag, so that I have additional indicators that automatically get identified on future cases.
Not everything extracted from the timeline is going to be applicable to the goals of my analysis. Ive pulled data from a timeline and my research has determined that the events in question were adware being installed. At that point, I can remove the data from my notes file.
By the time Ive completed my timeline analysis, I have the events file (all of the original events), the timeline file, and the notes file. The notes file is where Ill have the real guts of my analysis, and from where Ill pull things such as
indicator clusters (several events that, when they appear together, provide
context and a
greater level of confidence in the data...) that Ive validated from previous engagements, and will use in future engagements, as well as intel I can use in conjunction with other analysis (other systems, etc.) to develop a detailed picture of activity within the enterprise.
Again, this is just the process I use and have found effective...this is not to say that this is what will work for everyone. And I have tried other processes. Ive had analysts send me automatically-created colorized spreadsheets and to be honest, Ive never been very clear as to what theyve found or thought to be the issue. That is not to say that this method of analysis isnt effective for some, as Im sure it is...I simply dont find it effective. The process I described has been effective for me at a number of levels...from having a single data source from a system (i.e., a single Registry hive...), to having an entire image, to analyzing a number of systems from the same infrastructure. And again, Im not completely stuck to this process...Im very open to discussion of other processes, and if I do find something that proves to be effective, I have no problem adding it to what I do, or even changing my process all together.
visit link download 
