<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Detection and classification of DDoS flooding attacks by machine learning method</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Dmytro</forename><surname>Tymoshchuk</surname></persName>
							<email>dmytro.tymoshchuk@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Ternopil Ivan Puluj National Technical University</orgName>
								<address>
									<addrLine>Ruska str. 56</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Oleh</forename><surname>Yasniy</surname></persName>
							<email>oleh.yasniy@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Ternopil Ivan Puluj National Technical University</orgName>
								<address>
									<addrLine>Ruska str. 56</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Mykola</forename><surname>Mytnyk</surname></persName>
							<email>mytnyk@networkacad.net</email>
							<affiliation key="aff0">
								<orgName type="institution">Ternopil Ivan Puluj National Technical University</orgName>
								<address>
									<addrLine>Ruska str. 56</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Nataliya</forename><surname>Zagorodna</surname></persName>
							<email>zagorodna.n@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Ternopil Ivan Puluj National Technical University</orgName>
								<address>
									<addrLine>Ruska str. 56</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Vitaliy</forename><surname>Tymoshchuk</surname></persName>
							<email>tymoshchuk@tntu.edu.ua</email>
							<affiliation key="aff0">
								<orgName type="institution">Ternopil Ivan Puluj National Technical University</orgName>
								<address>
									<addrLine>Ruska str. 56</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Detection and classification of DDoS flooding attacks by machine learning method</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">D60BB885F8D3F269F31408A88182E199</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T20:12+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>machine learning, neural network, DDoS, flooding 1 (V. Tymoshchuk) 0000-0003-0246-2236 (D. Tymoshchuk)</term>
					<term>0000-0002-9820-9093 (O. Yasniy)</term>
					<term>0000-0003-3743-6310 (M. Mytnyk)</term>
					<term>0000-0002-1808-835X (N. Zagorodna)</term>
					<term>0009-0007-2858-9434 (V. Tymoshchuk)</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This study focuses on a method for detecting and classifying distributed denial of service (DDoS) attacks, such as SYN Flooding, ACK Flooding, HTTP Flooding, and UDP Flooding, using neural networks. Machine learning, particularly neural networks, is highly effective in detecting malicious traffic. A dataset containing normal traffic and various DDoS attacks was used to train a neural network model with a 24-106-5 architecture. The model achieved high Accuracy (99.35%), Precision (99.32%), Recall (99.54%), and F-score (0.99) in the classification task. All major attack types were correctly identified. The model was also further tested in the lab using virtual infrastructures to generate normal and DDoS traffic. The results showed that the model can accurately classify attacks under near-realworld conditions, demonstrating 95.05% accuracy and balanced F-score scores for all attack types. This confirms that neural networks are an effective tool for detecting DDoS attacks in modern information security systems.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>Distributed denial of service (DDoS) attacks are one of the most serious threats to network security. These attacks cause significant system disruptions by flooding the system with malicious traffic <ref type="bibr" target="#b0">[1]</ref>. Among the various DDoS techniques, Flooding attacks, such as SYN Flooding, ACK Flooding, HTTP Flooding, and UDP Flooding, are particularly difficult to neutralise due to their ability to mimic legitimate traffic. These attacks drain server resources, making it unavailable to legitimate users.</p><p>Machine learning (ML) is one of the key technologies increasingly being implemented in various fields of science and technology due to its ability to automate processes, analyze large amounts of data, and make highly accurate predictions. In medicine, ML is used to diagnose diseases, analyze medical images, develop personalized treatment plans, and predict the 1 spread of infectious diseases <ref type="bibr" target="#b1">[2]</ref>. In the financial sector, machine learning allows for assessing credit risk, detecting fraud, optimizing investment portfolios, and automating trading algorithms <ref type="bibr" target="#b2">[3]</ref>. In the automotive industry, ML underpins the development of autonomous vehicles that analyze sensor data to make real-time decisions and predict vehicle maintenance <ref type="bibr" target="#b3">[4]</ref>. In materials science, machine learning allows predicting material properties <ref type="bibr" target="#b4">[5,</ref><ref type="bibr" target="#b5">6,</ref><ref type="bibr" target="#b6">7]</ref>. In particular, ML minimizes the need for expensive and time-consuming experiments.</p><p>In cybersecurity, machine learning has become an important tool for detecting and preventing various threats. Traditional methods, such as rule-based and statistical approaches, often cannot detect sophisticated attacks. ML allows for more efficient analysis of network traffic, detection of anomalies, and classification of malicious traffic, making these methods indispensable for modern information security systems <ref type="bibr" target="#b7">[8,</ref><ref type="bibr" target="#b8">9]</ref>. Neural networks are a subset of machine learning techniques known for their ability to detect complex nonlinear relationships.</p><p>The aim of this study is to develop and evaluate an effective neural network for DDoS detection and classification. A dataset containing normal traffic and traffic from different Flooding attacks (SYN, ACK, HTTP, and UDP Flooding) was used to train and evaluate the neural network model. The main stages of this work include the development of a robust neural network model for DDoS detection, analyzing its performance for different types of attacks, and practical testing of the neural network performance on traffic generated in a laboratory environment under conditions close to real-world conditions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Methods</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1.">Dataset description</head><p>The dataset used in this study is specifically designed to detect DDoS flooding attacks and is obtained from <ref type="bibr" target="#b9">[10,</ref><ref type="bibr" target="#b11">11]</ref>. It includes two categories of traffic: normal traffic, which represents legitimate user activity, and malicious traffic generated by different Flooding attacks.</p><p>Normal traffic is network traffic that does not contain malicious activity and corresponds to the standard behavior of users and devices on the network. Such traffic includes legitimate requests, data transfers between users and servers, and other typical network operations that occur during the normal operation of network systems. In the context of DDoS detection, normal traffic is a benchmark for comparison with abnormal traffic that may indicate an attack.</p><p>SYN Flooding is a type of DDoS attack aimed at exhausting the resources of a server or network device's resources by sending many requests to establish a TCP connection <ref type="bibr" target="#b12">[12]</ref>. Under normal conditions, a TCP connection is established through a three-step process where the client sends a SYN packet to the server; after that, the server responds with a SYN-ACK, and the client completes the process by sending an ACK packet. However, in a SYN Flooding attack, the attacker sends many SYN packets (in many cases from a spoofed IP address) but does not respond to the SYN-ACK packets the server receives in return. This causes the server to keep half-open connections, wasting its resources on maintaining them. As a result, the server becomes overloaded and unable to process new legitimate connection requests, resulting in a denial of service for legitimate users. SYN Flooding is one of the most common and difficult attacks to detect because its packets look like legitimate requests.</p><p>ACK Flooding is a DDoS attack that uses many ACK packets to overload the target system <ref type="bibr" target="#b13">[13]</ref>. ACK packets are part of the normal data transfer process in the TCP protocol and acknowledge receipt of a data packet from the sender. In a typical scenario, after data is transmitted between two devices, the receiver sends an ACK packet to the sender to confirm that the data was successfully received. In the case of ACK Flooding, an attacker sends many ACK packets to the target server or network device. These packets do not correspond to the connection or previously transmitted data. The attack aims to overwhelm the server by processing many invalid ACK packets, thereby depleting its resources, such as CPU time and memory. Due to the constant flow of ACK packets, the server is forced to spend significant resources on processing them, which can lead to a decrease in performance or a complete cessation of service to legitimate users. Like other DDoS attacks, ACK Flooding is difficult to detect because individual ACK packets are not malicious and look like normal traffic. However, their massive number and the lack of a suitable connection make the attack effective and lead to server overload.</p><p>HTTP Flooding is a DDoS attack that aims to exhaust web server resources by sending many HTTP requests <ref type="bibr" target="#b14">[14]</ref>. In this case, attackers use the HTTP protocol to communicate between web browsers and servers to overload the target website or web application. In HTTP Flooding, attackers send requests that mimic legitimate web traffic to the target server. These requests can be for various website resources, such as HTML pages, images, or other media files. The attack aims to consume available server resources, such as network bandwidth, CPU time, and RAM. HTTP Flooding can significantly impact a website or web application, especially if the attack is large-scale. Due to the heavy load, the server can slow down or even stop functioning completely, making the website inaccessible to legitimate users. Since HTTP Flooding uses normal web traffic, it is difficult to distinguish it from legitimate requests, making it difficult to recognize and block the attack.</p><p>UDP Flooding is a DDoS attack that uses many UDP packets to overload a target server or network device <ref type="bibr" target="#b15">[15]</ref>. UDP (User Datagram Protocol) is a data transmission protocol that does not check packet delivery and does not establish a connection before sending data. In the case of UDP Flooding, attackers send many UDP packets to random ports on the target server or network device. When the server receives these packets, it tries to process them, including checking the incoming data and attempting to respond to requests if necessary. As a result, the server spends resources processing and responding to large volumes of spoofed requests. This leads to an overload of its network bandwidth and CPU resources, which can significantly slow down or stop the server's normal operation. UDP Flooding can also affect the network infrastructure by flooding communication channels with large data. Like other DDoS attacks, UDP Flooding can be difficult to detect and block because UDP packets are not malicious, and the attack uses a legitimate network protocol.</p><p>The dataset has already been pre-processed to make it suitable for neural network training. The dataset is divided into three parts to train the neural network: training, test, and validation samples. The total sample size was 38413. Of these, 16619 records were normal traffic, 3556 were SYN Flooding, 7562 were ACK Flooding, 1044 were HTTP Flooding, and 9632 were UDP Flooding.</p><p>To ensure effective training and evaluation of the model, 70% of the data were randomly selected for the training set, the largest share of the data. This part was used to train the model, i.e. to adjust its parameters based on the available data. The validation sample comprised 15% of the total data. It was used to check the quality of the model and the settings of its hyperparameters. This allowed us to avoid overfitting, i.e. a situation where the model works well on training data but performs poorly on new, unknown data. The remaining 15% of the data was reserved for the test sample, which was used after the model was trained. Testing allowed us to evaluate the final performance of the model on new data that was not involved in the training or validation process. It allowed us to determine its generalization capability.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2.">Neural network model</head><p>A neuron in neural networks is the basic element that mimics the behaviour of a biological neuron. Its main function is to receive signals at the input, process them, and transmit the results to the output. The mathematical model of the neuron is described by the following equation <ref type="bibr" target="#b16">[16]</ref>: In this paper, a neural network with the 24-106-5 architecture is built. Figure <ref type="figure" target="#fig_0">1</ref> shows the architecture of a multilayer perceptron with one hidden layer and one output layer. A neural network consists of three layers. The input layer contains 24 nodes, corresponding to the number of features in the input data; each neuron receives values from the data set and passes them on to the next layer. The hidden layer comprises 106 neurons activated using the tanh (hyperbolic tangent) activation function. The function is described as:</p><formula xml:id="formula_0">y= ( ∑ i=1 n ❑ i • x i +b ) ,</formula><formula xml:id="formula_1">tanh ( x )= e x −e −x e x +e −x , (<label>2</label></formula><formula xml:id="formula_2">)</formula><p>where x is an input value or a weighted sum of input signals for a particular neuron, e is a mathematical constant known as the Euler number.</p><p>The tanh function maps input values into a range from -1 to 1, which allows the model to learn more efficiently as it reduces the problem of vanishing gradients compared to other activation functions. The output layer contains 5 neurons, corresponding to the number of classes in the classification task, including normal traffic and four types of DDoS Flooding attacks. To activate the neurons in this layer, we used the softmax activation function. The function is described as:</p><formula xml:id="formula_3">( z i )= e z i ∑ j=1 n e z j ,<label>(3)</label></formula><p>where z i is a real number that reflects the 'strength' of the signal for class i before applying softmax, i is a fixed index for calculating the probability of a particular class, n defines the number of possible categories for classification. This function maps the neurons' output values into probabilities belonging to each class, where the sum of probabilities for all classes is 1. This allows the model to provide probabilities for each possible outcome, which is convenient for the classification task.</p><p>This neural network architecture allows for the effective detection and classification of various DDoS attacks using input data consisting of various network traffic characteristics.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3.">Model evaluation</head><p>A confusion matrix was built to evaluate the neural network's effectiveness in detecting and classifying DDoS attacks (Table <ref type="table">1</ref>). The model evaluation is based on four main categories of classification results: True Positive (TP), True Negative (TN), False Positive (FP), and False Negative (FN). Several key performance indicators are calculated based on the TP, TN, FP, and FN values: Accuracy, Precision, Recall, Specificity, and F-score.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 1 Confusion matrix</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>True label</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Predicted label</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>NNrNNNN NrNNNNN</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>DDoS</head><p>In terms of classifying normal traffic and DDoS traffic, accuracy shows the overall efficiency of the model in classifying these two types of traffic:</p><formula xml:id="formula_4">Accuracy=100 % • ∑ (TP+TN ) ∑ (TP+TN + FP+ FN ) , (<label>4</label></formula><formula xml:id="formula_5">)</formula><p>If the model correctly identifies the majority of samples as either normal traffic or a DDoS attack, it will have high accuracy.</p><p>Precision in the context of DDoS detection is the proportion of correctly classified traffic as a DDoS attack among all samples that are classified as attacks:</p><formula xml:id="formula_6">Precision=100 % • ∑ (TP ) ∑ (TP+ FP ) ,<label>(5)</label></formula><p>A high score means that the model rarely mistakes normal traffic for a DDoS attack, meaning that the number of False Positive results is low. This is important in real-world networks, where false alarms can lead to unnecessary blocking of legitimate traffic.</p><p>Recall (Sensitivity) shows how well the model detects real DDoS attacks. It is the proportion of correct attack classifications among all the real attacks present in the dataset:</p><formula xml:id="formula_7">Recall=100 % • ∑ (TP ) ∑ (TP+ FN ) , (<label>6</label></formula><formula xml:id="formula_8">)</formula><p>A high score means that the model effectively detects most or all real DDoS attacks while minimizing the number of missed attacks (False Negative). This is critical because missed attacks can go undetected, allowing attackers to cause damage to the system. Specificity measures how well the model identifies normal traffic and distinguishes it from DDoS attacks:</p><formula xml:id="formula_9">Specificity=100 % • ∑ (TN ) ∑ (TN + FP ) , (<label>7)</label></formula><p>A high score means that the model correctly classifies most normal traffic samples as not DDoS, reducing the number of False Positive results. It indicates how well the model protects legitimate traffic from false blocking.</p><p>The F-score in the case of classifying normal traffic and DDoS attacks provides a balanced assessment between Precision and Recall. It allows you to evaluate the overall performance of the model, taking into account both the model's ability to minimize False Positive results (high Precision) and detect genuine attacks (high Recall):</p><formula xml:id="formula_10">F−score= 2• Recall • Precision Recall+ Precision ,<label>(8)</label></formula><p>A high F-score indicates that the model performs well in detecting real attacks and avoiding false alarms, which is key to reliable network protection.</p><p>These metrics provide a comprehensive assessment of the neural network's performance to classify network traffic and determine how effectively it detects and recognizes different types of DDoS attacks in combination with normal traffic.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Results and discussion</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Detection performance</head><p>In this work, we used a neural network with a 24-106-5 architecture to detect and classify DDoS attacks such as SYN Flooding, ACK Flooding, HTTP Flooding, and UDP Flooding along with normal traffic. The confusion matrix of the model is shown in Table <ref type="table">2</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 2</head><p>Confusion matrix of the neural network 24-106-5 Most of the traffic samples are classified correctly, but it is noticeable that the largest classification errors occur between normal traffic and SYN Flooding. In some cases, the difference between normal connection establishment and SYN Flooding can be small, making it difficult for the model to distinguish between these types of traffic accurately. This also explains why the model sometimes confuses the two types of traffic, as SYN packets are used both in the normal connection establishment process and during an attack. Therefore, the similarity like requests between normal traffic and SYN Flooding may be the main reason for the increase in classification errors between them.</p><p>Table <ref type="table" target="#tab_0">3</ref> shows the performance of the neural network in the task of detecting and classifying DDoS attacks. The overall accuracy rate is 99.35%, which indicates that the model is highly effective in correctly classifying different types of traffic. The model also shows a high Precision of 99.32%, which indicates a minimal number of False Positive results. Recall, which reflects the model's ability to detect real attacks, reaches 99.54%, which means that the model almost never misses real attacks. The Specificity, which indicates the model's ability to identify normal traffic correctly, is 99.11%, which confirms the model's high ability to avoid misclassifying normal traffic as an attack. The F-score is 0.99, emphasizing the model's balance in detecting attacks and minimizing false alarms. Among the individual attack types, ASK Flooding and UDP Flooding are the easiest for the model to detect, with performance scores above 99% for all metrics. At the same time, the performance for SYN Flooding is somewhat lower, especially in Precision and F-score, which may be due to the peculiarities of this type of attack. Overall, the model shows a high level of performance, making it a reliable tool for detecting various types of DDoS attacks.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Practical testing of a neural network</head><p>The machine learning approach to detecting DDoS traffic and normal traffic involves several key steps (Figure <ref type="figure" target="#fig_4">2</ref>). To implement this approach, a special network infrastructure was created (Figure <ref type="figure" target="#fig_5">3</ref>). The basis of this infrastructure is a KVM hypervisor installed on Oracle Linux, which provides virtualization and supports the operation of virtual machines. Communication between the virtual machines and the physical network occurs through a virtual bridge connected to a Wi-Fi router. The Ubuntu Linux server deploys network services such as SSH, HTTP, DNS, FTP, SMTP, and IMAP, which are used to create a realistic network environment. Virtual machines with Parrot Security were launched to generate DDoS traffic to test the DDoS detection algorithms. At the same time, a network packet capture tool is running on Ubuntu Linux, collecting all network traffic for further analysis. Normal traffic, used to simulate normal network activity, is generated by laptops connected to the same network via Wi-Fi. This configuration allows you to collect the necessary data to test the effectiveness of the neural network in realistic conditions by simulating different types of traffic.</p><p>We used tcpdump to capture network packets and save them to a file in the pcap format. Parrot Security created the DDoS traffic using Metasploit, an effective tool for carrying out network attacks, including SYN Flooding, ACK Flooding, HTTP Flooding, and UDP Flooding.</p><p>Special software was developed in the Python programming language to extract features from captured network packets. This software allows for the automatic processing and analysis of large network data, highlighting key features that allow for further traffic classification.</p><p>The total network traffic records created in the lab environment was 10564. Of these, 3845 records were normal traffic, 1721 were SYN Flooding, 2203 were ACK Flooding, 980 were HTTP Flooding, and 1815 were UDP Flooding. The confusion matrix of the model is shown in Table <ref type="table" target="#tab_1">4</ref>. This confusion matrix shows the results of testing a neural network to detect and classify DDoS attacks from traffic generated in a lab environment. The neural network detected 3467 cases of normal traffic correctly. Still, several errors were made when SYN Flooding, ACK Flooding, HTTP Flooding, and UDP Flooding were mistakenly identified as normal traffic. Also, for SYN Flooding, the network correctly predicted 1665 cases but made 56 mistakes, identifying it as normal traffic. In the case of ACK Flooding, the network correctly predicted 2169 samples but made 34 errors. The network accurately classified 955 HTTP Flooding cases, making minor errors with this category, and correctly predicted 1786 UDP Flooding cases. The network generally does a good job of classifying DDoS attacks, but there are several errors, especially when SYN and ACK Flooding are classified as normal traffic.</p><p>Table <ref type="table" target="#tab_2">5</ref> shows the neural network's performance in detecting and classifying DDoS attacks on traffic generated in the laboratory environment. The overall Accuracy for all DDoS attacks is 95.05%, which indicates that the model can classify both normal traffic and different types of attacks correctly. Precision, which determines the percentage of correct positive predictions among all predicted positive cases for all attacks, is 94.56%. Recall, which indicates how well the model detects all positive cases, has the highest performance among the other metrics. The overall Recall is 97.85%. Specificity, which shows how well the model avoids false positives, is also quite high. The overall score for all attacks is 90.16%. For all attacks, the F-score, the harmonic mean between Precision and Recall, is 0.96.</p><p>Thus, the neural network demonstrates high efficiency in detecting and classifying DDoS attacks on traffic generated in the laboratory environment, showing good results for all major metrics for each type of attack.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Conclusions</head><p>As a result of the study, the neural network showed high efficiency in detecting and classifying DDoS attacks. The overall accuracy is 95.05%, and the Precision, Recall, and Specificity values are high for all types of attacks, indicating the model's reliability. For all DDoS attacks, the overall F-score is 0.96, indicating that the model is highly balanced. This means that the model effectively detects genuine attacks without generating many false alarms.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>( 1 )</head><label>1</label><figDesc>where x i are the input values, ❑ i are the weights associated with each input, b is the bias that allows the neuron to better adapt to the data, b is the activation function, n is the number of input signals or the number of input features, y is the output of the neuron. Each neuron receives input signals represented as a set of values x 1 , x 2 , … , x n . These values are weighted according to their weights ❑ 1 ,❑ 2 , … ,❑ n , which are adjusted during model training. The sum of the weighted inputs is then passed to the activation function φ.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Architecture of the 24-106-5 feed-forward neural network.</figDesc><graphic coords="4,85.20,467.75,424.90,219.55" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head></head><label></label><figDesc>TP) represents the number of times the model correctly identified an attack. True Negative (TN) represents the number of times the model correctly identified normal traffic. False Positive (FP) represents the number of times the model incorrectly identified normal traffic as an attack. False Negative (FN) shows the number of cases when the model failed to recognize an attack and classified the data as normal traffic.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Steps of the malicious traffic detection approach.</figDesc><graphic coords="9,115.70,228.45,363.90,64.90" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Lab network infrastructure.</figDesc><graphic coords="9,145.40,360.00,318.70,225.20" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 3</head><label>3</label><figDesc>Performance indicators of the neural network 24-106-5</figDesc><table><row><cell></cell><cell></cell><cell cols="3">NNrNNNNNrNNNNN</cell><cell></cell></row><row><cell>Performance</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>indicator</cell><cell>All DDoS</cell><cell>SYN</cell><cell>ACK</cell><cell>HTTP</cell><cell>UDP</cell></row><row><cell></cell><cell>Flooding</cell><cell>Flooding</cell><cell>Flooding</cell><cell>Flooding</cell><cell>Flooding</cell></row><row><cell>NNNNrNNNN</cell><cell>99.35</cell><cell>99.17</cell><cell>99.88</cell><cell>99.88</cell><cell>99.87</cell></row><row><cell>(%)</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>Precision (%)</cell><cell>99.32</cell><cell>97.21</cell><cell>99.73</cell><cell>98.73</cell><cell>99.86</cell></row><row><cell>Recall (%)</cell><cell>99.54</cell><cell>98.12</cell><cell>99.91</cell><cell>99.36</cell><cell>99.79</cell></row><row><cell>Specificity (%)</cell><cell>99.11</cell><cell>99.39</cell><cell>99.87</cell><cell>99.91</cell><cell>99.91</cell></row><row><cell>F-score</cell><cell>0.99</cell><cell>0.97</cell><cell>0.99</cell><cell>0.99</cell><cell>0.99</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 4</head><label>4</label><figDesc>Confusion matrix of neural network 24-106-5 in practical testing</figDesc><table><row><cell></cell><cell></cell><cell cols="2">Predicted label</cell><cell></cell><cell></cell></row><row><cell>True label</cell><cell>NNrNNNN</cell><cell>SYN</cell><cell>ACK</cell><cell>HTTP</cell><cell>UDP</cell></row><row><cell></cell><cell>NrNNNNN</cell><cell>Flooding</cell><cell>Flooding</cell><cell>Flooding</cell><cell>Flooding</cell></row><row><cell>NNrNNNN</cell><cell>3467</cell><cell>126</cell><cell>101</cell><cell>64</cell><cell>87</cell></row><row><cell>NrNNNNN</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>SYN Flooding</cell><cell>56</cell><cell>1665</cell><cell>-</cell><cell>-</cell><cell>-</cell></row><row><cell>ACK Flooding</cell><cell>34</cell><cell>-</cell><cell>2169</cell><cell>-</cell><cell>-</cell></row><row><cell>HTTP Flooding</cell><cell>25</cell><cell>-</cell><cell>-</cell><cell>955</cell><cell>-</cell></row><row><cell>UDP Flooding</cell><cell>29</cell><cell>-</cell><cell>-</cell><cell>-</cell><cell>1786</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>Table 5</head><label>5</label><figDesc>Performance indicators of the neural network 24-106-5 in practical testing</figDesc><table><row><cell></cell><cell></cell><cell cols="2">NNrNNNNNrNNNNN</cell><cell></cell><cell></cell></row><row><cell>Performance</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>indicator</cell><cell>All DDoS</cell><cell>SYN</cell><cell>ACK</cell><cell>HTTP</cell><cell>UDP</cell></row><row><cell></cell><cell>Flooding</cell><cell>Flooding</cell><cell>Flooding</cell><cell>Flooding</cell><cell>Flooding</cell></row><row><cell>NNNNrNNNN</cell><cell>95.05</cell><cell>96.57</cell><cell>97.66</cell><cell>98.02</cell><cell>97.83</cell></row><row><cell>(%)</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>Precision (%)</cell><cell>94.56</cell><cell>92.96</cell><cell>95.55</cell><cell>93.71</cell><cell>95.35</cell></row><row><cell>Recall (%)</cell><cell>97.85</cell><cell>96.74</cell><cell>98.45</cell><cell>97.44</cell><cell>98.40</cell></row><row><cell>Specificity (%)</cell><cell>90.16</cell><cell>96.49</cell><cell>97.16</cell><cell>98.18</cell><cell>97.55</cell></row><row><cell>F-score</cell><cell>0.96</cell><cell>0.95</cell><cell>0.97</cell><cell>0.95</cell><cell>0.97</cell></row></table></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">What is a DDoS attack</title>
		<ptr target="https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/" />
		<imprint>
			<date type="published" when="2024-08-25">Aug. 25, 2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Infectious diseases prediction based on machine learning: the impact of data reduction using feature extraction techniques</title>
		<author>
			<persName><forename type="first">Selestine</forename><surname>Melchane</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Youssef</forename><surname>Elmir</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Farid</forename><surname>Kacimi</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.procs.2024.06.223</idno>
	</analytic>
	<monogr>
		<title level="j">Procedia Computer Science</title>
		<idno type="ISSN">1877-0509</idno>
		<imprint>
			<biblScope unit="volume">239</biblScope>
			<biblScope unit="page" from="675" to="683" />
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Machine learning and economic forecasting: The role of international trade networks</title>
		<author>
			<persName><forename type="first">Christiano</forename><surname>Thiago</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Paulo</forename><surname>Silva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Berri</forename><surname>Victor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Diego</forename><forename type="middle">R</forename><surname>Wilhelm</surname></persName>
		</author>
		<author>
			<persName><surname>Amancio</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.physa.2024.129977</idno>
	</analytic>
	<monogr>
		<title level="j">Physica A: Statistical Mechanics and its Applications</title>
		<idno type="ISSN">0378-4371</idno>
		<imprint>
			<biblScope unit="volume">649</biblScope>
			<biblScope unit="page">129977</biblScope>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Information Technologies Use in the Study of Functional Properties of Wheeled Vehicles</title>
		<author>
			<persName><forename type="first">O</forename><surname>Lyashuk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Stashkiv</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Lytvynenko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Sakhno</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Khoroshun</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ITTAP</title>
		<imprint>
			<biblScope unit="page" from="500" to="512" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Methods of jump-like creep modeling of AMg6 aluminum alloy</title>
		<author>
			<persName><forename type="first">O</forename><surname>Yasniy</surname></persName>
		</author>
		<author>
			<persName><forename type="middle">M</forename><surname>Pasternak Ia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Didych</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Fedak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Tymoshchuk</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.prostr.2023.07.141</idno>
	</analytic>
	<monogr>
		<title level="j">Procedia Structural Integrity</title>
		<imprint>
			<biblScope unit="volume">48</biblScope>
			<biblScope unit="page" from="149" to="154" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">The evaluation of durability of structural elements using neural networks</title>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">S</forename><surname>Didych</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Pastukh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Pyndus</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Yasniy</surname></persName>
		</author>
		<idno type="DOI">10.12776/ams.v24i1.966</idno>
	</analytic>
	<monogr>
		<title level="j">Acta Metallurgica Slovaca</title>
		<imprint>
			<biblScope unit="volume">24</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="82" to="87" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Fracture Mechanism Analysis of the Heat-Resistant Steel 15Kh2MFA(II) After Laser Shock-Wave Processing</title>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">B</forename><surname>Okipnyi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">O</forename><surname>Maruschak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">I</forename><surname>Zakiev</surname></persName>
		</author>
		<idno type="DOI">10.1007/s11668-014-9869-4</idno>
	</analytic>
	<monogr>
		<title level="j">J Fail. Anal. and Preven</title>
		<imprint>
			<biblScope unit="volume">14</biblScope>
			<biblScope unit="page" from="668" to="674" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Evaluation of the efficiency of the system for detecting malicious outgoing traffic in public networks</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Klots</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Petliak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Titova</surname></persName>
		</author>
		<idno type="DOI">10.1109/DESSERT61349.2023.10416502</idno>
	</analytic>
	<monogr>
		<title level="m">13th International Conference on Dependable Systems, Services and Technologies (DESSERT)</title>
				<meeting><address><addrLine>Athens, Greece</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2023">2023. 2023</date>
			<biblScope unit="page" from="1" to="5" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Signature-based Approach to Detecting Malicious Outgoing Traffic</title>
		<author>
			<persName><forename type="first">N</forename><surname>Petliak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Klots</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Titova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Cheshun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Boyarchuk</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">4th International Workshop on Intelligent Information Technologies and Systems of Information Security, IntellTSIS 2023</title>
				<imprint>
			<date type="published" when="2023">2023</date>
			<biblScope unit="page" from="486" to="506" />
		</imprint>
	</monogr>
	<note>CEUR Workshop Proceedings</note>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title/>
		<author>
			<persName><forename type="first">Hayelom</forename><forename type="middle">;</forename><surname>Gebrye</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Yong</forename><surname>Wang</surname></persName>
		</author>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Flooding-Based-DDoS-Muleticlass-Dataset</title>
		<author>
			<persName><forename type="first">Fagen</forename><surname>Li</surname></persName>
		</author>
		<idno type="DOI">10.17632/w24hc4vy7t.1</idno>
	</analytic>
	<monogr>
		<title level="j">Mendeley Data</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">IoT network intrusion dataset</title>
		<author>
			<persName><forename type="first">Hyunjae</forename><surname>Kang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Dong</forename><surname>Hyun Ahn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Gyung</forename></persName>
		</author>
		<author>
			<persName><forename type="first">Min</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Jeong</forename><forename type="middle">Do</forename><surname>Yoo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Kyung</forename><forename type="middle">Ho</forename><surname>Park</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Huy</forename><surname>Kang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Kim</forename></persName>
		</author>
		<idno type="DOI">10.21227/q70p-q449</idno>
	</analytic>
	<monogr>
		<title level="j">IEEE Dataport</title>
		<imprint>
			<date type="published" when="2019-09-27">September 27. 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<ptr target="https://www.cloudflare.com/learning/ddos/syn-flood-ddos-attack/" />
		<title level="m">SYN flood attack</title>
				<imprint>
			<date type="published" when="2024-08-25">Aug. 25, 2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<title level="m" type="main">What is an ACK flood DDoS attack?</title>
		<ptr target="https://www.cloudflare.com/learning/ddos/what-is-an-ack-flood/" />
		<imprint>
			<date type="published" when="2024-08-25">Aug. 25, 2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<title level="m" type="main">HTTP flood attack</title>
		<ptr target="https://www.cloudflare.com/learning/ddos/http-flood-ddos-attack/" />
		<imprint>
			<date type="published" when="2024-08-25">Aug. 25, 2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<ptr target="https://www.cloudflare.com/learning/ddos/udp-flood-ddos-attack/" />
		<title level="m">UDP flood attack</title>
				<imprint>
			<date type="published" when="2024-08-25">Aug. 25, 2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<title level="m" type="main">Neural networks and learning machines</title>
		<author>
			<persName><forename type="first">S</forename><surname>Haykin</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2009">2009</date>
			<publisher>Prentice Hall</publisher>
			<biblScope unit="page">936</biblScope>
			<pubPlace>Hamilton, Ontario</pubPlace>
		</imprint>
	</monogr>
	<note>3rd ed</note>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
