2016
DOI: 10.1002/sec.1516
|View full text |Cite
|
Sign up to set email alerts
|

Traffic classification for managing Applications’ networking profiles

Abstract: Along with the growing number of applications and end‐users, online network attacks and advanced generations of malware have continuously proliferated. Many studies have addressed the issue of intrusion detection by inspecting aggregated network traffic with no knowledge of the responsible applications/services. Such systems fail to detect intrusions in applications whenever their abnormal traffic fits into the network normality profiles. We address the problem of detecting intrusions in (known) applications w… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
6
2
1

Relationship

2
7

Authors

Journals

citations
Cited by 12 publications
(4 citation statements)
references
References 63 publications
0
4
0
Order By: Relevance
“…The survey studies some of the encryption protocols, their packet structure and standard behavior in the network, as well as, the observable features that can be extracted for traffic analysis. In addition, [8] surveys the most common methodologies for traffic classification.…”
Section: A Related Workmentioning
confidence: 99%
“…The survey studies some of the encryption protocols, their packet structure and standard behavior in the network, as well as, the observable features that can be extracted for traffic analysis. In addition, [8] surveys the most common methodologies for traffic classification.…”
Section: A Related Workmentioning
confidence: 99%
“…To meet the first requirement, we proposed architectures that provide a binding between network traffic and source application that allows checking whether a packet/flow claimed by an application conforms to its expected traffic model [42], [43]. For the second requirement, we proposed GMM with automatic learning to model per-application traffic [2], [39], [44]. However, our prior application-specific models were still trained with features obtained from the entire packet flows and were not accurate enough for detecting anomalies in a timely manner before the end of a flow.…”
Section: B Traffic Verificationmentioning
confidence: 99%
“…Herein, we want to answer a more fine-grained question: is this packet/flow normal for its source application? To answer this question, the system requires to: (i) identify the claimant (source application) for being responsible for the traffic and (ii) model the genuine traffic of each application present in the network [3].…”
Section: Problem Definition and Motivationsmentioning
confidence: 99%