Welcome Guest. | Log In| Register | Membership Benefits
Dark Reading's evil-bytes Weblog

Topics:   Evil Bytes
  • Email this page E-mail this page
  • |  Print Print this page
  • |   Bookmark and Share

The Future Of Digital Forensics

Last week's 10th annual IT Security Awareness Day at the University of Florida had IT workers from all over the state in attendance to hear experts from InGuardians, F-Response, Sunbelt Software, and Microsoft. Though I enjoyed every presentation, I keep thinking about one in particular -- the future of forensics, by F-Response's Matt Shannon.

Oct 09, 2009 | 01:46 AM | 

By John H. Sawyer
Dark Reading
Last week's 10th annual IT Security Awareness Day at the University of Florida had IT workers from all over the state in attendance to hear experts from InGuardians, F-Response, Sunbelt Software, and Microsoft. Though I enjoyed every presentation, I keep thinking about one in particular -- the future of forensics, by F-Response's Matt Shannon.Matt's presentation, "Finding The Needle: New Directions In Electronic Evidence Collection," was an insightful look at traditional forensics and the challenges forensic investigators are beginning to face. Problems include the ever-increasing size of hard drives, attackers and malware using methods to avoid touching the hard drive, and the need for faster decision-making during incident response.

I've discussed the Metasploit Framework's meterpreter payload, which is designed to be injected into an exploited process and never touch the hard drive, making it difficult to determine an attacker's actions. While that's definitely a valid concern for today's forensic investigators, it's the size of hard drives that are having a major impact on traditional forensics.

As we've discussed before, traditional forensics is pretty much the standard operating procedures for most organizations that perform hard drive acquisition and authentication prior to analysis. Essentially, it is the process of getting a computer, creating a forensic copy of the hard drive, confirming it is an exact duplicate, and then performing analysis on the copy.

The challenge of traditional forensics and larger hard drives is that the acquisition typically takes hours -- sometimes days -- depending on the size and number of drives. After authentication, forensic investigators then have to dig through the massive amount of data, which can take a significantly long time. If you've ever done full-text indexing of a large drive, then you know it's not a quick process.

Matt's take on where the forensic industry: Live forensics is going to become a necessity. The idea is that when facing such large amounts of information, a forensic investigator can collect volatile information, analyze areas of the drive to help answer questions faster, and determine whether the full hard drive needs to be acquired or if other systems need to be analyzed.

Live forensics actually works to the forensic investigators' and the businesses' advantage because investigators are stuck sitting around waiting for the acquisition process to finish before they can get started with analysis. Management is happy because the investigators can start providing answers faster (because they can get a better idea of how much this incident is going to cost them).

I don't think anyone currently performing forensics and incident response on a regular basis will be all that surprised with Matt's outlook. The signs pointing that way have been there, but the tools to actually perform live forensics easily and effectively have only begun to take off. A good example is Matt's tool, F-Response, which enables forensic investigators to perform live forensics using any standard forensic tool, like AccessData's Forensic Toolkit (FTK), X-Ways Forensics, and Guidance Software's Encase.

Now's the time to start preparing because tomorrow might be the day you get the call about a case involving a dozen computers in which each one contains one to four 1.5 terabyte hard drives and a server containing about 10 terabytes of data.

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS









  1. Cookies, Social Media And FireSheep
  2. SMB Guide To Credit Card Regulations, Part 2: The Low-Hanging Fruit
  3. HP And The Scary Corporate Fifth Column Concept
  4. Taking USB Attacks To The Next Level
  5. NoSQL: Not Much, Anyway
  1. Taking Cybersecurity Lessons To The Bank
  2. Researchers See Real-Time Phishing Jump
  3. 'BlackSheep' Sniffs Out Firesheep WiFi-Hacking
  4. Slideshow: Ten Free Security Monitoring Tools
  5. A Different Spin On Sleuthing Stuxnet
  6. M&A Activity Muddles Database Security
  1. Secure Managed Web Hosting Saves 960.gs from Malicious Hackers
  2. Access Governance as a Business Service: An Integrated Strategy for Automation with ITSM
  3. Business Driven Access Management and Governance: Simplifying the Delivery and Governance of Access Throughout
 
 


 
  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag
 
  February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
  May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008