Re: [Nmlrg] Machine Learning in network - solicitation for use cases
Jérôme François <jerome.francois@inria.fr> Thu, 17 September 2015 20:53 UTC
Return-Path: <jerome.francois@inria.fr>
X-Original-To: nmlrg@ietfa.amsl.com
Delivered-To: nmlrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id DD2591A0203
for <nmlrg@ietfa.amsl.com>; Thu, 17 Sep 2015 13:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.26
X-Spam-Level:
X-Spam-Status: No, score=-6.26 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3,
RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id jaW-Q1PkaBcX for <nmlrg@ietfa.amsl.com>;
Thu, 17 Sep 2015 13:53:39 -0700 (PDT)
Received: from mail3-relais-sop.national.inria.fr
(mail3-relais-sop.national.inria.fr [192.134.164.104])
(using TLSv1.2 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 5356B1A0242
for <nmlrg@irtf.org>; Thu, 17 Sep 2015 13:53:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.17,549,1437429600"; d="scan'208";a="147661221"
Received: from unknown (HELO [192.168.43.145]) ([80.215.168.30])
by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA;
17 Sep 2015 22:53:37 +0200
Message-ID: <55FB2850.90302@inria.fr>
Date: Thu, 17 Sep 2015 22:53:36 +0200
From: =?UTF-8?B?SsOpcsO0bWUgRnJhbsOnb2lz?= <jerome.francois@inria.fr>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "nmlrg@irtf.org" <nmlrg@irtf.org>
References: <5D36713D8A4E7348A7E10DF7437A4B927BB2962B@nkgeml512-mbx.china.huawei.com>
<55F99621.4040409@inria.fr>
<5D36713D8A4E7348A7E10DF7437A4B927BB6442C@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B927BB6442C@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/nmlrg/B9epaa2SdQLbSQuSgS1AkbChQeA>
Subject: Re: [Nmlrg] Machine Learning in network - solicitation for use cases
X-BeenThere: nmlrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Machine Learning Research Group <nmlrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmlrg>,
<mailto:nmlrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmlrg/>
List-Post: <mailto:nmlrg@irtf.org>
List-Help: <mailto:nmlrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmlrg>,
<mailto:nmlrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2015 20:53:42 -0000
Le 17/09/2015 08:36, Sheng Jiang a écrit : > Hi, Jerome, > > Thanks for sharing. It would be helpful if you could introduce a little bit more on how to leverage the machine learning in your use case, such as the learning objects and objectives, etc. It would also useful to discuss the working principle in your use case. Assuming a protocol, the goal of this work was to automatically identifiy every device type using this protocol. By identification, I mean the name and version for software and the manufacturer and series for hardware. As usual, the feature definition was the core of the problem.: - case 1 relies on the syntactic trees extracted from messages using the protocol grammar - case 2 relies on a temporal behavioral tree which represents observed sequence of message with inter-arrival time information We then applied multi-class support vector machine with a learning stage. Hence, specific kernel functions had to been defined. We also tested other approaches like unsupervised graph-based clustering with tree-based based on isomorphic trees. In our work, we specifically targeted SIP and so applied the identification for one or a set of a single session. Then, different use cases can benefit from this approach: network inventory, detection of vulnerable/forbidden devices or automatically generate rules for stateful firewall (in that case, the classes which are learnt are not the device types but the anomalies). Of course, in a perfect world, device type can be easily identified by some configuration information or, for example, a user agent header can be included in message. However, this can be easily faked. Feature engineering was so very important. Messages were preprocessed to create these trees and metrics (distances, kernels) had to be defined. I have some other experiences with flow-based anomaly detection or phishing detection and I observed that fine-tuning the feature is a key step (more than ML algorithm parameter tuning). jerome > Many thanks and best regards, > > Sheng > >> -----Original Message----- >> From: nmlrg [mailto:nmlrg-bounces@irtf.org] On Behalf Of Jér?me Fran?ois >> Sent: Thursday, September 17, 2015 12:18 AM >> To: nmlrg@irtf.org >> Subject: Re: [Nmlrg] Machine Learning in network - solicitation for use cases >> >> I have experienced using ML for device fingerprinting meaning that by >> observing traffic pattern (message sequence and timing information) it >> is possible to automatically retrieve the precise types of device (name, >> version, series). >> It is particularily interesting to make network inventory as most of >> cases there are some unknwon devices on the network (user or old ones) >> and finally potentially identifying vulnerable devices from a security >> point of view. >> >> jerome >> >> Le 31/08/2015 05:15, Sheng Jiang a écrit : >>> Hi, all, >>> >>> Thanks for subscribe to NMLRG (Network Machine Learning) mail list. As we >> know, there are already many ongoing researches for Machine Learning in >> network, in many areas. But up to now, there are few matured applications >> yet. So it is the time for a Research Group to work on this future-oriented >> technology. >>> The first step would be to collect possible use cases: where the machine >> learning mechanism could be used in networks. The use cases does not need >> to be mature, but should have potential. >>> Note that this topic is rapidly moving from academic research into practical >> application. Therefore, use cases from university environments, industrial >> research and development organizations are all welcome. >>> Best regards, >>> >>> Sheng >> _______________________________________________ >> nmlrg mailing list >> nmlrg@irtf.org >> https://www.irtf.org/mailman/listinfo/nmlrg
- [Nmlrg] Machine Learning in network - solicitatio… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Dacheng Zhang
- [Nmlrg] Using Machine Learning for Network Device… Liubing (Leo)
- Re: [Nmlrg] Using Machine Learning for Network De… Sheng Jiang
- Re: [Nmlrg] Using Machine Learning for Network De… Liubing (Leo)
- Re: [Nmlrg] Using Machine Learning for Network De… Sheng Jiang
- Re: [Nmlrg] Using Machine Learning for Network De… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Dacheng Zhang
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Brian E Carpenter
- Re: [Nmlrg] Machine Learning in network - solicit… Dacheng Zhang
- Re: [Nmlrg] Machine Learning in network - solicit… Dacheng Zhang
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Brian E Carpenter
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Brian E Carpenter
- Re: [Nmlrg] Machine Learning in network - solicit… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Brian E Carpenter
- Re: [Nmlrg] Machine Learning in network - solicit… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Jérôme François
- Re: [Nmlrg] Machine Learning in network - solicit… Jérôme François
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Sebastian Abt
- Re: [Nmlrg] Machine Learning in network - solicit… Sebastian Abt
- Re: [Nmlrg] Machine Learning in network - solicit… Sebastian Abt
- Re: [Nmlrg] Machine Learning in network - solicit… Sebastian Abt
- Re: [Nmlrg] Machine Learning in network - solicit… Sebastian Abt
- Re: [Nmlrg] Machine Learning in network - solicit… Brian E Carpenter
- Re: [Nmlrg] Machine Learning in network - solicit… Jérôme François
- Re: [Nmlrg] Machine Learning in network - solicit… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Jérôme François
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang