<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "http://dtd.nlm.nih.gov/publishing/3.0/journalpublishing3.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="3.0" xml:lang="en" article-type="research article">
 <front>
  <journal-meta>
   <journal-id journal-id-type="publisher-id">
    jis
   </journal-id>
   <journal-title-group>
    <journal-title>
     Journal of Information Security
    </journal-title>
   </journal-title-group>
   <issn pub-type="epub">
    2153-1234
   </issn>
   <issn publication-format="print">
    2153-1242
   </issn>
   <publisher>
    <publisher-name>
     Scientific Research Publishing
    </publisher-name>
   </publisher>
  </journal-meta>
  <article-meta>
   <article-id pub-id-type="doi">
    10.4236/jis.2025.164024
   </article-id>
   <article-id pub-id-type="publisher-id">
    jis-145147
   </article-id>
   <article-categories>
    <subj-group subj-group-type="heading">
     <subject>
      Articles
     </subject>
    </subj-group>
    <subj-group subj-group-type="Discipline-v2">
     <subject>
      Computer Science 
     </subject>
     <subject>
       Communications
     </subject>
    </subj-group>
   </article-categories>
   <title-group>
    5G Network Vulnerabilities: A Security Mechanism for Detecting and Blocking DDoS Threats at the Network Edge 
   </title-group>
   <contrib-group>
    <contrib contrib-type="author" xlink:type="simple">
     <name name-style="western">
      <surname>
       Sakib
      </surname>
      <given-names>
       Mahmud
      </given-names>
     </name>
    </contrib>
    <contrib contrib-type="author" xlink:type="simple">
     <name name-style="western">
      <surname>
       Ahsan
      </surname>
      <given-names>
       Ullah
      </given-names>
     </name>
    </contrib>
    <contrib contrib-type="author" xlink:type="simple">
     <name name-style="western">
      <surname>
       Shakhawat Hossain
      </surname>
      <given-names>
       Shipon
      </given-names>
     </name>
    </contrib>
    <contrib contrib-type="author" xlink:type="simple">
     <name name-style="western">
      <surname>
       Mahedi
      </surname>
      <given-names>
       Hassan
      </given-names>
     </name>
    </contrib>
    <contrib contrib-type="author" xlink:type="simple">
     <name name-style="western">
      <surname>
       Md Nazmus
      </surname>
      <given-names>
       Sakib
      </given-names>
     </name>
    </contrib>
   </contrib-group> 
   <aff id="affnull">
    <addr-line>
     aDepartment of Computer Science and Engineering, World University of Bangladesh, Dhaka, Bangladesh
    </addr-line> 
   </aff> 
   <pub-date pub-type="epub">
    <day>
     22
    </day> 
    <month>
     08
    </month>
    <year>
     2025
    </year>
   </pub-date> 
   <volume>
    16
   </volume> 
   <issue>
    04
   </issue>
   <fpage>
    472
   </fpage>
   <lpage>
    499
   </lpage>
   <history>
    <date date-type="received">
     <day>
      3,
     </day>
     <month>
      June
     </month>
     <year>
      2025
     </year>
    </date>
    <date date-type="published">
     <day>
      23,
     </day>
     <month>
      June
     </month>
     <year>
      2025
     </year> 
    </date> 
    <date date-type="accepted">
     <day>
      23,
     </day>
     <month>
      August
     </month>
     <year>
      2025
     </year> 
    </date>
   </history>
   <permissions>
    <copyright-statement>
     © Copyright 2014 by authors and Scientific Research Publishing Inc. 
    </copyright-statement>
    <copyright-year>
     2014
    </copyright-year>
    <license>
     <license-p>
      This work is licensed under the Creative Commons Attribution International License (CC BY). http://creativecommons.org/licenses/by/4.0/
     </license-p>
    </license>
   </permissions>
   <abstract>
    The rapid expansion of 5G networks has revolutionized global connectivity, enabling billions of devices to communicate seamlessly across various industries. However, this advancement has also increased the vulnerability to Distributed Denial of Service (DDoS) attacks, posing significant threats to network reliability. This research presents a novel machine learning-based approach for detecting and mitigating DDoS attacks at the Multi-Access Edge Computing (MEC) layer, with the objective of enhancing the security and efficiency of 5G ecosystems. The proposed system integrates Random Forest (RF), K-Nearest Neighbor (KNN), and XGBoost algorithms with the Zeek Intrusion Detection System (IDS) to enable real-time traffic classification and mitigation at the network edge. Models were trained using the CIC-DDoS2019 dataset to identify realistic attack patterns. Python was used for implementation, and Zeek IDS dynamically extracted traffic features. Simulated traffic streams, blending both benign and malicious behaviors, were employed to evaluate system performance under realistic conditions. The architecture leverages separate inbound and outbound switches to isolate traffic flows, enabling immediate blocking of malicious packets and blacklisting of source IPs while maintaining uninterrupted service for legitimate traffic. The proof-of-concept demonstrated the ability to detect and mitigate 40% of malicious traffic effectively. Despite its success, the system currently relies on simulated data and lacks a complete deployment-ready software package. Future work will focus on building a robust, scalable implementation suitable for real-world MEC environments. This research provides a promising foundation for protecting 5G networks from evolving DDoS threats without compromising legitimate network operations.
   </abstract>
   <kwd-group> 
    <kwd>
     5G Networks
    </kwd> 
    <kwd>
      DDoS Attacks
    </kwd> 
    <kwd>
      Network Security
    </kwd> 
    <kwd>
      Multi-Access Edge Computing (MEC)
    </kwd> 
    <kwd>
      Intrusion Detection System (IDS)
    </kwd> 
    <kwd>
      Machine Learning
    </kwd> 
    <kwd>
      Network Edge
    </kwd> 
    <kwd>
      Threat Mitigation
    </kwd>
   </kwd-group>
  </article-meta>
 </front>
 <body>
  <sec id="s1">
   <title>1. Introduction</title>
   <p>The fifth generation of mobile networks, commonly known as 5G, is revolutionizing the way devices communicate. Unlike earlier generations that primarily connected mobile phones, 5G extends connectivity to a vast array of devices, including smart home appliances, healthcare systems, financial platforms, and transportation networks (Techopedia, n.d.; IBM, n.d.). While this level of interconnectivity enables innovative use cases and enhances efficiency, it also introduces significant security vulnerabilities. Devices on 5G networks are often always online, making them susceptible to exploitation if robust security measures are not in place. This pervasive connectivity creates a new attack surface for malicious activities, including Distributed Denial of Service (DDoS) attacks <xref ref-type="bibr" rid="scirp.145147-1">
     [1]
    </xref>.</p>
   <p>
    <xref ref-type="bibr" rid="scirp.145147-"></xref>A DDoS attack involves hundreds to thousands of compromised devices, often orchestrated as part of a botnet, overwhelming a target server or network with excessive traffic. These attacks can slow down or completely disrupt services, posing severe risks in highly connected 5G environments where uptime and performance are critical. As 5G adoption accelerates, addressing these threats becomes essential to safeguarding sensitive data and ensuring uninterrupted network functionality <xref ref-type="bibr" rid="scirp.145147-2">
     [2]
    </xref>.</p>
   <p>This research investigates vulnerabilities in the 5G ecosystem that enable attackers to exploit devices for botnets and launch DDoS attacks. Unlike conventional methods that focus on rate limiting or IP filtering, this study introduces a novel security mechanism that leverages Multi-Access Edge Computing (MEC) and strategically placed switches to manage inbound and outbound traffic. The proposed approach targets malicious traffic originating from compromised end-user devices, detecting and blocking threats closer to their source.</p>
   <p>To enhance detection accuracy, machine learning algorithms like Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost models are utilized to analyze and identify DDoS attack patterns. The CIC-DDoS2019 dataset, a comprehensive and publicly available benchmark dataset, is used to train and validate the model. By integrating ML-powered analysis with MEC and switch-based traffic management, this mechanism continuously monitors data streams and network activity, detecting anomalies or traffic surges indicative of DDoS attacks. This innovative solution not only ensures real-time protection for endpoints across the 5G network but also strengthens the overall resilience of the communication infrastructure against evolving threats.</p>
   <sec id="s1_1">
    <title>1.1. Objectives</title>
    <p>The objectives of this study are as follows:</p>
    <p>1) To identify and analyze weaknesses within the 5G ecosystem that allow devices to be misused as botnets for Distributed Denial of Service (DDoS) attacks at Edge Network.</p>
    <p>2) To propose a stronger security system, focused on real-time monitoring and blocking, to reduce risks for devices connected to 5G.</p>
   </sec>
   <sec id="s1_2">
    <title>1.2. Justification</title>
    <p>As 5G becomes a key part of daily life, protecting it from cyber threats is essential for public safety and data security. Devices, due to their constant connection and limited security features, are especially at risk of being used in harmful botnets. Such botnets can cause serious harm, like large-scale DDoS attacks that overwhelm systems and disrupt services or gain unauthorized access to sensitive data (Allot, n.d.). This research is timely, as many existing 5G security measures focus on general security issues but may overlook specific threats like DDoS attacks. By enhancing security at the network’s edge, we can better prevent unauthorized access and maintain trust in 5G technology, which is essential as it supports critical applications. Securing the network will bring significant positive impacts <xref ref-type="bibr" rid="scirp.145147-3">
      [3]
     </xref>.</p>
    <p>The Common Vulnerability Scoring System (CVSS) helps cybersecurity experts rate how dangerous vulnerabilities are. It gives a score from 0.0 (not severe) to 10.0 (very severe) based on how much damage it can cause and how easy it is to exploit. Using these scores helps experts focus on the most serious problems first.</p>
    <p>The recent Common Vulnerability and Exposure (CVE) score of DDoS attacks (<xref ref-type="table" rid="table1">
      Table 1
     </xref>):</p>
    <table-wrap id="table1">
     <label>
      <xref ref-type="table" rid="table1">
       Table 1
      </xref></label>
     <caption>
      <title>
       <xref ref-type="bibr" rid="scirp.145147-"></xref>Table 1. Severe CVE scores of DDoS vulnerabilities (2024).</title>
     </caption>
     <table class="MsoTableGrid custom-table" border="0" cellspacing="0" cellpadding="0"> 
      <tr> 
       <td class="custom-bottom-td acenter" width="41.55%"><p style="text-align:center">CVE ID</p></td> 
       <td class="custom-bottom-td acenter" width="16.36%"><p style="text-align:center">Score</p></td> 
      </tr> 
      <tr> 
       <td class="custom-top-td acenter" width="41.55%"><p style="text-align:center">CVE-2024-34567</p></td> 
       <td class="custom-top-td acenter" width="16.36%"><p style="text-align:center">9.9</p></td> 
      </tr> 
      <tr> 
       <td class="acenter" width="41.55%"><p style="text-align:center">CVE-2024-23456</p></td> 
       <td class="acenter" width="16.36%"><p style="text-align:center">8.7</p></td> 
      </tr> 
     </table>
    </table-wrap>
    <p>The increasing frequency and sophistication of Distributed Denial-of-Service (DDoS) attacks present significant challenges to protecting critical infrastructure, highlighting the need for advanced and targeted defense mechanisms. This research, titled “5G Network Vulnerabilities: A Security Mechanism for Detecting and Blocking DDoS Threats at the Network Edge”, introduces a novel approach to addressing these challenges. Unlike traditional methods such as rate limiting or IP-based filtering, which are insufficient for handling the evolving nature of modern DDoS attacks, this study focuses on detecting and blocking malicious traffic originating from end users. By leveraging Multi-Access Edge Computing (MEC) and strategically managing inbound and outbound traffic through different switches, the proposed solution enhances the ability to mitigate DDoS threats closer to their source. This approach not only ensures a more efficient and accurate detection mechanism but also strengthens the overall security and resilience of the network infrastructure against such threats.</p>
   </sec>
   <sec id="s1_3">
    <title>1.3. Scope of Study</title>
    <p>This research looks into how to find and stop Distributed Denial of Service (DDoS) attacks in 5G networks. It focuses on protecting the edge of the network. The goal is to create a new security system that uses Multi-Access Edge Computing (MEC) and switches placed in important spots to check and manage internet traffic coming in and out of the network. The research specifically looks at traffic from compromised end-user devices to deal with a major weakness in 5G networks: the misuse of interconnected devices to launch DDoS attacks.</p>
    <p>A key part of this research is the use of Zeek, a powerful tool for analyzing network traffic. Zeek is combined with machine learning algorithms at the MEC layer. This helps to find and analyze bad traffic in real-time. The setup makes sure that incoming and outgoing traffic are kept separate using different switches. This stops traffic from mixing and makes it easier to find and handle unusual things. This separation is expected to make stopping DDoS attacks more efficient and accurate.</p>
    <p>The research uses a few different machine learning models, including Random Forest (RF), K-Nearest Neighbor (KNN), and XGBoost, to find attacks. These models are taught and tested using something called the CIC-DDoS2019 dataset. This dataset is good for copying real-world DDoS attack situations and testing the suggested solution.</p>
    <p>Key Areas of Focus</p>
    <p>1) 5G Network Vulnerabilities: Identifying architectural and operational weaknesses in 5G that make it prone to DDoS attacks.</p>
    <p>2) Edge-Based Traffic Management: Implementing MEC with Zeek to monitor and manage traffic at the network edge.</p>
    <p>3) ML-Powered Detection: Utilizing Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost models to classify anomalous traffic patterns indicative of DDoS attacks.</p>
    <p>4) Traffic Segregation: Ensuring inbound and outbound traffic is handled on separate switches to prevent cross-contamination and improve detection precision.</p>
    <p>5) Dataset Utilization: Using the CIC-DDoS2019 dataset to develop and validate the detection mechanism.</p>
    <p>6) Real-Time Protection: Providing continuous monitoring, anomaly detection, and rapid mitigation of threats in a dynamic 5G environment.</p>
    <p>Exclusions</p>
    <p>The study does not include:</p>
    <p>This research contributes to the field of 5G security by introducing a scalable, efficient, and ML-driven edge-based solution that effectively counters DDoS threats, ensuring the resilience and safety of critical network infrastructure.</p>
    <sec id="s1">
     <title>2. Literature Review</title>
     <p>Recent research on Distributed Denial of Service (DDoS) threats within 5G networks and existing solutions will be reviewed. This review aims to highlight the limitations in current methods and set the foundation for the novel security mechanism proposed in this study. By addressing gaps in scalability, real-time traffic management, and endpoint-specific security, this research introduces a tailored mechanism that enhances 5G network defense against DDoS threats, particularly by focusing on malicious traffic originating from end-user devices.</p>
    </sec>
    <sec id="s2_4">
     <title>2.1. Review of Existing Solutions</title>
     <p>Onoja et al. <xref ref-type="bibr" rid="scirp.145147-4">
       [4]
      </xref>, in their study DDoS Threats and Solutions for 5G Networks, present an overview of various DDoS protection strategies. Their work emphasizes Software-Defined Networking (SDN) for centralized traffic management and edge computing for localized detection. While these methods isolate some DDoS patterns, they are limited in their ability to scale across diverse 5G ecosystems, where a wide range of endpoints, from IoT devices to smart appliances, are continuously online. The study also lacks emphasis on long-term botnet monitoring and adaptive attack detection, leaving gaps in addressing threats from botnets that evolve over time or remain dormant before initiating coordinated attacks.</p>
     <p>Similarly, studies such as Ghorbani et al. <xref ref-type="bibr" rid="scirp.145147-5">
       [5]
      </xref> and Serrano Mamolar et al. <xref ref-type="bibr" rid="scirp.145147-6">
       [6]
      </xref> rely on static rule-based mechanisms to identify DDoS patterns. These approaches are effective for predictable attack behaviors but struggle to detect advanced threats that leverage stealth or adaptive methods. Such limitations underscore the need for a more dynamic, endpoint-focused solution that addresses the vulnerabilities posed by the always-on connectivity inherent in 5G networks.</p>
     <p>Sanmorino and Yazid <xref ref-type="bibr" rid="scirp.145147-7">
       [7]
      </xref> proposed the use of flow patterns to detect and block malicious traffic. While their methodology demonstrated success in detecting certain DDoS traffic characteristics, it heavily relied on predefined traffic patterns, which are inadequate for detecting highly adaptive and evolving attack vectors. Furthermore, cluster-based analysis methods for DDoS detection are time-consuming and often less precise, making them unsuitable for real-time applications in dense 5G deployments.</p>
    </sec>
    <sec id="s2_5">
     <title>2.2. Proposed Improvements</title>
     <p>To address these limitations, this study focuses on a novel security mechanism that leverages Multi-Access Edge Computing (MEC) and the strategic use of separate switches for inbound and outbound traffic. Unlike existing solutions that often mix traffic or rely solely on centralized analysis, this approach ensures better segregation and management of network flows. By preventing the mixing of inbound and outbound traffic at the switch level, the proposed mechanism enables more precise detection of malicious traffic.</p>
     <p>This study also incorporates Zeek, a sophisticated tool for analyzing network traffic, to improve real-time detection capabilities at the MEC layer. The proposed solution uses machine learning algorithms like Random Forest (RF), K-Nearest Neighbor (KNN), and XGBoost, trained on the CIC-DDoS2019 dataset. This dataset provides a variety of traffic features, such as “Flow Duration”, “Total Fwd Packets”, “Total Backward Packets”, “Fwd Packet Length Max”, “Bwd Packet Length Max”, “Flow IAT Mean”, “Flow IAT Std”, “Flow IAT Max”, “Fwd Packets/s”, and “Bwd Packets/s”, which are used to identify unusual patterns in traffic flows. Although Zeek is not directly integrated with the machine learning models in this study, future work should aim to integrate these components for enhanced real-time detection. This integration will ensure that threats are detected proactively, even as attack methods change.</p>
    </sec>
    <sec id="s2_6">
     <title>2.3. The Novelty of the Proposed Solution</title>
     <p>This study’s novelty lies in its focus on endpoint-specific DDoS mitigation within 5G networks by combining MEC-based traffic analysis with ML-driven detection mechanisms. Unlike traditional methods, which often treat endpoints as secondary to overall network security, this mechanism positions endpoints as primary points of analysis. The always-on nature of 5G-connected devices makes them prime targets for botnet formation and subsequent DDoS attacks, and this solution is specifically designed to address that vulnerability.</p>
     <p>The use of separate switches for inbound and outbound traffic further enhances the precision of detection, as it prevents the mixing of legitimate and malicious traffic, enabling faster response times. By deploying this mechanism at the MEC layer, threats can be mitigated closer to their source, reducing the strain on the central network and improving scalability in dense 5G environments.</p>
     <p>This research introduces a robust framework for detecting and blocking DDoS attacks through continuous monitoring, malicious traffic eradication and containment ensuring both adaptability and scalability. By leveraging the CIC-DDoS2019 dataset and integrating Zeek at the edge, the study establishes a new benchmark for real-time 5G network defense, addressing gaps in prior research and paving the way for more resilient and secure 5G infrastructures.</p>
    </sec>
   </sec>
   <sec id="s3">
    <title>
     <xref ref-type="bibr" rid="scirp.145147-"></xref>3. Methodology</title>
    <p>This methodology was adopted to design, implement, and evaluate the proposed security mechanism for detecting and mitigating Distributed Denial of Service (DDoS) attacks within 5G networks. The approach follows a structured incident response framework inspired by the SANS Incident Response Process, consisting of six phases: Preparation, Identification, Containment, Eradication, Recovery, and Lessons Learned (<xref ref-type="fig" rid="fig1">
      Figure 1
     </xref>). The methodology integrates Multi-Access Edge Computing (MEC) with strategically isolated switches for inbound and outbound traffic management to ensure precise threat detection.</p>
    <fig id="fig1" position="float">
     <label>Figure 1</label>
     <caption>
      <title>Figure 1. The SANS institute incident response cycle.</title>
     </caption>
     <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId17.jpeg?20250826033327" />
    </fig>
    <p>Additionally, the proposed system employs Zeek for traffic analysis and an AI-based Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost model trained on the CIC-DDoS2019 dataset to identify abnormal patterns and block malicious traffic. Traffic flows are continuously monitored at the network edge, ensuring real-time identification of threats originating from compromised end-user devices. The incident response process allows for systematic detection, containment, and mitigation of DDoS attacks, ensuring minimal disruption to the network. By leveraging edge computing and AI, this methodology provides a scalable, efficient, and proactive solution for strengthening 5G network security.</p>
    <sec id="s3_1">
     <title>Description of Methodology</title>
     <p>The proposed methodology is justified as it addresses the challenges of 5G networks by detecting and mitigating Distributed Denial of Service (DDoS) attacks at the network edge. This approach leverages Multi-Access Edge Computing (MEC), which allows for real-time traffic monitoring and analysis closer to the source of malicious activity. By incorporating tools such as Zeek for traffic analysis and machine learning models—Random Forest (RF), K-Nearest Neighbor (KNN), and XGBoost—the system is capable of identifying malicious traffic patterns with high accuracy. The methodology further enhances detection efficiency by isolating inbound and outbound traffic using separate switches, ensuring precise control over network flows. Following the structured SANS Incident Response Process, the proposed system ensures a systematic approach to threat detection, containment, and mitigation, minimizing disruption to the 5G network infrastructure.</p>
     <p>The following covers the details about the methodology chosen:</p>
     <p>1) Flow Duration: Measures the time duration of a traffic flow. Malicious traffic often exhibits longer or irregular durations compared to normal traffic, making this feature critical for identifying anomalies.</p>
     <p>2) Total Forward Packets: Counts the total number of packets sent in the forward direction during a flow. DDoS traffic often includes an unusually high number of packets, which can help distinguish malicious flows.</p>
     <p>3) Total Backward Packets: Counts the total number of packets sent in the reverse direction. This feature complements the forward packet count to provide a complete picture of traffic flow behavior.</p>
     <p>4) Forward Packet Length Max: Captures the maximum length of packets in the forward direction. DDoS attacks may include large packets to overwhelm the target, making this feature valuable.</p>
     <p>5) Backward Packet Length Max: Captures the maximum length of packets in the reverse direction. Similar to the forward packet length, it aids in identifying abnormal traffic patterns.</p>
     <p>6) Flow Inter-Arrival Time (IAT) Mean: Measures the average time between packets in a flow. Malicious traffic often exhibits irregular inter-arrival times compared to legitimate traffic.</p>
     <p>7) Flow Inter-Arrival Time (IAT) Standard Deviation: Quantifies the variability in inter-arrival times. High variability can indicate irregular traffic patterns typical of DDoS attacks.</p>
     <p>8) Flow Inter-Arrival Time (IAT) Max: Captures the maximum inter-arrival time within a flow. This feature provides additional insight into traffic irregularities.</p>
     <p>9) Forward Packets per Second (Fwd Packets/s): Calculates the rate of packets sent in the forward direction. DDoS traffic often involves a high packet rate, making this feature crucial.</p>
     <p>10) Backward Packets per Second (Bwd Packets/s): Calculates the rate of packets sent in the reverse direction. It complements the forward packet rate to identify anomalous patterns.</p>
     <p>These features were chosen because they collectively capture the characteristics of network traffic, including volume, timing, and flow behavior. Such metrics are critical for differentiating between legitimate and malicious traffic in real-time. This comprehensive preparation ensures the network is equipped to handle DDoS threats effectively.</p>
     <p>At the Multi-Access Edge Computing (MEC) layer, the AI-trained detection program runs continuously to analyze and classify the traffic. The Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost model detects anomalies and determine whether the traffic is good or bad. Once harmful traffic is identified, it is contained using the outbound switch, preventing it from reaching the core network. This approach ensures that malicious traffic is blocked at the edge, minimizing the risk of disruption to the 5G network while allowing legitimate traffic to flow smoothly.</p>
     <p>By leveraging Zeek for deep traffic analysis, detailed logs are generated to pinpoint the root cause of the DDoS attack. If a network provider uses a single switch with VLANs for traffic separation, the compromised VLAN segment can be isolated, and the bad traffic can be purged. Once the source is identified, corrective measures are applied to remove or neutralize the malicious devices, such as shutting down affected endpoints, updating security rules, or blacklisting the source IPs.</p>
     <p>This process ensures that the network is not only protected from immediate threats but also cleaned thoroughly, reducing the chances of future attack recurrence.</p>
     <p>Comprehensive documentation is completed, ensuring that all aspects of the incident, including events, actions taken, and challenges faced, are clearly recorded. An incident report is prepared, offering a detailed, step-by-step analysis of the incident while answering critical questions: Who, What, Where, Why, and How. This report helps identify areas where the response was effective and where improvements are needed.</p>
     <p>Additionally, Zeek’s capability to log details of the attack can be analyzed to identify patterns of malicious traffic. These logs provide insights into the nature of the attack and enable the development of preemptive measures to mitigate similar threats in the future. By applying these lessons, the incident response process is refined, ensuring better preparedness and stronger defense against future DDoS threats within the 5G network.</p>
     <p>The CSIRT uses the report to identify specific ways to improve team performance by highlighting any issues that were not handled efficiently. Metrics derived from the incident, such as response time or detection accuracy, are established as benchmarks for future comparisons. Finally, a lessons learned meeting is conducted with the CSIRT team and key stakeholders to discuss findings and implement improvements immediately. By applying these lessons, the incident response process is refined, ensuring better preparedness and stronger defense against future DDoS threats within the 5G network.</p>
    </sec>
   </sec>
   <sec id="s4">
    <title>
     <xref ref-type="bibr" rid="scirp.145147-"></xref>4. Requirement Analysis, Design &amp; Developments</title>
    <sec id="s4_1">
     <title>4.1. Requirement Gathering Technique</title>
     <p>This chapter presents the key requirements, design considerations, and development details of the proposed system to detect and mitigate DDoS threats in 5G networks using edge computing. It defines the functional and non-functional requirements necessary for implementing the solution, emphasizing the capabilities and limitations of the proposed methodology.</p>
    </sec>
    <sec id="s4_2">
     <title>
      <xref ref-type="bibr" rid="scirp.145147-"></xref>4.2. Functional Requirements</title>
     <p>Functional requirements define the essential tasks and behaviors that the system must perform to achieve its objectives. In this research, the focus is on detecting and mitigating DDoS attacks using Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost as the machine learning model, while leveraging Multi-Access Edge Computing (MEC) and network traffic separation strategies.</p>
     <p>The functional requirements are as follows:</p>
    </sec>
    <sec id="s4_3">
     <title>4.3. Non-Functional Requirements</title>
     <p>Non-functional requirements focus on the overall quality, performance, and usability of a system rather than its core functions. These attributes are vital to ensure the Intrusion Detection System (IDS) for DDoS attacks operates effectively and remains practical in real-world 5G environments.</p>
     <p>The non-functional requirements for this research include:</p>
     <p>By addressing these non-functional requirements, the system not only fulfills its purpose but also ensures seamless integration into real-world scenarios, offering a reliable and scalable defense against DDoS attacks in the 5G network environment.</p>
    </sec>
    <sec id="s4_4">
     <title>4.4. Design</title>
     <p>The design of the proposed system focuses on detecting and mitigating DDoS attacks originating from compromised end-user devices within the 5G network. The system leverages Multi-Access Edge Computing (MEC), Zeek Intrusion Detection System (IDS), and a Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost-based detection model to analyze and filter malicious traffic. The core principle of the design ensures that legitimate and malicious traffic are separated, with a clear focus on precision and efficiency at the network edge.</p>
     <p>The design components and flow of the system are as follows:</p>
     <p>1) Malicious Traffic from End-User Devices: The traffic originates from end-user devices, which may be compromised and used to generate DDoS attacks. This malicious traffic is transmitted through the 5G Gateway and 5G Base Station (BTS) to the network.</p>
     <p>2) Traffic Segregation at Switch IN: All traffic, both legitimate and malicious, is directed to Switch IN. This switch serves as the entry point for analyzing traffic flows.</p>
     <p>3) Traffic Analysis at MEC Layer: At the Multi-Access Edge Computing (MEC) layer, the traffic is sent for analysis. The MEC is equipped with the Zeek IDS and the Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost detection models trained on the CIC-DDoS2019 dataset.</p>
     <p>4) Traffic Filtering and Containment:</p>
     <p>5) Traffic Isolation: To ensure precision, inbound and outbound traffic are managed using separate switches (Switch IN and Switch OUT). This prevents the mixing of good and bad traffic, enhancing detection accuracy and improving containment efficiency. In cases where a single switch is used for a Base Station (BTS), VLANs are configured to separate inbound and outbound traffic flows.</p>
     <p>Design Benefits:</p>
     <p>This design (<xref ref-type="fig" rid="fig2">
       Figure 2
      </xref>) ensures a robust, scalable, and efficient system for mitigating DDoS attacks, protecting the 5G network from disruptions caused by malicious end-user devices.</p>
     <fig id="fig2" position="float">
      <label>Figure 2</label>
      <caption>
       <title>Figure 2. System design for DDoS detection and mitigation in a 5G network.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId18.jpeg?20250826033334" />
     </fig>
     <p>A DDoS attack using a botnet is a coordinated cyber assault that aims to disrupt the normal functioning of a target server or network. In this type of attack, a botnet a network of compromised devices, often called “bots” is controlled by a central entity, such as a hacker or malware operator. Once an attack is initiated, these infected devices generate and send an overwhelming amount of traffic toward the target system, as illustrated in <xref ref-type="fig" rid="fig3">
       Figure 3
      </xref>.</p>
     <fig id="fig3" position="float">
      <label>Figure 3</label>
      <caption>
       <title>Figure 3. DDoS attack (Source: Akamai).</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId19.jpeg?20250826033335" />
     </fig>
     <p>The primary objective of a DDoS attack is to overwhelm the target’s resources, such as bandwidth, processing power, or memory, ultimately rendering services inaccessible to legitimate users. Botnets can include thousands or even millions of infected devices, amplifying the scale and severity of the attack. The consequences of such attacks are significant, often causing financial losses, operational disruptions, and reputational harm. These impacts make DDoS attacks a serious challenge for network administrators and security professionals, particularly within highly connected environments like 5G networks.</p>
     <p>The Detection and Mitigation Mechanism at the Multi-Access Edge Computing (MEC) layer is designed to handle incoming network traffic in real time. This system is created to detect Distributed Denial of Service (DDoS) attacks and block malicious traffic while ensuring legitimate traffic is forwarded seamlessly. The process is carried out step by step as shown in <xref ref-type="fig" rid="fig4">
       Figure 4
      </xref>.</p>
     <fig id="fig4" position="float">
      <label>Figure 4</label>
      <caption>
       <title>Figure 4. Detection and mitigation process at MEC.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId20.jpeg?20250826033337" />
     </fig>
     <p>Step 1: Start and Real-Time Traffic Collection</p>
     <p>All incoming traffic is collected continuously by the MEC layer from Inbound Switch. A Traffic Collector is used to monitor and capture live network traffic. This ensures that no packet bypasses the system. The traffic is prepared for further analysis.</p>
     <p>Step 2: Feature Extraction</p>
     <p>After the traffic is collected, important features are extracted from the packets. Attributes like packet size, protocol type, flow duration, and packet rate are analyzed and structured. This step is carried out in real-time to prepare the data for classification. The selected features are critical for distinguishing between legitimate and malicious traffic by providing insights into the flow characteristics of the network. By focusing on these key attributes, the model can efficiently identify patterns indicative of DDoS attacks. Accurate and timely feature extraction ensures the system’s responsiveness and effectiveness in detecting malicious traffic in real-world scenarios.</p>
     <p>Step 3: Feature Set Processing by the Trained Machine Learning Algorithm</p>
     <p>The extracted feature set is processed using the pre-trained Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost Machine Learning algorithm. This model was trained earlier on the CIC-DDoS2019 dataset. The features are analyzed, and the traffic is classified into two categories:</p>
     <p>The classification is performed quickly and efficiently using decision trees in the Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost models.</p>
     <p>Step 4: Confirmation of DDoS Attack</p>
     <p>If the traffic is classified as malicious, the system checks whether the patterns confirm a DDoS attack. If no attack is detected, the traffic is forwarded as legitimate. However, if a DDoS attack is confirmed, the system immediately moves to mitigation.</p>
     <p>Step 5: Mitigation of Malicious Traffic</p>
     <p>Mitigation measures are applied to block or reduce the impact of malicious traffic. Several actions are taken:</p>
     <p>These actions are carried out in real-time, ensuring that the network is protected without delays.</p>
     <p>Step 6: Forwarding Legitimate Traffic</p>
     <p>Traffic classified as legitimate is forwarded through the Outbound Switch to its intended destination or the core network. This ensures that normal users experience no disruptions and that valid traffic continues uninterrupted.</p>
    </sec>
   </sec>
   <sec id="s5">
    <title>
     <xref ref-type="bibr" rid="scirp.145147-"></xref>5. Project Description</title>
    <sec id="s5_1">
     <title>
      <xref ref-type="bibr" rid="scirp.145147-"></xref>5.1. Real-Time Detection of DDoS Attacks Using CIC-DDoS2019 and ML Classifiers</title>
     <p>This project focuses on designing an Intrusion Detection System (IDS) for detecting and mitigating DDoS attacks using machine learning techniques, specifically the Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost Classifier. The project utilizes the CIC-DDoS2019 dataset, a real-world dataset that contains diverse traffic patterns, including malicious and legitimate flows. The dataset is preprocessed to remove irrelevant columns, handle missing values, and prepare features for model training. The input features are analyzed, and the target labels (attack or normal) are defined for classification purposes. The data is split into training and testing sets, with 80% used for model learning and 20% for evaluation. A Random Forest (RF), K-Nearest Neighbor (KNN) and XGBoost model is trained to classify network traffic accurately, with performance assessed using metrics such as accuracy and a confusion matrix. Hyperparameter optimization is performed using GridSearchCV to improve the model’s performance. This project demonstrates how machine learning can be leveraged to detect malicious traffic patterns in real time, contributing to 5G network security. The structured approach ensures that the system is robust, scalable, and capable of effectively differentiating between normal and DDoS attack traffic.</p>
     <p>The first step involves importing all the necessary Python libraries (<xref ref-type="fig" rid="fig5">
       Figure 5
      </xref>) required for data loading, preprocessing, feature selection, model building, and evaluation. Libraries such as Pandas and NumPy form the backbone of data handling. Pandas is utilized to work with tabular data, enabling easy reading, cleaning, and manipulation of datasets. NumPy supports numerical operations, such as array handling and mathematical computations, which are essential for machine learning tasks.</p>
     <fig id="fig5" position="float">
      <label>Figure 5</label>
      <caption>
       <title>Figure 5. Importing python libraries.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId21.jpeg?20250826033340" />
     </fig>
     <p>For visualization, Matplotlib and Seaborn are imported. These libraries are used to create graphical representations, such as correlation matrices and confusion matrices, making it easier to analyze and interpret data patterns.</p>
     <p>From Scikit-learn, a comprehensive machine learning library, tools like train_test_split are used for splitting datasets into training and testing subsets. Preprocessing utilities such as StandardScaler and LabelEncoder standardize and encode data, ensuring it is suitable for model training. Feature selection is achieved using SelectKBest and mutual_info_classif, which identify the most relevant features for classification tasks.</p>
     <p>The machine learning models include RandomForestClassifier, KNeighborsClassifier, and XGBoost (from the XGBoost library). These algorithms are the core of the detection mechanism, trained to classify traffic as benign or malicious. The SMOTE library (Synthetic Minority Over-sampling Technique) is employed to handle class imbalances in the training data, ensuring the models perform effectively even with skewed datasets.</p>
     <p>Additional utilities like joblib enable saving and loading trained models, while evaluation metrics such as classification_report, confusion_matrix, roc_curve, and auc assess model performance. By importing these libraries at the start, a comprehensive toolkit is established for building a robust DDoS detection system.</p>
     <p>The dataset, CIC-DDoS2019, is loaded into the Python environment using the pd.read_csv() function from the Pandas library (<xref ref-type="fig" rid="fig6">
       Figure 6
      </xref>). This function reads the data from a CSV file and converts it into a DataFrame, a table-like structure that allows for easy access, analysis, and manipulation of the data.</p>
     <p>After loading, the script displays the column names using the columns attribute of the DataFrame, providing an overview of the dataset’s features. The shape of the dataset, representing the number of rows and columns, is displayed using the .shape attribute, giving an idea of the dataset’s size.</p>
     <fig id="fig6" position="float">
      <label>Figure 6</label>
      <caption>
       <title>Figure 6. Dataset path.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId22.jpeg?20250826033341" />
     </fig>
     <p>To explore the dataset (<xref ref-type="fig" rid="fig7">
       Figure 7
      </xref>) more effectively, the Pandas option display.max_columns is set to None, ensuring that all columns are visible when viewing the DataFrame. The dataset itself is printed, which allows a complete view of its structure, column names, and sample values.</p>
     <p>This preliminary exploration is essential for understanding the dataset and preparing for further analysis. Key details such as column names, data types, and the presence of missing values will be examined in subsequent steps to address any issues and prepare the data for modeling.</p>
     <fig id="fig7" position="float">
      <label>Figure 7</label>
      <caption>
       <title>Figure 7. Basic information about the dataset.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId23.jpeg?20250826033341" />
     </fig>
     <p>Missing or infinite values can cause problems during model training. To address this, infinite values were first replaced with NaN using the replace() function. Then, rows containing NaN values were removed using the dropna() function. This ensured that the dataset was clean and ready for analysis. Handling these values also helped prevent errors during the training process. The code below was used:</p>
     <p># Replace infinite values with NaN and drop rows with NaN values</p>
     <p>dataset.replace([np.inf, -np.inf], np.nan, inplace=True)</p>
     <p>dataset.dropna(inplace=True)</p>
     <p>The selected classes encompass a range of benign and malicious traffic, including denial-of-service attacks (DrDoS) targeting various protocols (DNS, LDAP, MSSQL, NTP, NetBIOS, SNMP, UDP), as well as other attack types such as LDAP, MSSQL, NetBIOS, Portmap, Syn, TFTP, UDP, UDP-lag, and WebDDoS. This selection enables the model to learn distinct patterns associated with these prevalent attacks, contributing to a more accurate and robust intrusion detection system. By concentrating on these specific classes, the research aims to provide valuable insights into their characteristics and improve mitigation strategies against them.</p>
     <p>selected_classes = ['Benign', 'DrDoS_DNS', 'DrDoS_LDAP', 'DrDoS_MSSQL', 'DrDoS_NTP', 'DrDoS_NetBIOS', 'DrDoS_SNMP', 'DrDoS_UDP', 'LDAP', 'MSSQL', 'NetBIOS', 'Portmap', 'Syn', 'TFTP', 'UDP', 'UDP-lag', 'UDPLag', 'WebDDoS']</p>
     <p>dataset = dataset [dataset ['Label'].isin(selected_classes)]</p>
     <p>The dataset included many features, but not all of them were equally useful for detecting DDoS attacks. A set of ten important features was selected based on domain knowledge and their relevance to network traffic. These features included Flow Duration, Total Fwd Packets, and Flow IAT Mean. By selecting only these features, the complexity of the dataset was reduced, and the model’s performance improved. The selected features are shown below:</p>
     <p>selected_features = ['Flow Duration', 'Total Fwd Packets', 'Total Backward Packets', 'Fwd Packet Length Max', 'Bwd Packet Length Max', 'Flow IAT Mean', 'Flow IAT Std', 'Flow IAT Max', 'Fwd Packets/s', 'Bwd Packets/s'] X = dataset [selected_features] y = dataset ['Label']</p>
     <p>Understanding the relationships between features is essential for improving the model’s accuracy. A correlation matrix was created to identify how features were related to one another. The matrix was visualized using a heatmap, which made it easier to see which features had strong correlations. Features with high correlation values often carry similar information, so this step also guided further feature selection. The correlation heatmap was created with the following code (<xref ref-type="fig" rid="fig8">
       Figure 8
      </xref>).</p>
     <p>To train and test the machine learning models, the dataset was divided into two parts: training data (80%) and testing data (20%). This split ensured that the models were trained on one set of data and evaluated on another. Stratified sampling was used to maintain a balanced distribution of classes in both subsets. The following code was executed for this step:</p>
     <p>X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.2, random_state=42, stratify=y)</p>
     <p>The dataset was imbalanced, meaning that some classes had significantly fewer samples than others. To address this, the Synthetic Minority Oversampling Technique (SMOTE) was applied to the training data. SMOTE created synthetic samples for the minority classes, making the dataset more balanced. A balanced dataset improves the model’s ability to detect all classes effectively.</p>
     <fig id="fig8" position="float">
      <label>Figure 8</label>
      <caption>
       <title>Figure 8. Correlation matrix of features.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId24.jpeg?20250826033348" />
     </fig>
     <p>Machine learning models perform better when features are on a similar scale. To achieve this, the StandardScaler was used to normalize the data. After normalization, all features had a mean of 0 and a standard deviation of 1. This step ensured that no feature dominated others due to differences in scale.</p>
     <p>The confusion matrices provide a visual assessment of the classification performance for three different machine learning models: Random Forest (RF), K-Nearest Neighbors (KNN), and XGBoost (XGB). Each matrix reveals the models’ strengths and weaknesses in accurately identifying various network traffic categories, including both benign traffic and different types of attacks.</p>
     <fig id="fig9" position="float">
      <label>Figure 9</label>
      <caption>
       <title>Figure 9. Random forest confusion matrix.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId25.jpeg?20250826033351" />
     </fig>
     <fig id="fig10" position="float">
      <label>Figure 10</label>
      <caption>
       <title>Figure 10. KNN confusion matrix.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId26.jpeg?20250826033351" />
     </fig>
     <fig id="fig11" position="float">
      <label>Figure 11</label>
      <caption>
       <title>Figure 11. XGBoost confusion matrix.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId27.jpeg?20250826033350" />
     </fig>
     <p>In this phase, the implementation of the Random Forest (RF), K-Nearest Neighbor (KNN), and XGBoost models was tested for their accuracy before deploying them in a Multi-Access Edge Computing (MEC) environment. MEC allows data to be processed closer to the network’s edge, significantly reducing latency and improving response times for real-time applications. This setup is particularly beneficial for applications that require fast detection and mitigation of network threats, such as Distributed Denial-of-Service (DDoS) attacks.</p>
     <p>Zeek, an open-source Intrusion Detection System (IDS), plays a key role in monitoring network traffic in real time. Zeek captures traffic flow data and extracts relevant features, such as Flow Duration, Total Fwd Packets, Fwd Packet Length Max, Flow IAT Mean, and Bwd Packets/s. These features are then sent to the pre-trained machine learning models (RF, KNN, and XGBoost) for classification. Based on the input features, the models predict whether the traffic is benign or malicious.</p>
     <p>In this phase, the models were tested by simulating DDoS attacks using Python code. When the models classify traffic, legitimate traffic is forwarded to the core network, while malicious traffic is blocked and contained at the MEC layer. This process is dynamic, occurring in real-time without the need for intermediate storage like CSV files, which allows immediate action against threats.</p>
     <p>The trained models and Python code were uploaded to a Virtual Private Server (VPS) for testing. The models were saved as .pkl files and loaded into the testing server, where they were used to simulate and analyze traffic. This setup ensures that the models can be tested under live conditions before full deployment.</p>
     <p>For future work, the goal is to integrate the trained machine learning models directly with Zeek in the MEC environment. This integration will enable seamless, real-time detection and mitigation of DDoS attacks. By leveraging the low-latency characteristics of MEC, this system aims to block malicious traffic as soon as it is detected, improving overall network security without relying on cloud resources or manual intervention.</p>
    </sec>
    <sec id="s5_2">
     <title>5.2. Testing the Models Using Python Script</title>
     <p>On an Ubuntu 22.04 LTS machine (<xref ref-type="fig" rid="fig12">
       Figure 12
      </xref>), the Python script mec_traffic_monitor.py was created and executed to simulate real-time traffic monitoring and classification. The pre-trained .pkl files for the Random Forest (RF), K-Nearest Neighbor (KNN), and XGBoost models, the models, along with the StandardScaler, were previously downloaded from Google Colab, were uploaded and placed in the same directory as the script. Using the python3 command, the script initiated a dynamic process to simulate traffic flows, with a portion of the traffic mimicking malicious DDoS attacks. Legitimate traffic was identified and forwarded, while malicious traffic was blocked, and the associated IP addresses were recorded in a file named blacklist.txt. A one-second delay (time.sleep(1)) was introduced to regulate the speed of classification, making the results easy to observe in the terminal. It is important to note that this is only a demonstration of the proposed idea. To fully implement this system in a real-world scenario, a complete software solution would need to be developed to run on the MEC layer, capable of handling live traffic streams with scalability and robustness.</p>
     <fig id="fig12" position="float">
      <label>Figure 12</label>
      <caption>
       <title>Figure 12. Result of demonstration.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId28.jpeg?20250826033352" />
     </fig>
    </sec>
    <sec id="s5_3">
     <title>5.3. Evaluation and Results</title>
     <p>In <xref ref-type="table" rid="table2">
       Table 2
      </xref>, we present the evaluation results for the Random Forest (RF), K-Nearest Neighbor (KNN), and XGBoost models, which were trained on the CIC-DDoS2019 dataset. The models were evaluated using key classification metrics, including precision, recall, F1-score, and accuracy. These metrics allow for a comprehensive understanding of the models’ effectiveness in classifying network traffic into benign and malicious categories.</p>
     <table-wrap id="table2">
      <label>
       <xref ref-type="table" rid="table2">
        Table 2
       </xref></label>
      <caption>
       <title>
        <xref ref-type="bibr" rid="scirp.145147-"></xref>Table 2. Classification report.</title>
      </caption>
      <table class="MsoTableGrid custom-table" border="0" cellspacing="0" cellpadding="0"> 
       <tr> 
        <td class="custom-bottom-td acenter" width="15.06%"><p style="text-align:center">Class</p></td> 
        <td class="custom-bottom-td acenter" width="9.43%"><p style="text-align:center">Precision (RF)</p></td> 
        <td class="custom-bottom-td acenter" width="9.43%"><p style="text-align:center">Recall (RF)</p></td> 
        <td class="custom-bottom-td acenter" width="9.44%"><p style="text-align:center">F1-Score (RF)</p></td> 
        <td class="custom-bottom-td acenter" width="9.43%"><p style="text-align:center">Precision (KNN)</p></td> 
        <td class="custom-bottom-td acenter" width="9.43%"><p style="text-align:center">Recall (KNN)</p></td> 
        <td class="custom-bottom-td acenter" width="9.44%"><p style="text-align:center">F1-Score (KNN)</p></td> 
        <td class="custom-bottom-td acenter" width="9.43%"><p style="text-align:center">Precision (XGBoost)</p></td> 
        <td class="custom-bottom-td acenter" width="9.43%"><p style="text-align:center">Recall (XGBoost)</p></td> 
        <td class="custom-bottom-td acenter" width="9.44%"><p style="text-align:center">F1-Score (XGBoost)</p></td> 
       </tr> 
       <tr> 
        <td class="custom-top-td acenter" width="15.06%"><p style="text-align:center">Benign</p></td> 
        <td class="custom-top-td acenter" width="9.43%"><p style="text-align:center">0.99</p></td> 
        <td class="custom-top-td acenter" width="9.43%"><p style="text-align:center">0.99</p></td> 
        <td class="custom-top-td acenter" width="9.44%"><p style="text-align:center">0.99</p></td> 
        <td class="custom-top-td acenter" width="9.43%"><p style="text-align:center">0.99</p></td> 
        <td class="custom-top-td acenter" width="9.43%"><p style="text-align:center">0.99</p></td> 
        <td class="custom-top-td acenter" width="9.44%"><p style="text-align:center">0.99</p></td> 
        <td class="custom-top-td acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="custom-top-td acenter" width="9.43%"><p style="text-align:center">0.98</p></td> 
        <td class="custom-top-td acenter" width="9.44%"><p style="text-align:center">0.99</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">DrDoS_DNS</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.51</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.40</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.45</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.45</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.47</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.46</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.46</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.33</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.38</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">DrDoS_LDAP</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.25</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.35</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.29</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.24</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.38</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.29</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.29</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.38</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.33</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">DrDoS_MSSQL</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.39</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.51</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.44</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.37</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.40</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.39</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.40</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.59</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.48</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">DrDoS_NTP</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.99</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.99</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">1.00</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">DrDoS_NetBIOS</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.05</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.08</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.06</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.16</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.20</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.18</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.05</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.06</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.05</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">DrDoS_SNMP</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.72</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.57</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.64</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.59</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.65</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.62</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.57</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.70</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.63</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">DrDoS_UDP</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.33</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.38</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.35</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.34</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.39</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.36</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.36</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.47</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.41</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">LDAP</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.38</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.58</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.46</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.30</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.13</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.18</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.34</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.49</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.40</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">MSSQL</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.54</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.41</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.47</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.52</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.53</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.53</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.58</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.40</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.47</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">NetBIOS</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.36</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.60</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.45</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.35</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.45</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.40</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.31</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.64</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.41</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">Portmap</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.23</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.29</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.25</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.22</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.30</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.25</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.19</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.36</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.25</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">Syn</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.99</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.98</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.99</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.96</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.92</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.94</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.99</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.98</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.99</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">TFTP</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">1.00</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">1.00</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">UDP</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.59</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.52</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.55</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.59</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.51</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.54</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.61</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.54</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.57</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">UDP-lag</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.69</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.74</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.72</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.48</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.60</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.53</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.87</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.75</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.81</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">UDPLag</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.12</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.45</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.20</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.06</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.27</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.10</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.06</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.73</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.12</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">WebDDoS</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.03</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.10</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.05</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.03</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.20</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.05</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.01</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.30</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.02</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">Accuracy</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.92</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.92</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.92</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.91</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.91</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.91</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.92</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.92</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.92</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">Macro avg</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.51</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.55</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.52</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.48</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.52</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.49</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.50</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.59</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.52</p></td> 
       </tr> 
       <tr> 
        <td class="acenter" width="15.06%"><p style="text-align:center">Weighted avg</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.92</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.92</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.92</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.91</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.91</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.91</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.93</p></td> 
        <td class="acenter" width="9.43%"><p style="text-align:center">0.92</p></td> 
        <td class="acenter" width="9.44%"><p style="text-align:center">0.92</p></td> 
       </tr> 
      </table>
     </table-wrap>
     <p>The evaluation of the three models revealed the following results:</p>
     <fig id="fig13" position="float">
      <label>Figure 13</label>
      <caption>
       <title>Figure 13. Performance comparison of models.</title>
      </caption>
      <graphic mimetype="image" position="float" xlink:type="simple" xlink:href="https://html.scirp.org/file/7801130-rId29.jpeg?20250826033354" />
     </fig>
     <p>The following performance comparison bar chart (<xref ref-type="fig" rid="fig13">
       Figure 13
      </xref>) illustrates the accuracy of the models. From the chart, we observe that Random Forest (RF) and XGBoost consistently outperformed KNN in terms of overall accuracy. Despite KNN performing well on certain traffic types, the more complex nature of some DDoS attacks required the more robust models, RF and XGBoost, to yield better results.</p>
     <p>The models performed well in distinguishing benign traffic from attacks such as DrDoS_NTP, Syn, and TFTP. However, the challenges were evident for attacks with low frequencies, such as DrDoS_LDAP and WebDDoS, where recall values were notably lower.</p>
    </sec>
   </sec>
   <sec id="s6">
    <title>
     <xref ref-type="bibr" rid="scirp.145147-"></xref>6. Conclusions</title>
    <p>This study focused on the detection and mitigation of Distributed Denial of Service (DDoS) attacks in 5G networks by leveraging machine learning algorithms. Specifically, Random Forest (RF), K-Nearest Neighbor (KNN), and XGBoost were used to classify traffic as benign or malicious. The approach aimed to address the vulnerabilities of 5G networks, particularly those arising from compromised end-user devices. While the project was conceptual, a Python script was used to demonstrate how these models can detect attacks, mimicking a real-world scenario. The CIC-DDoS2019 dataset served as a solid foundation for training and testing the models, allowing the system to identify and mitigate malicious traffic in real time. The results indicated that the proposed solution could improve network security and minimize service disruptions by detecting threats at the edge. Although the core components of the framework were validated, the research did not implement a fully operational system at the MEC layer, marking a clear area for future development.</p>
    <sec id="s6_1">
     <title>
      <xref ref-type="bibr" rid="scirp.145147-"></xref>6.1. Limitations</title>
     <p>Despite the positive results, the study faced several limitations. The most significant challenge is the cost of deploying Multi-Access Edge Computing (MEC) infrastructure at the edge of the network, which could impede its scalability in real-world applications. Moreover, the project did not result in a fully deployable solution that could run autonomously at the MEC layer. Although the machine learning models were validated, the implementation was limited to simulations and requires substantial development to transition into a practical deployment. Additionally, the research focused only on network-layer DDoS attacks, overlooking application-layer threats, which also pose considerable risks in 5G environments.</p>
    </sec>
    <sec id="s6_2">
     <title>
      <xref ref-type="bibr" rid="scirp.145147-"></xref>6.2. Future Works</title>
     <p>We successfully integrated the trained RF, KNN, and XGBoost models with Zeek IDS for real-time traffic monitoring and DDoS detection. Future work should focus on fully implementing this system at the MEC layer, ensuring it can autonomously process live traffic and mitigate attacks in real time. Additionally, research should aim to reduce the cost of MEC deployment by exploring shared infrastructure or optimizing resource allocation. Expanding the system to address application-layer DDoS attacks and incorporating other machine learning algorithms could enhance its accuracy and adaptability. This will make the system more robust against evolving threats, enabling it to effectively secure 5G networks at scale.</p>
    </sec>
   </sec>
  </sec>
 </body><back>
  <ref-list>
   <title>References</title>
   <ref id="scirp.145147-ref1">
    <label>1</label>
    <mixed-citation publication-type="other" xlink:type="simple">
     GSMA (2019) 5G and the Future: How 5G Research Is Transforming Our World. &gt;https://www.gsma.com/get-involved/gsma-membership/wp-content/uploads/2019/11/5G-Research_A4.pdf 
    </mixed-citation>
   </ref>
   <ref id="scirp.145147-ref2">
    <label>2</label>
    <mixed-citation publication-type="other" xlink:type="simple">
     Rinf.tech (2024) The IoT Security in the 5G Era. &gt;https://www.rinf.tech/the-iot-security-in-the-5g-era/ 
    </mixed-citation>
   </ref>
   <ref id="scirp.145147-ref3">
    <label>3</label>
    <mixed-citation publication-type="other" xlink:type="simple">
     Robustel (2024) How 5G Autonomous Vehicles Will Benefit from 5G. &gt;https://www.robustel.com/iot-technology-solutions-blog/how-5g-autonomous-vehicles-will-benefit-from-5g-1/ 
    </mixed-citation>
   </ref>
   <ref id="scirp.145147-ref4">
    <label>4</label>
    <mixed-citation publication-type="other" xlink:type="simple">
     Onoja, D., Hitchens, M. and Shankaran, R. (2022) DDoS Threats and Solutions for 5G-Enabled IoT Networks. In: Pal, S., Jadidi, Z. and Foo, E., Eds., Secure and Trusted Cyber Physical Systems, Springer, 115-133. &gt;https://doi.org/10.1007/978-3-031-08270-2_5
    </mixed-citation>
   </ref>
   <ref id="scirp.145147-ref5">
    <label>5</label>
    <mixed-citation publication-type="other" xlink:type="simple">
     Ghorbani, H., Mohammadzadeh, M.S. and Ahmadzadegan, M.H. (2020) DDoS Attacks on the IoT Network with the Emergence of 5G. 2020 International Conference on Technology and Entrepreneurship—Virtual (ICTE-V), San Jose, 20-21 April 2020, 1-5. &gt;https://doi.org/10.1109/icte-v50708.2020.9113779
    </mixed-citation>
   </ref>
   <ref id="scirp.145147-ref6">
    <label>6</label>
    <mixed-citation publication-type="other" xlink:type="simple">
     Serrano Mamolar, A., Salvá-García, P., Chirivella-Perez, E., Pervez, Z., Alcaraz Calero, J.M. and Wang, Q. (2019) Autonomic Protection of Multi-Tenant 5G Mobile Networks against UDP Flooding DDoS Attacks. Journal of Network and Computer Applications, 145, Article ID: 102416. &gt;https://doi.org/10.1016/j.jnca.2019.102416
    </mixed-citation>
   </ref>
   <ref id="scirp.145147-ref7">
    <label>7</label>
    <mixed-citation publication-type="other" xlink:type="simple">
     Sanmorino, A. and Yazid, S. (2013) DDoS Attack Detection Method and Mitigation Using Pattern of the Flow. 2013 International Conference of Information and Communication Technology (ICoICT), Bandung, 20-22 March 2013, 12-16. &gt;https://doi.org/10.1109/icoict.2013.6574541
    </mixed-citation>
   </ref>
  </ref-list>
 </back>
</article>