Links
Carbon Black
I recently gave a presentation at ETCSS, during which we discussed the need for incident preparedness in order to improve the effect of incident response efforts. In that presentation, I mentioned and described Carbon Black (Cb), as well as how it can be used in other ways besides IR.
While I was traveling to the venue, Cb Enterprise was released. Folks, if you don't know what Carbon Black is, you really should take a look at it. If you use computers in any capacity beyond simply sitting at a keyboard at your house...if you're a dentist's office, hospital, law firm, or a national/global business...you need to take a good hard look at Cb. Cb is a small, light-weight sensor that monitors execution on a system...remember Jesse Kornblum's Rootkit Paradox paper? The paradox of rootkits is that they want to hide, but they must run...the same is true with any malware. Cb monitors program execution on Windows systems. The guys at Cb have some great examples of how they've tracked down a three-stage browser drive-by infection in minutes, where it may have taken an examiner doing just disk forensics days to locate the issue.
If you have and use computers, or you have customers who do, you should really take a hard look at Cb and consider deploying it. Seriously...check out the site, give the Kyrus Tech guys a call, and take a good hard look at what Cb can do for you. I honestly believe that Cb is a game changer, and the Kyrus Tech guys have demonstrated that it is, indeed, a game changer, but not just for IR work.
Timeliner
Jamie Levy has posted documentation and plugins for her OMFW talk (from last July) regarding extracting timeline data from a memory dump using the Volatility framework. This is a great set of plugins for a great memory analysis framework, folks. What's really cool is that with a little bit of programming effort, you can modify the output format of the plugins to meet your needs, as well. A greatbighuge THANKS to Jamie for providing these plugins, and for the entire Volatility team/community for a great memory analysis framework.
Exploit Artifacts
Speaking of timelines...Corey has posted yet another analysis of exploit artifacts, this one regarding a signed Java applet. This is a great project that Corey works on, and a fantastic service that he's providing. Using available tools (i.e., MetaSploit), he compromises a system, and then uses available tools and techniques (i.e., timeline analysis) to demonstrate what the artifacts of the exploit "look like" from the perspective if disk analysis. Corey's write-up is clear and concise, and to be honest, this is what your case notes and reports should look like...not exactly, of course, but there are lot of folks that use the "...I don't know what standard to write to..." as an excuse to not do anything. Look at what Corey's done here...don't you think that there's enough information to replicate what he did? Does that work as a standard?
Also, take a look at the technique Corey used for investigating this issue...rather than posting a question online, he took steps to investigate the issue himself. Rather than starting with an acquired image and a question (as is often the case during an exam), he started with just a question, and set out to determine an answer. Information like this can be extremely valuable, particular when it comes to determining things such as the initial infection vector of malware or a bad guy, and a good deal of what he's provided can be added to an exam checklist or a plugin for a forensic scanner. I know that I'm going to continue to look for these artifacts...a greatbighuge THANKS to Corey, not just for doing this sort of work, but posting his results, as well.
DFF
DFF 1.2 is available for download. Take a look at this for a list of the updates; check out batch mode. Sorry, I don't have more to write...I just haven't had a chance to dig into it yet.
Community
One of the things I see a great deal of, whether it's browsing the lists or reading questions that appear in my inbox, is that when asking questions regarding forensic analysis, many of us still aren't providing any indication of the operating system that we're analyzing. Whether its an application question (P2P, FrostWire, a question about MFT entries, etc.), many of us are still asking the questions without identifying the OS, and if it's Windows, the version.
Is this important at all? I would suggest that yes, it is. The other presentation I gave at ETCSS (see the Carbon Black entry above) was titled What's new in Windows 7: An analyst's perspective. During this presentation, we discussed a number of differences, specifically between Windows XP and Win7, but also between Vista and Win7. Believe it or not, the version of Windows does matter...for example, Windows 2003 and 2008 do not, by default, perform application prefetching (although they can be configured to do so). With Windows XP, the searches a user executed from the desktop were recorded in the ACMru key; with Vista, the searches were NOT recorded in a Registry key (they were/are maintained in a file); with Windows 7, the search terms are maintained in the WordWheelQuery key.
Still not convinced? Try analyzing a Windows 7 memory dump with Volatility, but don't use the Windows 7 profile.
So, it you're asking a question that has to do with file access times, then the version of Windows is very important...because as of Vista, by default, updating of last access times on files is disabled. This functionality can be controlled by a Registry value, which means that this functionality can also be disabled on Windows XP systems.
I also see a number of questions referring to various applications, many of which are specific to P2P applications. Different applications behave differently...so saying, "I'm doing a P2P investigation" doesn't really provide much information if you're looking for assistance. I mean, who's going to write an encyclopedic if/then loop with all of the possibilities? Not only is the particular application important, but so is the version...for the same reasons that the OS version is important. I've dealt with older versions of applications, and what those applications do, or are capable of doing, can be very important to an investigation...that is, unless you're planning to fill in the gaps in your investigation with speculation.
In short, if you've got a question about something, be sure to provide relevant background information regarding what you're looking at...it can go a long way toward helping someone answer that question and provide you with assistance.
Tools
I've started a new page for my blog, listing the FOSS forensic tools that I find, come across, get pointed to, and use. It's a start...I have a good deal of catching up to do. I've started listing the tools, and provided some descriptions...I'll be updating the tools and descriptions as time goes on. This is mostly a place for me to post tools and frameworks so that I don't have to keep going back and searching through my blog for something, but feel free to stop by and take a look, or email me a tool that you like to use, or site with several tools.
Endorsements
One final thing...and this is for Mr. Anonymous, who likes to leave comments to some of my blog posts...I get no benefit, monetarily or otherwise, for my comments or endorsement of Volatility, nor for DFF...or any other tool (FOSS or otherwise) for that matter. I know that in the past, you've stated that you "...want to make sure that it is done with the right intentions". Although you've never explicitly stated what those intentions are, I just wanted to be up front and clear...I have used these tools, and I see others discovering great benefit from them, as well...as such, I think that it's a great idea to endorse them as widely as possible, so that others don't just see the web site, but also see how they can benefit from using these tools. I hope that helps.
While I was traveling to the venue, Cb Enterprise was released. Folks, if you don't know what Carbon Black is, you really should take a look at it. If you use computers in any capacity beyond simply sitting at a keyboard at your house...if you're a dentist's office, hospital, law firm, or a national/global business...you need to take a good hard look at Cb. Cb is a small, light-weight sensor that monitors execution on a system...remember Jesse Kornblum's Rootkit Paradox paper? The paradox of rootkits is that they want to hide, but they must run...the same is true with any malware. Cb monitors program execution on Windows systems. The guys at Cb have some great examples of how they've tracked down a three-stage browser drive-by infection in minutes, where it may have taken an examiner doing just disk forensics days to locate the issue.
If you have and use computers, or you have customers who do, you should really take a hard look at Cb and consider deploying it. Seriously...check out the site, give the Kyrus Tech guys a call, and take a good hard look at what Cb can do for you. I honestly believe that Cb is a game changer, and the Kyrus Tech guys have demonstrated that it is, indeed, a game changer, but not just for IR work.
Timeliner
Jamie Levy has posted documentation and plugins for her OMFW talk (from last July) regarding extracting timeline data from a memory dump using the Volatility framework. This is a great set of plugins for a great memory analysis framework, folks. What's really cool is that with a little bit of programming effort, you can modify the output format of the plugins to meet your needs, as well. A greatbighuge THANKS to Jamie for providing these plugins, and for the entire Volatility team/community for a great memory analysis framework.
Exploit Artifacts
Speaking of timelines...Corey has posted yet another analysis of exploit artifacts, this one regarding a signed Java applet. This is a great project that Corey works on, and a fantastic service that he's providing. Using available tools (i.e., MetaSploit), he compromises a system, and then uses available tools and techniques (i.e., timeline analysis) to demonstrate what the artifacts of the exploit "look like" from the perspective if disk analysis. Corey's write-up is clear and concise, and to be honest, this is what your case notes and reports should look like...not exactly, of course, but there are lot of folks that use the "...I don't know what standard to write to..." as an excuse to not do anything. Look at what Corey's done here...don't you think that there's enough information to replicate what he did? Does that work as a standard?
Also, take a look at the technique Corey used for investigating this issue...rather than posting a question online, he took steps to investigate the issue himself. Rather than starting with an acquired image and a question (as is often the case during an exam), he started with just a question, and set out to determine an answer. Information like this can be extremely valuable, particular when it comes to determining things such as the initial infection vector of malware or a bad guy, and a good deal of what he's provided can be added to an exam checklist or a plugin for a forensic scanner. I know that I'm going to continue to look for these artifacts...a greatbighuge THANKS to Corey, not just for doing this sort of work, but posting his results, as well.
DFF
DFF 1.2 is available for download. Take a look at this for a list of the updates; check out batch mode. Sorry, I don't have more to write...I just haven't had a chance to dig into it yet.
Community
One of the things I see a great deal of, whether it's browsing the lists or reading questions that appear in my inbox, is that when asking questions regarding forensic analysis, many of us still aren't providing any indication of the operating system that we're analyzing. Whether its an application question (P2P, FrostWire, a question about MFT entries, etc.), many of us are still asking the questions without identifying the OS, and if it's Windows, the version.
Is this important at all? I would suggest that yes, it is. The other presentation I gave at ETCSS (see the Carbon Black entry above) was titled What's new in Windows 7: An analyst's perspective. During this presentation, we discussed a number of differences, specifically between Windows XP and Win7, but also between Vista and Win7. Believe it or not, the version of Windows does matter...for example, Windows 2003 and 2008 do not, by default, perform application prefetching (although they can be configured to do so). With Windows XP, the searches a user executed from the desktop were recorded in the ACMru key; with Vista, the searches were NOT recorded in a Registry key (they were/are maintained in a file); with Windows 7, the search terms are maintained in the WordWheelQuery key.
Still not convinced? Try analyzing a Windows 7 memory dump with Volatility, but don't use the Windows 7 profile.
So, it you're asking a question that has to do with file access times, then the version of Windows is very important...because as of Vista, by default, updating of last access times on files is disabled. This functionality can be controlled by a Registry value, which means that this functionality can also be disabled on Windows XP systems.
I also see a number of questions referring to various applications, many of which are specific to P2P applications. Different applications behave differently...so saying, "I'm doing a P2P investigation" doesn't really provide much information if you're looking for assistance. I mean, who's going to write an encyclopedic if/then loop with all of the possibilities? Not only is the particular application important, but so is the version...for the same reasons that the OS version is important. I've dealt with older versions of applications, and what those applications do, or are capable of doing, can be very important to an investigation...that is, unless you're planning to fill in the gaps in your investigation with speculation.
In short, if you've got a question about something, be sure to provide relevant background information regarding what you're looking at...it can go a long way toward helping someone answer that question and provide you with assistance.
Tools
I've started a new page for my blog, listing the FOSS forensic tools that I find, come across, get pointed to, and use. It's a start...I have a good deal of catching up to do. I've started listing the tools, and provided some descriptions...I'll be updating the tools and descriptions as time goes on. This is mostly a place for me to post tools and frameworks so that I don't have to keep going back and searching through my blog for something, but feel free to stop by and take a look, or email me a tool that you like to use, or site with several tools.
Endorsements
One final thing...and this is for Mr. Anonymous, who likes to leave comments to some of my blog posts...I get no benefit, monetarily or otherwise, for my comments or endorsement of Volatility, nor for DFF...or any other tool (FOSS or otherwise) for that matter. I know that in the past, you've stated that you "...want to make sure that it is done with the right intentions". Although you've never explicitly stated what those intentions are, I just wanted to be up front and clear...I have used these tools, and I see others discovering great benefit from them, as well...as such, I think that it's a great idea to endorse them as widely as possible, so that others don't just see the web site, but also see how they can benefit from using these tools. I hope that helps.