Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

"Extensible Network Configuration and Communication Framework"


Published on

  • Be the first to comment

  • Be the first to like this

"Extensible Network Configuration and Communication Framework"

  1. 1. Extensible Network Configuration and Communication Framework Todd Sproull and John Lockwood {todd,lockwood} 7 th International Working Conference on Active and Programmable Networks (IWAN) November 2005
  2. 2. Overview <ul><li>Background </li></ul><ul><ul><li>Project motivation </li></ul></ul><ul><li>Extensible Network Configuration Architecture </li></ul><ul><li>Experimental Results </li></ul><ul><ul><li>Initial results using the Emulab testbed </li></ul></ul><ul><li>Conclusions </li></ul>
  3. 3. Background <ul><li>Administrators currently overwhelmed securing networks </li></ul>Wireless Router Traffic Shaper Intrusion Prevention System (IPS) NAT / Firewall Intrusion Detection System (IDS) <ul><li>Security devices in the network help combat the problem </li></ul><ul><ul><li>Intrusion Detection or Prevention Systems (IDS) or (IPS) </li></ul></ul><ul><ul><li>Packet shapers </li></ul></ul><ul><ul><li>Firewalls </li></ul></ul><ul><li>Overhead associated with managing these devices is fairly high </li></ul><ul><ul><li>Require manual configuration </li></ul></ul><ul><ul><li>Lack interoperability with other security devices </li></ul></ul>
  4. 4. Problem Statement <ul><li>Objective </li></ul><ul><ul><li>Develop generic infrastructure for management of security devices </li></ul></ul><ul><li>Challenges </li></ul><ul><ul><li>Need an abstraction for communication between heterogeneous security devices </li></ul></ul><ul><ul><li>Need to provide interfaces to configure key components of a security device </li></ul></ul><ul><ul><ul><li>Example: Ability to update rules on each firewall supported in the overlay </li></ul></ul></ul><ul><li>Proposed Solution </li></ul><ul><ul><li>Deploy an overlay network of security devices </li></ul></ul><ul><ul><li>Allow nodes to communicate through eXtensible Markup Language (XML) </li></ul></ul><ul><ul><li>Create generic abstractions of a device are advertised to peers </li></ul></ul><ul><ul><ul><li>Example: “Advertisement: I provide firewall capabilities” </li></ul></ul></ul>
  5. 5. Description of Framework <ul><li>Create overlay network of security devices </li></ul><ul><li>Devices subscribe to events of interest </li></ul><ul><ul><li>Administrative Updates </li></ul></ul><ul><ul><li>Virus Signatures </li></ul></ul><ul><ul><li>Malicious IP flows to rate limit </li></ul></ul><ul><li>Administrator joins overlay to issue updates </li></ul><ul><ul><li>Messages sent to each peer or a single group </li></ul></ul><ul><li>Nodes communicate with each other through services </li></ul><ul><li>Nodes discover services in each group </li></ul>? ? ? ? ? <ul><li>Nodes create and join groups of interest </li></ul><ul><ul><li>Administrative </li></ul></ul><ul><ul><li>Firewall </li></ul></ul><ul><ul><li>Anomaly Detection </li></ul></ul><ul><li>Overlay software interfaces directly with applications executing on the node </li></ul><ul><ul><li>Modifying configuration files </li></ul></ul><ul><ul><li>Restarting processes </li></ul></ul>Wireless Router Traffic Shaper Intrusion Prevention System (IPS) NAT / Firewall Intrusion Detection System (IDS)
  6. 6. Implementation <ul><li>Overlay network built using the JXTA API </li></ul><ul><ul><li>Provides open infrastructure to create Peer-to-Peer (P2P) networks </li></ul></ul><ul><li>Protocols built into JXTA include </li></ul><ul><ul><li>Peer Discovery </li></ul></ul><ul><ul><ul><li>Discover peers, groups, and service in the overlay </li></ul></ul></ul><ul><ul><li>Endpoint Routing </li></ul></ul><ul><ul><ul><li>Provide route information to peers, simplifying communication behind firewalls and NAT </li></ul></ul></ul><ul><ul><li>Pipe Binding </li></ul></ul><ul><ul><ul><li>Creates communication channels for sending and receiving XML messages </li></ul></ul></ul><ul><li>Supports various programming languages </li></ul><ul><ul><li>Java (J2SE) </li></ul></ul><ul><ul><li>C </li></ul></ul><ul><ul><li>Mobile Java (J2ME) </li></ul></ul><ul><ul><li>Ruby </li></ul></ul>
  7. 7. Example Security Nodes <ul><li>Current research explores three hardware platforms </li></ul>FPX with FPGA Hardware Pentium M Embedded Processor FPGA Worm Detector SPADE None Anomaly or Event Detection FPGA Queue Manager Hierarchical Token Buckets (HTB) Linksys QoS Support Quality of Service FPGA Snort Lite Snort or Bro Snort with limited ruleset Intrusion Detection or Prevention Extensible Switch Workstation Wireless Router 200MHz MIPS
  8. 8. Experimental Setup <ul><li>Testbed experiment evaluates overhead in Processing and Routing XML Messages in JXTA </li></ul><ul><ul><li>XML Publish/Subscribe </li></ul></ul><ul><ul><li>JXTA Pipes Creation </li></ul></ul><ul><ul><li>JXTA Message Notification </li></ul></ul><ul><li>Traffic Generator sends XML messages to Publisher </li></ul><ul><li>Publisher parses XML messages and forwards message to clients based on individual service subscription </li></ul><ul><li>Experiment created in Emulab testbed </li></ul><ul><ul><li>2GHz Pentium 4 nodes </li></ul></ul><ul><ul><li>100Mbit/sec Ethernet links </li></ul></ul>Publisher Subscribers Network A Network B XML Traffic Generator
  9. 9. Experimental Results <ul><li>Experiments performed measure packet loss as packets per second (pps) increase </li></ul><ul><ul><li>XML Traffic Generator increases pps to Publisher </li></ul></ul><ul><ul><li>Publisher forwards relevant messages to a single subscriber </li></ul></ul><ul><ul><ul><li>All messages forwarded in this experiment </li></ul></ul></ul><ul><ul><li>Loss represents packets not received by subscriber </li></ul></ul><ul><li>Relatively low performance deal with overhead in JXTA creating an “output pipe” for each connection </li></ul><ul><ul><li>The overhead is approximately 40ms per connection </li></ul></ul><ul><li>Potential optimizations </li></ul><ul><ul><li>Creating output pipe once per node, assuming the peer is available </li></ul></ul><ul><ul><li>Utilizing JXTA sockets instead of JXTA pipes </li></ul></ul>
  10. 10. Future Work <ul><li>Evaluate security functions of the overlay </li></ul><ul><ul><li>Example: Benchmark nodes ability to update firewall rules in the presence of an attack </li></ul></ul><ul><li>Deploy all three platforms in one testbed environment </li></ul><ul><ul><li>Utilize Open Network Labs </li></ul></ul><ul><ul><ul><li>Testbed for developing high performance network applications </li></ul></ul></ul><ul><ul><li>Investigate Hardware Plug-ins </li></ul></ul>
  11. 11. Conclusions <ul><li>Proposed Architecture for Network Configuration and Communication </li></ul><ul><ul><li>Overlay network distributing XML messages between devices </li></ul></ul><ul><li>Developed and deployed framework in network testbed </li></ul><ul><li>Obtained Preliminary Results </li></ul><ul><ul><li>Quantified overhead of JXTA protocol and XML message parsing in publish subscribe network </li></ul></ul>
  12. 12. Acknowledgments <ul><li>Research Group </li></ul><ul><ul><li>Reconfigurable Network Group </li></ul></ul>