If you are interested in participating in Time Machine development, please make yourself known on the mailing list. ICSI’s resources for this project are unfortunately limited at this time and we appreciate any help.
About
There are times when it would be extraordinarily convenient to record the entire contents of a high-volume network traffic stream, in order to later "travel back in time" and inspect activity that has only become interesting in retrospect. Two examples are security forensics — determining just how an attacker compromised a given machine — and network trouble-shooting, such as inspecting the precursors to a fault after the fault.
To perform this task efficiently, the packets are first stored in a ring buffer in the memory (RAM), later the packets are copied to (hard) disk. This allows the time machine to smoothen capture bandwidth peaks in memory and store huge amounts of traffic on disk, covering several days of network traffic. The time machine is designed to work in Gbps environments.
Since it is not feasible to capture the complete load of a fully utilized Gbps link to disk, the time machine utilizes a mechanism called "connection cutoff" to reduce the the amount of data to process. This "connection cutoff" only records the first X bytes of every monitored connection (identified via the 5-tuple of source and destination IP and Port and the transport protocol). Indeed this approach it does not impair the analysis capabilities (unless the cutoff is set to low) because most of the "interessting" data is located in the first few packets of a connection. The effiency of this approach comes from leveraging the heavy-tailed nature of network traffic: because the bulk of the traffic in high-volume streams comes from just a few connections.
To take full advantage of this recording it is import to be able to quickly locate certain packets. For example one might be interested in all packets of a specific connection or all packets from one IP address. This is achieved by indexing stored packets. The indexes to create can be specified, for example one could create indexes for the connection 5-tuple, for IP address pairs, for IP addresses, etc. One can than issue a queries for a specific index to the time machine and the time machine will lookup the query in its index and will return all stored packets matching the query.
To further streamline the analysis capabilities we have coupled the TimeMachine with the Zeek network intrusion detection system (IDS) www.zeek.org. Thus the IDS can directly interact with the TimeMachine and request historic traffic to represent it to a security analyst or to do retrospective analysis.
Download
Latest release of Time Machine can be found at the link below. A new release at ICSI will follow soon.
At this point in time we recommend that new users clone our git repository and run that.
Development
Run the following command to checkout TimeMachine’s master:
git clone --recursive https://github.com/zeek/time-machine
Browse source at GitHub
Mailing Lists
Issue Tracker
History
2010-02-26 - Project moved to ICSI from its previous location. Old URL.
License
The TimeMachine is a joint project of the Technische Universität Berlin, the Technische Universität München, and the ICSI (University of California Berkeley). It is open-source and published under the BSD license.
Page Contents
Quick Links
- 13 February 2020: Ask the Zeeksperts - Aashish Sharma
- 18 February 2020 - Portland OR: Zeek Days Workshops
- 27 February 2020: Ask the Zeeksperts
- 7-9 October 2020 - Austin, Texas: ZeekWeek 2020
