FloCon 2006 Archive

Presentation
By
Artifacts from the program of FloCon 2006 (October 9-12 in Vancouver, Washington).
Publisher

Software Engineering Institute

Abstract

This FloCon conference included 12 papers and 13 presentations given by experts in the field of flow analysis. Discussions covered topics such as flow processing, flow measurement, network traffic, and analysis methods.

This archive includes:

  • A Case for Packet Sampling, Tanja Zseby
  • A System Architecture for Processing Flows, Raj Srinivasan
  • A Traffic Analysis of a Small Private Network Compromised by an Online Gaming Host (White Paper and Presentation), Ron McLeod
  • Analysis Methods Discussion
  • Anomaly Detection Through Blind Flow Analysis Inside a Local Network (White Paper and Presentation), Ron McLeod
  • Anomaly Sampling (Bringing Diversity to Network Security), David Moore
  • Anomaly-Based BotServer (and more!) Detection, Jim Binkley
  • Attribution and Aggregation of Network Flows for Security Analysis (White Paper and Presentation), Annarita Giani, Ian Gregorio-de Souza, Vincent Berk, and George Cybenko
  • Bidirectional Flow Measurement, IPFIX, and Security Analysis, Elisa Boschi and Brian Trammell
  • Identifying Anomalous Network Traffic Through the Use of Client Port Distribution, Josh Goldfarb
  • Impact of Packet Sampling on Anomaly Detection Metrics, Daniela Brauckhoff, Bernhard Tellenbach, Arno Wagner, Anukool Lakhina, and Martin May
  • IPFIX/PSAMP: What Future Standards Can Offer to Network Security (White Paper and Presentation), Tanja Zseby, Elisa Boschi, Thomas Hirsch, and Lutz Mark
  • RAVE: The Retrospective Analysis and Visualization Engine, Phil Groce and John Prevost
  • Scalable Flow Analysis (White Paper and Presentation), Abhishek Kumar and Sapan Bhatia
  • System Requirements for Flow Processing, Raj Srinivasan
  • The Effect of Packet Sampling on Anomaly Detection, Daniela Brauckhoff, Bernhard Tellenbach, Arno Wagner, Anukool Lakhina, and Martin May
  • The Past and Future of Flow Analysis (Keynote), John McHugh

This content was created for a conference series or symposium and does not necessarily reflect the positions and views of the Software Engineering Institute.