<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud-Native Architecture |</title><link>https://integraceion.com/tags/cloud-native-architecture/</link><atom:link href="https://integraceion.com/tags/cloud-native-architecture/index.xml" rel="self" type="application/rss+xml"/><description>Cloud-Native Architecture</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Mon, 27 Oct 2025 00:00:00 +0000</lastBuildDate><image><url>https://integraceion.com/media/icon_hu_623a664287f5d0d2.png</url><title>Cloud-Native Architecture</title><link>https://integraceion.com/tags/cloud-native-architecture/</link></image><item><title>Assessing the Energy and Resilience Trade-offs of Service Mesh Integration and DDoS Mitigation in a Cloud-Native 5G Environment</title><link>https://integraceion.com/projects/msc-thesis/</link><pubDate>Mon, 27 Oct 2025 00:00:00 +0000</pubDate><guid>https://integraceion.com/projects/msc-thesis/</guid><description>&lt;h2 id="research-context-securing-the-cloud-native-5g-core"&gt;Research Context: Securing the Cloud-Native 5G Core&lt;/h2&gt;
&lt;p&gt;The telecommunications sector is undergoing a profound transformation as 5G networks embrace cloud-native technologies and a Service-Based Architecture (SBA). In this modern paradigm, monolithic infrastructure has been replaced by containerized, modular Network Functions (NFs) that communicate via HTTP/2 APIs and are orchestrated by platforms like Kubernetes.&lt;/p&gt;
&lt;p&gt;While this virtualization enables unprecedented scalability and automation, it also introduces immense signaling complexity. A single procedure - such as a user registration - now triggers dozens of distributed API calls across the network. This decoupled nature drastically expands the attack surface, making the Control Plane highly vulnerable to signaling storms and Distributed Denial of Service (DDoS) attacks.&lt;/p&gt;
&lt;p&gt;Furthermore, as the industry&amp;rsquo;s research pushes toward 6G, environmental and economic sustainability have emerged as essential design parameters alongside ultra-low latency and reliability. Telecom operators now face a critical dilemma: &lt;strong&gt;How can they deploy robust, dynamic security in the Control Plane without violating green energy goals or inflating operational costs?&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id="thesis-objectives"&gt;Thesis Objectives&lt;/h3&gt;
&lt;p&gt;To address the complexity of distributed signaling, 3GPP introduced the Service Communication Proxy (SCP) as a centralized broker for inter-NF communication. This Master&amp;rsquo;s thesis leverages the SCP concept by integrating an Istio Service Mesh, utilizing Envoy sidecar proxies to enforce zero-trust security (mTLS) and provide unified Layer 7 observability.&lt;/p&gt;
&lt;p&gt;The primary objective of this research was to design a custom experimentation platform and an intelligent anomaly detection algorithm capable of dynamically mitigating signaling-level DDoS attacks, specifically registration floods. Secondarily, the study aimed to empirically quantify the exact &amp;ldquo;energy cost of resilience&amp;rdquo; by measuring the power overhead introduced by the Service Mesh under varying network loads.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="custom-experimentation-platform"&gt;Custom Experimentation Platform&lt;/h2&gt;
&lt;p&gt;To conduct this research, a comprehensive, fully decoupled 5G testbed was engineered from the ground up. The platform leveraged a modern open-source software stack deployed on a bare-metal Kubernetes cluster, provisioned via Proxmox Virtual Environment to ensure near-native performance and strict resource isolation.&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th style="text-align: left"&gt;Component&lt;/th&gt;
&lt;th style="text-align: left"&gt;Technology&lt;/th&gt;
&lt;th style="text-align: left"&gt;Implementation Details&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align: left"&gt;&lt;strong&gt;5G Core&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align: left"&gt;Open5GS&lt;/td&gt;
&lt;td style="text-align: left"&gt;Containerized Release-17 implementation for 5GC, strictly enforcing 3GPP Model D communication where the SCP acts as the centralized broker.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align: left"&gt;&lt;strong&gt;RAN Simulation&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align: left"&gt;UERANSIM&lt;/td&gt;
&lt;td style="text-align: left"&gt;Simulated 5G User Equipment (UE) and Next Generation Node B (gNB) to generate massive signaling loads.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align: left"&gt;&lt;strong&gt;Service Mesh&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align: left"&gt;Istio&lt;/td&gt;
&lt;td style="text-align: left"&gt;Handled centralized routing control, unified Layer 7 observability, and mandatory mutual TLS (mTLS) encryption via Envoy sidecars.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align: left"&gt;&lt;strong&gt;Telemetry&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align: left"&gt;Prometheus, Grafana &amp;amp; Kepler&lt;/td&gt;
&lt;td style="text-align: left"&gt;Centralized time-series metrics collection, unified observability dashboards, and eBPF-based pod-level energy estimation.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;hr&gt;
&lt;h2 id="dynamic-anomaly-detection--mitigation"&gt;Dynamic Anomaly Detection &amp;amp; Mitigation&lt;/h2&gt;
&lt;p&gt;The core innovation of this thesis was the design and validation of a proprietary, metric-based anomaly detection framework tailored specifically for the 5G Control Plane.&lt;/p&gt;
&lt;p&gt;A registration flood - where misbehaving UEs repeatedly perform registration and deregistration procedures - can quickly exhaust Control Plane resources (CPU, Memory, Network Bandwidth) and degrade service for legitimate users. To combat this, a custom Python-based backend was developed to constantly monitor telemetry and enforce a dynamic rate-limiting strategy directly within the Kubernetes environment.&lt;/p&gt;
&lt;h3 id="the-detection-algorithm"&gt;The Detection Algorithm&lt;/h3&gt;
&lt;p&gt;The custom algorithm evaluates real-time metrics against historical data to distinguish between legitimate high-demand traffic and sustained malicious behavior:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Historical Context:&lt;/strong&gt; The system queries Prometheus every 10 seconds, maintaining a memory buffer of the 100 most recent median network usage records for each UE workload.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Threshold Identification:&lt;/strong&gt; A pod is flagged as suspicious if its current metric exceeds a predefined threshold factor (set to 2.5) multiplied by its current median.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sustained Anomaly Verification:&lt;/strong&gt; To prevent false positives, the quarantine mechanism is strictly activated only after 5 consecutive spikes, equating to at least 50 seconds of sustained abnormal behavior.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dynamic Mitigation:&lt;/strong&gt; Because UERANSIM bridges all simulated UE traffic to the pod&amp;rsquo;s single &lt;code&gt;eth0&lt;/code&gt; interface, fine-grained control per UE was not feasible without a specialized CNI plugin. Therefore, once a policy violation is confirmed, the offending UE pod is rate-limited at the network interface level for a 5-minute duration.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Adaptive Median Adjustment:&lt;/strong&gt; During the quarantine period, the system continues to update the pod&amp;rsquo;s median record; if the traffic originates from legitimate high volume, the median adjusts upwards to prevent blind re-banning once the policy expires.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="results"&gt;Results&lt;/h3&gt;
&lt;p&gt;When tested against a simulated 100-UE registration flood, the framework successfully detected the anomaly and triggered the Fair-use policy. The enforcement of the rate-limit resulted in a &lt;strong&gt;~50% reduction in signaling traffic&lt;/strong&gt; directed at critical core Network Functions, heavily mitigating the load on the Access and Mobility Management Function (AMF) and the Session Management Function (SMF).&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="service-mesh-energy-impact-assessment"&gt;Service Mesh Energy Impact Assessment&lt;/h2&gt;
&lt;p&gt;While the Service Mesh provided crucial Layer 7 security and observability, injecting Envoy sidecars into every pod inherently introduces operational overhead. The secondary objective of this study was to empirically quantify this environmental cost to address the gap in understanding the true OPEX of cloud-native 5G adoption.&lt;/p&gt;
&lt;p&gt;Using Kepler, which utilizes eBPF to probe CPU performance counters and Linux kernel tracepoints, the energy consumption of a plain Open5GS core was benchmarked against a Service Mesh-enabled core under varying levels of signaling load (from 10 to 100 concurrent UEs).&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Idle Overhead:&lt;/strong&gt; At an idle state, the sidecar proxies introduced a baseline energy overhead of &lt;strong&gt;9.3%&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Active Load Scalability:&lt;/strong&gt; As signaling traffic volume increased, the proxy overhead scaled accordingly due to the computational demands of L7 routing and cryptographic mTLS processing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Peak Consumption:&lt;/strong&gt; Under heavy signaling load (50 to 100 UEs), the energy overhead gap widened and stabilized at approximately &lt;strong&gt;33.6% to 34.1%&lt;/strong&gt; additional power consumption compared to the naked 5G core.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These findings establish tangible, quantitative data on the operational expenditure of cloud-native adoption, providing a clear picture of the energy required to gain the security and resilience benefits of a Service Mesh in a 5GC deployment.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="-resources--artifacts"&gt;🔗 Resources &amp;amp; Artifacts&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Thesis Document:&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Code Repository:&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>