1 / 13

Flow Anomaly Detection in Firewalled Networks Research Report Mike Chapple December 15, 2005

Flow Anomaly Detection in Firewalled Networks Research Report Mike Chapple December 15, 2005. The Problem. Intruders are Clever!. Firewall Anomaly Detection. FADS Architecture. Forecast Development. Evaluation Criteria Number of connections Bytes to client Bytes to server

alden-pennington
Télécharger la présentation

Flow Anomaly Detection in Firewalled Networks Research Report Mike Chapple December 15, 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Flow Anomaly Detection in Firewalled NetworksResearch ReportMike ChappleDecember 15, 2005

  2. The Problem Intruders are Clever!

  3. Firewall Anomaly Detection

  4. FADS Architecture

  5. Forecast Development • Evaluation Criteria • Number of connections • Bytes to client • Bytes to server • Data Segmentation • Six time segments • Weekday traffic only

  6. Modeling Techniques Average 30 Standard Deviation 14 Forecast Range 9-51 Median 30 Interquartile Range 20 Forecast Range 0-60 Average 880 Standard Deviation 2,257 Forecast Range -2,507 – 4,267 Median 30 Interquartile Range 20 Forecast Range 0-60

  7. Evaluation Goals • Determine whether FADS produces a manageable number of alerts • Evaluate impact of external traffic • Examine three case studies for evidence of system effectiveness • Demonstrate performance is within bounds of feasibility

  8. Goal #1: Feasibility

  9. Goal #2: Impact of External Traffic

  10. Goal #3: Case Studies • Underflow alerts to a web server supporting academic functions • Overflow events to a reporting server in production datacenter • Overflow events related to file integrity monitoring

  11. Goal #4: Performance • Feasible to port this system to an online application • Processing 6-hour log file < 10 minutes • Forecasts generated in < 30 seconds • Evaluation dataset processed in ~ 4 seconds

  12. Future Work • Evaluation with extended dataset • Advanced modeling techniques including periodicity • Dynamic selection of time segments • Automation of processing for online analysis

  13. Questions?

More Related