Litigious investigation methodology

From: Harlan Carvey (keydet89_at_yahoo.com)
Date: 06/10/04

  • Next message: Harlan Carvey: "RE: Simple Windows incident response methodology"
    Date: Thu, 10 Jun 2004 04:45:40 -0700 (PDT)
    To: incidents@securityfocus.com
    
    

    All,

    I posted a cursory methodology for Windows systems
    last night, and based on some posts I saw this
    morning, wanted to pose a question or two...

    Mark's simple data collection methodology is a good
    one (albiet some of the references to "analysis"
    should read "collection"), and someone pointed out to
    him that it's not useful for litigious investigations
    (ie, investigations that lead to law enforcement
    involvement).

    After reviewing other sources, I have to ask...why?
    What is it specifically about his methodology that
    prevents it from being used in pursuit of a litigious
    investigation? Is it b/c some of the tools are run
    from the victim system rather than the CD? Is it b/c
    the output of the tools is written to a diskette, and
    those diskettes can be "infected" with malware, just
    b/c they are writable?

    What I'm getting at here is that rather than simply
    pointing out the flaws in something, let's try making
    suggestions for improvement.

    Take the methodology I developed for my book, the
    Forensic Server Project (code and instructions
    available at http://www.windows-ir.com), for example.
    Tools are run from a CD, and the output of the tools
    is transported off of the system via the network to a
    waiting server system. The server component handles
    documentation/logging, generation of hashes
    (verification of hashes if files are copies off of the
    system, etc.).

    Is such a methodology sufficient? If you've got
    questions about the FSP, feel free to ask. The goal
    here is to produce something that can be used.


  • Next message: Harlan Carvey: "RE: Simple Windows incident response methodology"

    Relevant Pages

    • Re: Domain Controller qestion
      ... valid methodology to apply to business networks? ... >methodology to apply to business networks. ... >Meanwhile, sounds like your remote server is already a DC, ignore that step. ...
      (microsoft.public.windows.server.sbs)
    • Re: How to transfer SBS 2003 to new server?
      ... Its a methodology - can do most of the stuff if you spend the time looking ... >> Agree - it dont mean a thing if it aint got that swing. ... >> the old server to the final server ... >>> Simon ...
      (microsoft.public.windows.server.sbs)
    • HELP! hangs at applying settings
      ... configuration and applications installed on server. ... But a methodology would ... We are able to boot to safe mode. ...
      (microsoft.public.windows.server.sbs)
    • Re: Replacing Server 2003 Std with SBS2003
      ... methodology may be the ticket. ... TS in application mode on the SBS server under any circumstances. ... Or is there a method of doing the install while retaining all ...
      (microsoft.public.windows.server.sbs)
    • Re: Domain Controller qestion
      ... Internet based backup is a viable solution for Joe Homer, ... methodology to apply to business networks. ... Meanwhile, sounds like your remote server is already a DC, ignore that step. ... > replication process replicates the AD from the primary server to ...
      (microsoft.public.windows.server.sbs)