<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Technique for IoT Cyberattacks Detection Based on DNS Traffic Analysis</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Khmelnitsky National University</institution>
          ,
          <addr-line>Khmelnitsky</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Silesian University of Technology</institution>
        </aff>
      </contrib-group>
      <fpage>0000</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>The dynamic growth of the number of cyberattacks, which perform destructive against the IoT devices, forces the developers of anti-virus software to implement new methods and algorithms for their search and disposal. The existing statistics prove the need of the novel cyberattacks detection approaches development. The paper presents a new technique for IoT cyberattacks detection based on DNS traffic analysis is presented. The method allows detecting IoT botnet cyberattacks. The method has the heuristic and proactive nature. It is based on the gathering of the set of features that may indicate the IoT cyberattacks presence. The mechanism of attack detection system is based on the cyberattacks' features gathering from network and feature vectors construction. As the classification algorithms a semi-supervised fuzzy c-means clustering, SVM and Artificial Immune System classification algorithms were employed.</p>
      </abstract>
      <kwd-group>
        <kwd>Internet of Things</kwd>
        <kwd>Cyberattack</kwd>
        <kwd>DNS</kwd>
        <kwd>Network traffic</kwd>
        <kwd>Network</kwd>
        <kwd>Cybersecurity</kwd>
        <kwd>Computer system</kwd>
        <kwd>Host</kwd>
        <kwd>Malicious traffic</kwd>
        <kwd>Attacks Detection</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Every year, new types of devices are used in the Internet of Things (IoT) market:
home automation, smart cities, medicine, and agriculture. The devices’ firmware is
being developed without taking into account the latest cybersecurity requirements [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
and, many IoT devices manufacturers are striving to make their products as cheap and
expedite as possible by simplifying security features [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        Despite the small computing power of individual IoT devices, their sheer number,
combined into a single malicious bot-managed network, poor security (or even lack
thereof) and permanent Internet connection make them a convenient tool for
organizing powerful cyberattacks [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>
        Malicious traffic volume generated by IoT botnets is usually much higher than the
of botnet’ traffic volume generated from personal computers [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        Thus, cyberattacks against the IoT devices are a major important cybersecurity
problem because they are difficult to detect, localize and mitigate [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Related work</title>
      <p>
        In [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] various IoT botnet detection approaches are discussed. In [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] the Rustock IoT
botnet which employs the evasion technique fast-flux to communicate with its bots
and command and control (C&amp;C) centers is investigated. For its detection the set of
features were analyzed and number of classifiers were used.
      </p>
      <p>
        In paper [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] an approach for botnet detecting of the on activity within consumer
IoT devices and networks was presented. As a tool of making conclusion the kind of
neural network (with the bidirectional long short term memory) was involved. As a
tool of the communication detection between attackers the word embedding packets
were employed. The proposed technique was compared with other ones, based on the
usage of other kinds of neural networks. In order to determine the effectiveness of the
detection, the Mirai IoT botnet was used. Experimental results demonstrated that the
bidirectional approach increased the detection time, but improved its efficiency.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] the functioning of the Mirai IoT bontet is presented. It is also demonstrated
an approach for its detection using the network analysis.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] a new behavior-based approach for DDoS detection in IoT network traffic
was presented. It describes the specific IoT network’s features, that may indicate the
attacks presence in the network.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] a novel IDS able to detect DNS IoT botnets’ attacks. It is an effective
mitigation tool against the attacks performed by the IoT botnets. Technique involves the
detection of IoT attacks that employ DNS, HTTP and MQTT protocols. It is based on
statistical processing and uses machine such learning algorithms as Artificial Neural
Network, Naive Bayes, and decision tree. The experimental cases with usage of the
known botnet datasets were presented.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] a new approach IoT botnet DDoS attack detection which is able to mitigate
the cyberattacks is presented. It is an event management-based approach and enables
the possibility of the DDoS attack blocking. Approach monitors the network traffic
concerning the compromised IoT devices taking into account specific network
features.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] a novel IoT botnet detecting approach based on the usage of the machine
learning algorithms is presented. It is able to identify the botnet cyberattacks
performed using the infected IoT devices. The detection process involved the “Grey
Wolf” algorithm as well as the SVM and demonstrated promising results.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] the aspects of the IoT cybersecurity concerning the smart cities
infrastructure are presented. Furthermore, a new anomaly-based technique for the IoT attacks
detection is proposed. It uses the Random Forest algorithms and demonstrated good
detection effectively concerning infected IoT devices.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] a new technique for DDoS detection was presented. It described the
infected IoT devices’ network traffic generation. Based on this, a new approach for
anomaly detection was produced.
      </p>
      <p>Nevertheless, the mentioned above approaches have common drawbacks: they
