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
- NetworkMiner is an open source Network Forensics Tool available at SourceForge
- Xplico is an Internet/IP Traffic Decoder (NFAT). Protocols supported: HTTP, SIP, FTP, IMAP, POP, SMTP, TCP, UDP, IPv4, IPv6, ...
- Chaosreader is a session reconstruction tool (supports both live or captured network traffic)
- NetFSE is a web-based search and analysis application for high-volume network data available at NetFSE.org
- NetSleuth is a live and retrospective network analysis and triage tool.
Commercial Network Forensics
- WildPackets OmniPeek  
- E-Detective  
- Code Green Networks Content Inspection Appliance - Passive monitoring and mandatory proxy mode. Easy to use Web GUI. Linux platform. Uses Stellent Outside In to access document content and metadata.
- NETRESEC NetworkMiner Professional (portable network forensic analysis tool for Windows)
- NetWitness Corporation - Freeware/Commercial, Enterprise-Wide, Real-Time Network Forensics NetWitness
- Network Instruments 
- NIKSUN's NetDetector
- PacketMotion 
- Sandstorm's NetIntercept - Passive monitoring appliance. Qt/X11 GUI. FreeBSD platform. Uses forensic parsers written by Sandstorm to access document content and metadata.
- Mera Systems NetBeholder
- InfoWatch Traffic Monitor
- MFI Soft SORMovich (in Russian)
- Solera Networks - Provider of full packet capture network forensics appliances Solera Networks
- Arbor Networks
- GraniteEdge Networks
- Lancope http://www.lancope.com/
- Mantaro Product Development Services http://www.mantaro.com/products/MNIS/index.htm
- Mazu Networks http://www.mazunetworks.com/
These systems combine flow analysis, deep analysis, and security event monitoring and reporting.
- Q1 Labs http://www.q1labs.com/
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.