ip flow anonymisa on support
play

IP Flow Anonymisa/on Support dra6boschiipfixanon03 Elisa Boschi, - PowerPoint PPT Presentation

IP Flow Anonymisa/on Support dra6boschiipfixanon03 Elisa Boschi, Brian Trammell Hitachi Europe, Zrich [See h&p://people.ee.ethz.ch/~boschie/dra7boschiipfixanon03.txt] Monday 23 March 2009, San Francisco,


  1. IP Flow Anonymisa/on Support dra6‐boschi‐ipfix‐anon‐03 Elisa Boschi, Brian Trammell – Hitachi Europe, Zürich [See h&p://people.ee.ethz.ch/~boschie/dra7‐boschi‐ipfix‐anon‐03.txt] Monday 23 March 2009, San Francisco, California, USA

  2. IETF 74 ‐ IPFIX WG – San Francisco, California 23 rd March 2009 Why?  Standardiza/on of flow export [RFC5101] and storage representa/ons [dra6‐ieX‐ipfix‐file] removes a technical barrier to data sharing for  interdomain measurement efforts, and  trace publica/on for research.  End‐user privacy concerns s/ll a barrier.  Anonymisa/on provides one toolset for addressing these concerns.  Need a way to represent the anonymisa/on status of exported or stored data. 2

  3. IETF 74 ‐ IPFIX WG – San Francisco, California 23 rd March 2009 What?  Node and user iden/fying informa/on:  IP addresses  MAC addresses [TODO]  Addi/onal informa/on that can be used to profile users and/or aeack anonymisa/on techniques:  ports (applica/on profiling)  /mestamps and counters (host profiling, fingerprin/ng)  most other fields (fingerprin/ng) 3

  4. IETF 74 ‐ IPFIX WG – San Francisco, California 23 rd March 2009 How?  Generaliza/on  mapping of mul/ple real values to a single anonymised value.  aggregates; does not preserve countability.  [One‐Way] Subs/tu/on  one‐to‐one mapping of real to anonymised values.  count of unique values preserved across anonymisa/on.  [One‐Way] Set Subs/tu/on  each anonymised value respresents a single real value, but  each real value may be represented by mul/ple anonymised values.  does not aggregate, does not preserve countability. 4

  5. IETF 74 ‐ IPFIX WG – San Francisco, California 23 rd March 2009 For how long?  Anonymisa/on func/ons map a real space of values to an anonymised space.  This mapping func/on may change over /me (e.g. through rekeying or dele/on of permuta/on table), affec/ng long‐term comparability of anonymised datasets.  Stability measures this change. 5

  6. IETF 74 ‐ IPFIX WG – San Francisco, California 23 rd March 2009 Anonymisa/on Record scope iden/fies {Template, IE} index op/onal (mul/‐IE only) Technique used to anonymise Associated with a Template, exported via IPFIX Op/ons. 6

  7. IETF 73 ‐ IPFIX WG ‐ Minneapolis 23 rd March 2009 Supported Techniques (1)  None  Data assumed to be real at EP  Undefined  no assump/on anonymisa/on at EP  Dele/on/“Black Marker”  IPFIX supports this na/vely – simple removal of IE from Template  Precision Degrada/on/Trunca/on (Generaliza/on)  Replacement of host addresses with network addresses  Timestamp and counter degrada/on 7

  8. IETF 74 ‐ IPFIX WG – San Francisco, California 23 rd March 2009 Supported Techniques (2)  Binning (Generaliza/on)  Enumera/on (Set Subs/tu/on)  Assignment of a unique value to each record.  May be applied to preserve ordering, esp. with /mestamps.  Permuta/on (Subs/tu/on)  Assignment of a unique anonymised value to each real value.  Prefixed Permuta/on (Subs/tu/on)  Permuta/on that preserved structure present in source data (e.g. CryptoPAN prefix‐preserving IP address anonymisa/on) 8

  9. IETF 74 ‐ IPFIX WG – San Francisco, California 23 rd March 2009 Supported Stability Classes  Undefined  No assump/on about stability at EP  Session  All anonymisa/on parameters stable for dura/on of Transport Session.  Exporter‐Collector  All anonymisa/on parameters stable for an EP‐CP pair.  Different sessions between same EP and CP are comparable.  Stable  All anonymisa/on parameters stable for an EP.  Different sessions from same EP are comparable. 9

  10. IETF 74 ‐ IPFIX WG – San Francisco, California 23 rd March 2009 Guidelines for IPFIX Anonymisa/on  Certain IPFIX data structures can leak informa/on about original data:  IPFIX Message Header Export Time  IPFIX Message Header Observa/on Domain, if linked to EP/MP address  expor/ngProcessIPv[46]Address  collec/onTime and File Time Window Op/ons  Care should be taken with these to prevent deanonymisa/on. 10

  11. IETF 74 ‐ IPFIX WG – San Francisco, California 23 rd March 2009 Next Steps  Con/nued work on Open Issues:  MAC address anonymisa/on  Finaliza/on of classifica/on, stability classes, and techniques  Editorial comple/on  IANA Considera/ons, Security Considera/ons, Examples  nonsensical IE/Technique combina/ons  other relevant guidelines  Considera/on as new Working Group item within the context of the Mediator effort, when appropriate. 11

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend