1. MobileMan IAB Meeting CORE: Design, Test-bed and Dissemination Pietro Michiardi Pietro.Michiardi@eurecom.fr Institut Eurecom

2. Outline  (Quick) CORE Overview  CORE Test bed Design Scenario  CORE Mechanism Dissemination: Web site (a la OLSR.org) Source code for Glomosim Source code & IPKG for Linux Familiar  “Doxygen” documentation for CORE Link to MobileMan deliverables & research papers  Input from IAB

3. Security in MANET  Managed environment A-priori trust Entity authentication  correct operation But: requirement for authentication infrastructure  Open environment NO a-priori trust authentication does not guarantee correct operation  cooperative security scheme

4. Node Misbehavior Selfish Nodes  Do not cooperate  Priority: battery saving  No intentional damage to other nodes.  Attacks:  passive denial of service  black hole  idle status Malicious Nodes  Goal: damage to other nodes  Battery saving is not a priority  Attacks:  active denial of service  traffic subversion  exploiting the security mechanism

5. CORE: principles Local Reputation as a measure of a node’s behavior. Basic idea: good reputation  node can use the network bad reputation  network utilization gradually denied  Gradual isolation of misbehaving nodes BUT it does not means that selfish nodes are not used!!! (re-integration mechanism not needed) Network Utilization Contribution

6. CORE: components  Monitoring mechanism: watchdog  Reputation: subjective, indirect, functional  Computing the reputation value  Filtering of “high frequency” fluctuations in node behavior

7. CORE Mechanism (overview) a b ic d g k e h m f n d: — — l: — — h:  — b: — — c: — — Node k has a valid route to node e: Node h does not Participate to the packet forwarding function No Distribution of Negative Ratings EXAMPLE: Black hole attack on packet forwarding function

8. CORE: Test bed (1)  Platform: IPAQ 39xx + Linux Familiar  802.11b Cards: wlan/orinoco Promiscuous mode MANDATORY  Ad hoc routing: OLSR Source vs. Table driven routing Need for secure OLSR  Manual Address Configuration  Standard Libraries Need for project-wide rules!!!

9. CORE: Test bed (2) FTP Client 192.168.50.2 OLSR FTP Server AiroPeek CORE 192.168.50.3 192.168.50.4 IPTABLES –mac xx:C2:D7:54 –j DROP 00:02:2D:C2:D7:54 00:02:2D:8F:99:61 00:02:2D:C2:D7:55 IPTABLES –mac xx:C2:D7:55 –j DROP SELFISHNESS IPTABLES Chain FORWARD (policy DROP) == BLACK HOLE ATTACK == OLSRCORE OLSRCORE

10. CORE implementation: Design  Initial implementation: CORE enforces only Packet Forwarding  User Space Linux Module Routing independent  (OLSR) Plug-in interface  Watchdog based on standard LibPcap

11. CORE implementation: Future directions  Game theoretical selfishness model Implementation of “rational behavior”  CORE + OLSR_Willingness PROs: Load balancing ~ power management CONs: Bogus willingness Attack  Reputation propagation PROs: Fast detection, Coherence CONs: Reputation message integrity  X-layering CORE provides information to other layers Which information can be used by CORE?

12. CORE: dissemination (1)  Motivation: Widely studied and adopted by the research community:  CS Dept. University of Pittsburgh  CS Dept. Virginia Tech  Information Security Group Royal Holloway, University of London  CS Dept. University of Trier  CS Dept. Rochester Institute of Technology  CS Dept. Universität Karlsruhe  Laboratory of Cryptography and System Security University of Budapest  CS Dept. University of California, Davis  RSA Laboratories  Faculty of Sciences, Vrije Universiteit  Universiteit Twente  EPFL Third party CORE implementation(s)  National Security Research Institute, Korea  Samsung electronics, Korea  Yonsei University, Korea  GOAL: CORE as a reference in cooperation enforcement mechanisms

13. CORE: dissemination (2)  Web site: Mailing list Releases Documentation (see next slide)  Simulation environment: Patch for Glomosim Patch for NS-2  Test bed: Source code & IPKG for IPAQ

14. CORE: Doxygen  Generate on-line documentation browser and/or off- line reference manual  Visualize relations between code elements: Include dependency graphs Inheritance diagrams  Link code to Deliverables & Research Papers  Common documentation platform for the project?

15. Input from IAB  Commercial implication of promiscuous mode operation  Selfishness models: Manual Energy-based …  Punishment models: Communication denial …

16. Conclusion  Project Status By the end of 2 nd year:  Standalone working prototype  Integration with other MMAN components 3 rd year activities:  Documentation  Fine tuning  Tests  Advanced features  Questions ? Thank you!