2015 IEEE 2nd International Conference on Cyber Security and Cloud Computing 2015
DOI: 10.1109/cscloud.2015.53
|View full text |Cite
|
Sign up to set email alerts
|

Design of Detecting Botnet Communication by Monitoring Direct Outbound DNS Queries

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
8
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
7
2

Relationship

1
8

Authors

Journals

citations
Cited by 14 publications
(10 citation statements)
references
References 3 publications
0
8
0
Order By: Relevance
“…The evaluation metric was the false positive rate (FPR) in terms of malicious DNS queries, which is presented in Table 8. More specifically, we use the first ten pcap files in log data, which were obtained in our previous study [32]. First, we manually confirmed that the pcap files do not contain any malicious traffic.…”
Section: Discussionmentioning
confidence: 99%
“…The evaluation metric was the false positive rate (FPR) in terms of malicious DNS queries, which is presented in Table 8. More specifically, we use the first ten pcap files in log data, which were obtained in our previous study [32]. First, we manually confirmed that the pcap files do not contain any malicious traffic.…”
Section: Discussionmentioning
confidence: 99%
“…In their further investigation, ~22% of these queries were targeting suspicious URLs identified by virustotal [169]. A similar approach is used by Jin et al in [157], which proposes a novel DNS-based detection approach for detecting botnet activity. The paper focuses on direct outbound DNS queries on non-standard authoritative name servers to identify botnets, which use TXT records to send commands.…”
Section: Domain Name System (Dns) Based Detectionmentioning
confidence: 99%
“…al. [8] designed a botnet communication detection method by collecting authoritative NS records and their IP addresses, as well as monitoring direct outbound DNS queries. Their method is based on storing NS records with corresponding IP addresses of valid query response pairs, IP addresses of public DNS servers, and ISP specified DNS servers in a NS-IP database.…”
Section: Related Workmentioning
confidence: 99%
“…Any destination IP address not included in the previously archived Name Server (NS) records is considered suspicious and should be investigated. In this way, "all unusual domain name resolution that uses direct outbound DNS query can be monitored" [8].…”
Section: Related Workmentioning
confidence: 99%