don’t take into account a set of techniques that may be used by IoT botnets to perform
the cyberattacks such as cycling of IP mapping, domain flux, fast flux, and DNS
tunneling. In addition, techniques demonstrate low IoT botnets detection efficiency and
have high false positives rate.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Technique for IoT Cyberattacks Detection Based on DNS</title>
    </sec>
    <sec id="sec-4">
      <title>Traffic Analysis</title>
      <p>
        DNS is widely used to establish links between IoT botnets’ bots and their command
and control centers (C&amp;C) attackers [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. It makes it possible to control the IoT botnet
anonymously and flexibly. Various complex techniques are used to avoid the C&amp;C
servers tracking through DNS: cycling of IP mapping, domain flux, fast flux, and
DNS tunneling [
        <xref ref-type="bibr" rid="ref1 ref2 ref5">1, 2, 5</xref>
        ].
      </p>
      <p>In order to solve this problem, a new technique for IoT cyberattacks detection
based on DNS traffic analysis was proposed. It is based on the detection of the IoT
botnets’ communication with C&amp;C over DNS protocol, and consists of steps:
1. Gathering of the incoming DNS traffic of the IoT network.
2. Domain names’ "white" and "black" lists checking.
3. DNS traffic features extraction that may indicate the malicious botnets activity in
the IoT network.
4. Feature vectors analysis.
5. Localization and blocking of the infected IoT devices.</p>
      <p>Let us present the IoT botnets detection process of based on the DNS traffic analysis
as a tuple</p>
      <p>M BN</p>
      <p>=A, C, B, Ψ, Z , L, F , χ T ,ϑ1T ,ϑ2T , ϒT ,ϑ3T ,T , where
C = {c j }Nj=C1 - a set of botnet’s elements, N C - the number of botnet’s elements;
3  p NB
A = {a j } j=1 - IoT botnet architecture type; B = b 
 j  j=1
used to manage the IoT botnet, N B - number of network protocols, p ∈ P,
P={1.65535} - a set of ports used for the IoT botnet management; Ψ = {ψ }
4
j j=1 - a
set of evasion techniques of IoT botnet based on DNS; Z = {z j } Nj=Z1 - a set of IoT
devices infected by botnet, N Z - a number of infected IoT devices; L = {l }
5
j j=1 - a
set of botnet’s life cycle stages; l1 - infection; l2 - initial registration or connection;
l3 - implementation of the malicious activity; l4 - technical support; l5 - termination
- a set of network protocols
of the botnet; stages l2 - l4 occur with the involvement of DNS; F = {f j }Nj=F1 - the set
of bot functions of the IoT botnet, determined by the corresponding botnet’s life cycle
stage, N F - the number of bot functions of the botnet IoT; IoT device infection
function l1 ⇒ Υ  f1→{hinf hinf ∈ H } , where Y - a set of botnet’s malicious actions,
H - a set of infected IoT devices in the network, hinf - an infected IoT device; the
connecting function of the infected IoT device to botnet
l2 ⇒ Z ∪ {hinf hinf ∈ H }  f2 → Z ′ ; IoT botnet upgrade function to a new version
l3 ⇒ z × z′ f3 → z′ ;
the
set
of
botnet’s
malicious
commands
l4 ⇒ Z ×{ p p ∈ P}  f4 → Υ , where P - a set of commands that can be executed
by bots of the IoT botnet; the deactivation function of the IoT botnet
l5 ⇒ Z \ {z z ∈ Z}  f5 → Z ′ ; χT - the set of captured incoming DNS messages
addressed to the set of network IoT devices H; ϑ1T - a function of domain names
comparison with the "white" and "black" lists; ϑ2T - a function of the feature
extraction from incoming DNS traffic, indicating the presence of malicious activity of the
IoT botnets; ϒT - a set of IoT botnets’ detecting algorithms based on the DNS traffic
analysis; ϑ T
3 - the localization function of infected IoT devices, and blocking the</p>
      <p>N
bots’ actions; T = {tm}mT=0 - the observation time interval, where NT - the number of
iterations of the observation.</p>
      <p>Let present the command and control elements of an IoT botnet as
C ={cj } Nj=C1 ={D, I , N , E }NC , where D = {d j }Nj=D1 , I = {i j }Nj=I1 - a set of
j j=1
domain names and IP addresses of IoT botnet control elements for d; N = {n }NN ,
j j=1
E = {e j }Nj=E1 - a set of domain names and IP addresses of authority name servers for
d ; N D - a number of domain names corresponding to the controlling elements of
the IoT botnet; N I - the number of IPs mapped to domain names; N N - the number
of domain names of authority name servers; N Е - the number of IP addresses of
authority name servers.</p>
      <p>Let's present the type of IoT botnet architecture as A = {a j }3j=1 , where a1 -
centralized, a2 - distributed, a3 - hybrid.</p>
      <p>Let us consider the steps of the method in more detail.
3.1</p>
      <sec id="sec-4-1">
        <title>Gathering the Incoming DNS Traffic of the IoT Network</title>
        <p>Let us represent DNS traffic as a tuple χ N = χ , Н , S , D , where χ - the set of
DNS messages sent from and to the set IoT network devices H, χ =χ O ∪ χ I ,
where χO - a set of outcoming DNS messages, χI - a set of incoming DNS
messages; S - a set of DNS servers, S =S L ∪ S N , where S L - a set of local DNS
servers, S N - a set of non-local DNS servers; D - the set of requested domain names by
IoT devices, D = {di}iN=D1 , where N D - number of different domain names.</p>
        <p>Let us present a set of IoT devices that have made DNS requests as
dND NTTL
H =   H j,k , where H j - a subsets of MAC addresses of IoT devices that have
j =d1 k =1
sent DNS requests for a specific domain name; H j,k - subsets of MAC addresses of
IoT network devices that have sent DNS requests to a specific domain name within a
specific TTL period; NTTL - the total number of such subsets; H j,k = {h j,k ,i i=1
}NH , j,k ,
where h j,k ,i - MAC address of a specific IoT network device; N H , j,k - the number
of network IoT devices that have sent DNS requests within a specific TTL period.
dND NTTL
Let us present the set of captured DNS messages as χ T =   χ j,k , where
j=d1 k =1
χ j - subsets of incoming DNS messages for a specific domain name; χ j,k - subsets
of incoming DNS messages for a specific domain name captured within a specific
TTL period; χ j,k = {χ j,k,i }iN=χ1, j,k , where χ j,k ,i - DNS message captured within a
TTL period, Nχ, j,k - the number of DNS messages captured within a TTL period.</p>
        <p>
          Employing the incoming DNS message structure [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ], let us present the captured
DNS response for a specific domain name as a tuple
χ
j,k,i = χ j,k,i,H , χ j,k,i,TS , χ j,k,i,IP , χ j,k,i,HD ,χ j,k,i, ANS ,χ j,k,i, ATH ,χ j,k,i, ADD
j =1,..., d dND , k =1,NTTL , i =1,Nχ , j,k , where χ j,k,i,H - MAC address of the IoT
device that perform the DNS request; χ
- a time stampt of DNS packet;
j,k ,i,TS
χ j,k,i,IP - DNS packet source IP address; χ j,k,i,HD ,χ j,k,i,ANS ,χ j,k,i,ATH ,χ j,k,i,ADD
DNS message sections: Header, Answer, Authority, and Additional respectively.
        </p>
        <p>The DNS message header can be presented as follows:
j,k ,i,HD,ID
(ID field); χ
code;
χ</p>
        <p>j,k ,i,HD,OPC
j,k ,i,HD,QDC
, χ</p>
        <p>,χ
j,k,i,HD
j,k,i,HD,ID
j,k,i,HD,OPC
j,k,i,HD,RC
j,k,i,HD,QDC
j,k,i,HD, ANC
= χ
,χ
,χ
,χ
,χ
,χ
j,k,i,HD,NSC
j,k,i,HD, ARC
, j
=1,..., d d ND , k
=1,NTTL , i
=1,Nχ , j,k ,
where
- an identifier that allows associating a DNS request with DNS response
- a request type (OPCODE field); χ
j,k ,i,HD,RC
- response
number
of
entries
in
the
query
section;
χ
χ
χ
χ
χ
j
χ
χ
= (χ


j,k ,i,HD,ANC j,k ,i,HD,NSC j,k ,i,HD,ARC
header, nameservers and additional information sections (fields ANCOUNT,
NSCOUNT, ARCOUNT), respectively.</p>
        <p>The Answer, Authority, and Additional sections have the same format and can be
described as a set of the resource records as follows:
- the number of resource records in the
j,k ,i,S
j,k ,i,S ,NM
j,k ,i,S ,TP
j,k,i,S ,TTL</p>
        <p>j,k,i,S ,RDL
, χ
, χ
, χ
, χ
=1,..., d d ND , k
=1,NTTL , i
=1,Nχ , j,k ,
where</p>
        <p>S ∈ { " ANS "," ATH "," ADD " } ,
j,k ,i,S ,NM
j,k,i,S ,RDL
- NAME field; χ
- RDATA field length; χ
j,k,i,S ,TP
- TYPE field; χ</p>
        <p>j,k ,i,S ,TTL
j,k,i,S ,RDT
- RDATA field value; N RR,S - the
number
χ
of
, χ
resource</p>
        <p>records
,χ
j,k,i,HD, ANC
j,k,i,HD,NSC
j,k,i,HD, ARC
in the section
for the relevant section).</p>
        <p>j,k,i,S ,RDT n n=1</p>
        <p>) NRR,S
