2006
DOI: 10.1109/glocom.2006.280
|View full text |Cite
|
Sign up to set email alerts
|

NIS04-2: Detection of DNS Anomalies using Flow Data Analysis

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
28
0

Year Published

2012
2012
2019
2019

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 35 publications
(28 citation statements)
references
References 1 publication
0
28
0
Order By: Relevance
“…This is instead of the IP address of the queried domain because root nodes do not have complete information of every domain in the Internet. If it has data for the queried domain, the 1 Faculty of Engineering, Toyohashi University of Technology, Toyohashi, Aichi 441-8580, Japan 2 Internet Initiative Japan Inc., Iidabashi Grand Bloom, Chiyoda, Tokyo 102-0071, Japan 3 ComWorth Co., Ltd., Ota, Tokyo 143-0026, Japan a) takeuchi2015@ppl.cs.tut.ac.jp next-level server replies an IP address corresponding to the domain. Otherwise, the server introduces a 2nd next-level server as in the previous step.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…This is instead of the IP address of the queried domain because root nodes do not have complete information of every domain in the Internet. If it has data for the queried domain, the 1 Faculty of Engineering, Toyohashi University of Technology, Toyohashi, Aichi 441-8580, Japan 2 Internet Initiative Japan Inc., Iidabashi Grand Bloom, Chiyoda, Tokyo 102-0071, Japan 3 ComWorth Co., Ltd., Ota, Tokyo 143-0026, Japan a) takeuchi2015@ppl.cs.tut.ac.jp next-level server replies an IP address corresponding to the domain. Otherwise, the server introduces a 2nd next-level server as in the previous step.…”
Section: Introductionmentioning
confidence: 99%
“…Karasaridis et al [3] introduced a method to detect DNS Cache Poisoning and DNS Tunneling. Unlike ordinary Intrusion Detection Systems, their method does not rely on known attack patterns called signatures.…”
Section: Introductionmentioning
confidence: 99%
“…The flow exporter aggregates packets with common properties into one flow until the flow is terminated. This termination can be caused by the expiration of flow cache entry (active time-out, idle time-out or resource constraints), natural expiration based on packet flags indicating connection end, emergency expiration or cache flush [7]. In networks with a large volume of traffic, it is necessary to have sufficiently large and free flow cache to avoid emergency expiration or cache flush, which may cause unwanted flow records split.…”
Section: Standard Flow Monitoringmentioning
confidence: 99%
“…Flow acquisition can be done by common network devices that support flow record export, such as routers, or by specialized network probes [7] which provides greater data accuracy and are able to effectively process a large volume of traffic. Figure 1 depicts a monitored network with the probes installed at the local network uplink and also inside the network.…”
Section: Standard Flow Monitoringmentioning
confidence: 99%
“…Anomaly based botnet detection, tries to detect bot activities based on several network behavior anomalies such as unexpected network latencies, network traffic on unusual and unused ports, high volumes of traffic for a midclass network or unusual system behaviors that could indicate the existence of malicious parties in the network (Feily et al, 2009). Karasaridis, Rexroad, & Hoeflin (2007) proposed an algorithm for detection and characterization of botnets using passive analysis. Their approach was based on flow data in transport layer.…”
Section: Anomaly Based Detection Techniquesmentioning
confidence: 99%