Difference between revisions of "Network forensics"

From ForensicsWiki
Jump to: navigation, search
m
m (Deep-Analysis Systems)
Line 10: Line 10:
 
== Commercial Network Forensics ==
 
== Commercial Network Forensics ==
 
===Deep-Analysis Systems===
 
===Deep-Analysis Systems===
* Sandstorm's [http://www.sandstorm.net/products/netintercept/ NetIntercept]
+
* Code Green Networks [http://www.codegreennetworks.com Content Inspection Appliance] - Passive monitoring and mandatory proxy mode. Simple to us Web GUI. Linux platform. Uses Stellent Outside In to access document content and metadata.
* NIKSUN's [[NetDetector]]
+
 
* ManTech International Corporation [http://www.netwitness.com/ NetWitness]
 
* ManTech International Corporation [http://www.netwitness.com/ NetWitness]
 +
* NIKSUN's [[NetDetector]]
 +
* Sandstorm's [http://www.sandstorm.net/products/netintercept/ NetIntercept] - Passive monitoring appliance. Qt/X11 GUI. FreeBSD platform. Uses forensic parsers written by Sandstorm to access document content and metadata.
 +
 
===Flow-Based Systems===
 
===Flow-Based Systems===
 
* Arbor Networks
 
* Arbor Networks

Revision as of 11:18, 12 February 2007

Network forensics is the process of capturing information that moves over a network and trying to make sense of it in some kind of forensics capacity. A network forensics appliance is a device that automates this process.

There are both open source and proprietary network forensics systems available.

Open Source Network Forensics

Commercial Network Forensics

Deep-Analysis Systems

  • Code Green Networks Content Inspection Appliance - Passive monitoring and mandatory proxy mode. Simple to us Web GUI. Linux platform. Uses Stellent Outside In to access document content and metadata.
  • ManTech International Corporation NetWitness
  • NIKSUN's NetDetector
  • Sandstorm's NetIntercept - Passive monitoring appliance. Qt/X11 GUI. FreeBSD platform. Uses forensic parsers written by Sandstorm to access document content and metadata.

Flow-Based Systems

Tips and Tricks

  • The time between two events triggered by an intruder (as seen in logfiles, for example) can be helpful. If it is very short, you can be pretty sure that the actions were performed by an automated script and not by a human user.