- TTL field;
(equal
to
3.2</p>
      </sec>
      <sec id="sec-4-2">
        <title>Usage of "white" and "black" Domain Names Lists</title>
        <p>In order to detect DNS requests to known domain names of the IoT botnets and to
reject legitimate DNS requests, the requested domain names of the IoT devices are
compared with "white" and "black" domain names lists.
3.3</p>
      </sec>
      <sec id="sec-4-3">
        <title>IoT malicious traffic extraction</title>
        <p>At this stage, the inbound DNS messages are to be analyzed, and the features that may
indicate the malicious IoT botnets activity are to be extracted.
4</p>
        <p>Let us define a set of IoT botnets evasion techniques as Ψ ={ψ j } j=1 , where ψ1
cycling of IP mapping, ψ 2 – domain flux, ψ 3 - fast flux, ψ 4 - DNS tunneling.</p>
        <p>If IoT botnet uses cycling of IP mapping C&amp;C server с ∈ C periodically changes
its location, and the domain name d is associated with the C&amp;C server is mapped to
the some IP address from the set i ∈ I , d → {i1,..., in} . Botnet’s architecture type is
centralized, ψ 1 ⇒ a1 .</p>
        <p>Let us define a set of features that indicate the usage cycling of IP mapping
technique by IoT botnet as GΨ1 = {tmod ,tmed ,taver , nIP , sIP} , where tmod - tmed taver
- TTL-period (mode, median, average respectively ); nIP and sIP - the number of IPs
and the average distance between IPs associated with the domain name respectively.</p>
        <p>When IoT botnet uses domain flux technique, the C&amp;C server c ∈ C periodically
migrates to the new domain names from a list formed using the domain name
generation algorithm (DGA). Thus, within specified TTL period a new name d ∈ D may
correspond to IP address of the C&amp;C server i ∈ I , {i} → {d1,..., dn} . If the C&amp;C
server also changes location, then {i1,..., in} → {d1,..., dm} . Botnet architecture type is
centralized, ψ 2 ⇒ a1 .</p>
        <p>Let us define a set of features that indicate the use of "domain flux" evasion
technique as GΨ2 = {tmod ,tmed ,taver , fs , nD} , where fs - binary sign of success of
DNS request; nD - the number of domain names with shared IP addresses.</p>
        <p>Within the time interval defined by the TTL DNS period, a single-flux network
domain name d, which is used to connect with the infected IoT devices to control
elements {c1,..., cn} , is mapped to a new set of IPs. These IPs are changing cyclically
d → {i1,..., in} . Also, the IP addresses are geographically distributed by the infected
botnet’s nodes that redirect traffic to the control elements
{с1,..., сn} :={x|x ∈ Z ∧ x ∈ С} . For the double-flux network the domain name of each
authority name server n is matched to a subset of cyclically changing IPs
d → {i1,..., in} , n → {e1,..., em} . These IPs are also the IP addresses of the
geographically distributed infected botnet’s nodes, i.e. {n1,..., nm} :={x|x ∈ Z ∧ x ∈ N} . As the
number of name servers for such botnets is usually more than one, then
{n1,..., nm} → {e1,..., en} . Botnet’s architecture type is distributed,ψ 3 ⇒ a2 .</p>
        <p>Let us define the set of features that indicate the usage fast-flux technique
changing as GΨ3 = {tmod ,tmed ,taver , nA , sA , nUA , sUA} , where nA - the number of
Arecords corresponding to the domain name in the incoming DNS message; sA , nUA
and sUA - the average distance between IPs, the number of unique IPs and the average
distance between unique IPs in multiple A-records corresponding to a domain name
in incoming DNS messages respectively.</p>
        <p>Attacker uses the DNS tunneling to transmit C&amp;C traffic to a fake DNS server. It
enables the possibility of the IoT infected devices to send the encrypted messages to
the attacker’s server and receive the commands from him. In this case, the set of
domain names D actually is an analogue of the domain names of the C&amp;C server of the
IoT botnet. IP address e of the fake DNS server usually stays stable, that is
{d1,..., dn} → e . Type of botnet architecture - centralized or hybrid,ψ 4 ⇒ a1 ∨ a3 .</p>
        <p>Let us define a set of features of DNS tunneling as GΨ4 = {lN , nU , eN , eR, fUR ,lP} ,
where lN - a length of the domain name; nU - a number of unique characters in the
domain name; eN - a domain name entropy; eR - a maximum entropy value of DNS
resource records contained in DNS messages; fUR - a sign of a rare DNS records
usage; lP - an average size of DNS messages for a domain name.</p>
        <p>Let us define a set of features that can obtained by the usage of the active DNS
probing as GΨ = {nNS , sNS , vretry , nASN , nASA} , where nNS - the number of NS
records in the DNS response; sNS - the average distance between IPs for multiple NS
records for a domain name; vretry - the value of the retry field obtained in the DNS
response of the SOA request; nASN - the number of different ASNs for name servers’
IPs; nASA - the number of different ASNs for domain name.</p>
        <p>From these features extracted from the incoming DNS traffic, feature vectors are
generated for each domain name requested by the network IoT devices:
Wd = {tmod , tmed , taver , nIP , sIP , nA , sA , nUA , sUA , lN , nU , eN , eR, fUR , lP , fs , nD } .
(1)
3.4</p>
      </sec>
      <sec id="sec-4-4">
        <title>The Feature Vectors Analysis</title>
        <p>The feature vectors obtained after the feature gathering and extraction are to be
assigned to specified classes. The results of classification are the memberships of the
feature vectors to IoT botnet malicious classes or benign class of uninfected IoT
devices. The task of classification can be described as a function fclassifier : Wd → ς ,
where fclassifier - a classification function, ς - IoT botnet malicious class or benign
class of uninfected IoT devices.
3.5</p>
      </sec>
      <sec id="sec-4-5">
        <title>Localization and Block of the Infected IoT Devices</title>
        <p>Localization and blocking of IoT devices infected with botnets is performed based on
the log files analysis that contain lists of domain names requested by IoT devices of
the network and MAC addresses of these devices.
4</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Experiments</title>
      <p>
        In order to determine the efficiency of the proposed technique a number of
experiments were carried out. As the classification algorithms a semi-supervised fuzzy
cmeans clustering [
        <xref ref-type="bibr" rid="ref15 ref16 ref17">15-17</xref>
        ], Support Vector Machine (SVM) [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ], Artificial Immune
System (AIS) [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] classification algorithms were used. For the purpose of training the
classifiers 16804 samples of the labeled DNS data of the real modern normal traffic
and synthetic contemporary IoT botnet attack traffic of two data set were used:
BoTIoT dataset [
        <xref ref-type="bibr" rid="ref20 ref21">20, 21</xref>
        ] and the UNSW-NB15 dataset [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ].
      </p>
      <p>
        In order to compare the effectiveness of the classification algorithms the test
samples of IoT malware infections and IoT benign traffic from IoT-23 dataset [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ] were
employed. The test data contains 32 415 samples of IoT DNS traffic. 15611 DNS
samples of them were the samples of DNS traffic flows of different version’s IoT
botnets, in particular such as Mirai, Torii, IoT Trojan, Kenjiro, Okiru, Haji me and
other [
        <xref ref-type="bibr" rid="ref24 ref25 ref26 ref27">24, 25, 26, 27</xref>
        ]. Also test data contains 16804 samples of uninfected IoT
devices.
      </p>
      <p>Test result of experiments are presented in the Table 1.</p>
      <p>Number of Semi-supervised fuzzy c- Support Vector
MamaDliNciSous means clustering chine
samples</p>
      <sec id="sec-5-1">
        <title>Artificial Immune System</title>
      </sec>
      <sec id="sec-5-2">
        <title>Botnet`s name</title>
      </sec>
      <sec id="sec-5-3">
        <title>Mirai</title>
      </sec>
      <sec id="sec-5-4">
        <title>Linux Mirai</title>
      </sec>
      <sec id="sec-5-5">
        <title>Torii</title>
      </sec>
      <sec id="sec-5-6">
        <title>IoT Trojan</title>
      </sec>
      <sec id="sec-5-7">
        <title>Kenjiro</title>
      </sec>
      <sec id="sec-5-8">
        <title>Okiru</title>
        <p>IRC Bot
Linux
Hajime
Muhstik</p>
      </sec>
      <sec id="sec-5-9">
        <title>Hide&amp;Seek Total 2308 1795</title>
        <p>1386
1762
1822
1080
1521
1162
1284
1491</p>
        <p>TP
2195
1709
1318
1674
1694
961
1427
1106
1217
1405</p>
        <p>FP
94
74
32
64
35
46
49
47
34
52</p>
        <p>TP
2236
1741
1331
1711
1771
1051
1478
1118
1258
1449</p>
        <p>FP
52
49
24
29
3
8
32
17
16
26</p>
        <p>TP
2213
1691
1321
1676
1729
1036
1427
1112
1226
1430</p>
        <p>FP
81
50
34
32
2
12
24
18
15
54
15611</p>
        <p>14706/94,2% 527/3,14% 15144/97% 256/1,5% 14861/95,19% 322/1,9%</p>
        <p>The experimental results show that usage of the SVM demonstrated better results
than the other two methods. The effectiveness of the method involving SVM is in the
range of 96,06 to 98,01% with the false positives in the range of 0,015 to 0,31%.
Involving of AIS demonstrated effectiveness in the range of 93,8 to 95,9% with the
false positives in the range of 0,01 to 0,48%. And the worst results were shown by
involving semi-supervised fuzzy c-means clustering - in the range of 89 to 95,2%
with false positives in the range of 0,19 to 0,56%.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Conclusion</title>
      <p>The new technique for IoT cyberattacks detection based on DNS traffic analysis is
presented. The method allows detecting IoT botnet cyberattacks. The method has the
heuristic and proactive nature. It is based on the gathering of the set of features that
may indicate the IoT cyberattacks presence.</p>
      <p>The mechanism of attack detection system is based on the cyberattacks’ features
gathering from network and feature vectors construction.</p>
      <p>As the classification algorithms a semi-supervised fuzzy c-means clustering, SVM
and Artificial Immune System classification algorithms were employed. The proposed
method has demonstrated the ability to detect unknown IoT cyberattacks with high
efficiency in the range of 96,06 to 98,01% with the false positives in the range of
0,015 to 0,31%.</p>
      <p>The further work may be devoted to the development of the techniques that
involve machine learning algorithms and new IoT attacks’ features analysis.
6</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Vignau</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khoury</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Hallé</surname>
            ,
            <given-names>S. 10</given-names>
          </string-name>
          <article-title>Years of IoT Malware: a Feature-Based Taxonomy</article-title>
          .
          <source>In 2019 IEEE 19th International Conference on Software Quality</source>
          , Reliability and Security
          <string-name>
            <surname>Companion (QRS-C)</surname>
          </string-name>
          , pp.
          <fpage>458</fpage>
          -
          <lpage>465</lpage>
          , IEEE (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Murphy</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>The Internet of Things and the threat it poses to DNS</article-title>
          . Network Security,
          <year>2017</year>
          .7, pp.
          <fpage>17</fpage>
          -
          <lpage>19</lpage>
          (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Angrishi</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <article-title>Turning internet of things (iot) into internet of vulnerabilities (iov): Iot botnets</article-title>
          .
          <source>arXiv preprint arXiv:1702.03681</source>
          (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Alieyan</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Almomani</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abdullah</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Almutairi</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Alauthman</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>Botnet and Internet of Things (IoTs): A Definition, Taxonomy, Challenges, and Future Directions</article-title>
          . In Security, Privacy, and
          <article-title>Forensics Issues in Big Data</article-title>
          ,
          <source>IGI Global</source>
          , pp.
          <fpage>304</fpage>
          -
          <lpage>316</lpage>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jin</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>J. H.</given-names>
          </string-name>
          <article-title>Analysis of Botnet Domain Names for IoT Cybersecurity</article-title>
          .
          <source>IEEE Access</source>
          ,
          <volume>7</volume>
          ,
          <fpage>94658</fpage>
          -
          <lpage>94665</lpage>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>McDermott</surname>
            ,
            <given-names>C. D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Majdani</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petrovski</surname>
            ,
            <given-names>A. V.</given-names>
          </string-name>
          <article-title>Botnet detection in the internet of things using deep learning approaches</article-title>
          .
          <source>In 2018 international joint conference on neural networks (IJCNN)</source>
          , IEEE, pp.
          <fpage>1</fpage>
          -
          <lpage>8</lpage>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>De Donno</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dragoni</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giaretta</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spognardi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <article-title>DDoS-capable IoT malwares: Comparative analysis and Mirai investigation</article-title>
          .
          <source>Security and Communication Networks</source>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Doshi</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Apthorpe</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Feamster</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <article-title>Machine learning ddos detection for consumer internet of things devices</article-title>
          .
          <source>In 2018 IEEE Security and Privacy Workshops (SPW)</source>
          , IEEE, pp.
          <fpage>29</fpage>
          -
          <lpage>35</lpage>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Moustafa</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Turnbull</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Choo</surname>
            ,
            <given-names>K. K. R.</given-names>
          </string-name>
          <article-title>An ensemble intrusion detection technique based on proposed statistical flow features for protecting network traffic of internet of things</article-title>
          .
          <source>IEEE Internet of Things Journal</source>
          ,
          <volume>6</volume>
          (
          <issue>3</issue>
          ),
          <fpage>4815</fpage>
          -
          <lpage>4830</lpage>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Al-Duwairi</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Al-Kahla</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          , AlRefai,
          <string-name>
            <given-names>M. A.</given-names>
            ,
            <surname>Abdelqader</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            ,
            <surname>Rawash</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            , &amp;
            <surname>Fahmawi</surname>
          </string-name>
          ,
          <string-name>
            <surname>R.</surname>
          </string-name>
          <article-title>SIEM-based detection and mitigation of IoT-botnet DDoS attacks</article-title>
          .
          <source>International Journal of Electrical &amp; Computer Engineering (2088-8708)</source>
          ,
          <volume>10</volume>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11. Al Shorman,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Faris</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            ,
            <surname>Aljarah</surname>
          </string-name>
          ,
          <string-name>
            <surname>I.</surname>
          </string-name>
          <article-title>Unsupervised intelligent system based on one class support vector machine and Grey Wolf optimization for IoT botnet detection</article-title>
          .
          <source>Journal of Ambient Intelligence and Humanized Computing</source>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>17</lpage>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Alrashdi</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alqazzaz</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aloufi</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alharthi</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zohdy</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ming</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <article-title>AD-IoT: anomaly detection of IoT cyberattacks in smart city using machine learning</article-title>
          .
          <source>In 2019 IEEE 9th Annual Computing and Communication Workshop and Conference</source>
          , pp.
          <fpage>0305</fpage>
          -
          <lpage>0310</lpage>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Cvitić</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peraković</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Periša</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Botica</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>Novel approach for detection of IoT generated DDoS traffic</article-title>
          .
          <source>Wireless Networks</source>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>14</lpage>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. Mockapetris P. RFC-
          <volume>1035</volume>
          . Domain names
          <article-title>- implementation and specification</article-title>
          .
          <source>ISI</source>
          ,
          <year>1987</year>
          . Available online: http://www.ietf.org/rfc/rfc1035.txt?
          <source>number=1035 (аccessed on March 20</source>
          ,
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Pomorova</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savenko</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lysenko</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kryshchuk</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bobrovnikova</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <article-title>A technique for the botnet detection based on DNS-traffic analysis</article-title>
          .
          <source>Communications in Computer and Information Science</source>
          , Vol.
          <volume>522</volume>
          , pp.
          <fpage>127</fpage>
          -
          <lpage>138</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Lysenko</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bobrovnikova</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savenko</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          <article-title>A botnet detection approach based on the clonal selection algorithm</article-title>
          .
          <source>The 2018 IEEE 9th International Conference on Dependable Systems, Services and Technologies: Proceedings</source>
          . Vol.
          <volume>1</volume>
          , pp.
          <fpage>424</fpage>
          -
          <lpage>428</lpage>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Lysenko</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savenko</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kryshchuk</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klyots</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <article-title>Botnet detection technique for corporate area network</article-title>
          .
          <source>The IEEE 7th International Conference on Intelligent Data Acquisition and Advanced Computing Systems: Proceedings</source>
          , Berlin. Vol.
          <volume>1</volume>
          , pp.
          <fpage>315</fpage>
          -
          <lpage>320</lpage>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Lysenko</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bobrovnikova</surname>
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savenko</surname>
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kryshchuk</surname>
            <given-names>A</given-names>
          </string-name>
          .
          <article-title>BotGRABBER: SVM-based self-adaptive system for the network resilience against the botnets' cyberattacks</article-title>
          .
          <source>Communications in computer and information science</source>
          , pp.
          <fpage>127</fpage>
          -
          <lpage>143</lpage>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Lysenko</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savenko</surname>
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bobrovnikova</surname>
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kryshchuk</surname>
            <given-names>A</given-names>
          </string-name>
          .
          <article-title>Self-adaptive system for the corporate area network resilience in the presence of botnet cyberattacks</article-title>
          .
          <source>Communications in computer and information science</source>
          , pp.
          <fpage>385</fpage>
          -
          <lpage>401</lpage>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>The BoT-IoT Dataset</surname>
          </string-name>
          . Available online: https://www.unsw.adfa.edu.au/unsw-canberracyber/cybersecurity/ADFA-NB15-Datasets/bot_iot.
          <source>php (аccessed on March 20</source>
          ,
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Koroniotis</surname>
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moustafa</surname>
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sitnikova</surname>
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Turnbull</surname>
            <given-names>B</given-names>
          </string-name>
          .
          <article-title>Towards the Development of Realistic Botnet Dataset in the Internet of Things for Network Forensic Analytics: Bot-IoT Dataset”</article-title>
          , https://arxiv.org/abs/
          <year>1811</year>
          .00701 (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>The</surname>
            <given-names>UNSW-NB15</given-names>
          </string-name>
          <string-name>
            <surname>Dataset</surname>
          </string-name>
          . Available online: https://www.unsw.adfa.edu.au/unswcanberra-cyber/cybersecurity/ADFA-NB15-Datasets
          <source>/ (аccessed on March 20</source>
          ,
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23. Stratosphere Laboratory. Aposemat IoT-23.
          <article-title>A labeled dataset with malicious and benign IoT network traffic</article-title>
          . Parmisano,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Garcia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Erquiaga</surname>
          </string-name>
          , M. J. Available online: https://www.stratosphereips.org/datasets-iot23
          <source>(аccessed on March 20</source>
          ,
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Securelist</surname>
          </string-name>
          .
          <article-title>New trends in the world of IoT threats</article-title>
          . Available online: https://securelist.com
          <article-title>/new-trends-in-the-world-of-iot-</article-title>
          <source>threats/87991/ (аccessed on March 20</source>
          ,
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Cloudflare</surname>
          </string-name>
          . What is the Mirai Botnet? Available online: https://www.cloudflare.com/learning/ddos/glossary/mirai-botnet
          <source>/ (аccess.March</source>
          <volume>20</volume>
          ,
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Kharchenko</surname>
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kondratenko</surname>
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kacprzyk</surname>
            <given-names>J</given-names>
          </string-name>
          . (eds).
          <article-title>Concepts of Green IT Engineering: Taxonomy, Principles and Implementation</article-title>
          . Green IT Engineering: Concepts,
          <source>Models, Complex Systems Architectures. Studies in Systems, Decision and Control</source>
          , Springer, Cham,
          <year>2017</year>
          , Vol.
          <volume>74</volume>
          . pp.
          <fpage>3</fpage>
          -
          <lpage>19</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Singh</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Singh Dhindsa</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Bhushan</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          (
          <year>2018</year>
          ).
          <article-title>Performance analysis of agent based distributed defense mechanisms against ddos attacks</article-title>
          .
          <source>International Journal of Computing</source>
          ,
          <volume>17</volume>
          (
          <issue>1</issue>
          ),
          <fpage>15</fpage>
          -
          <lpage>24</lpage>
          . Retrieved from http://computingonline.net/computing/article/view/945.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>