In-network Attack Detection with Federated Deep Learning in IoT Networks: Real Implementation and Analysis

cs.LG cs.CR Devashish Chaudhary, Sutharshan Rajasegarar, Shiva Raj Pokhrel, Lei Pan, Ruby D · Mar 23, 2026
Local to this browser
What it does
This paper addresses the challenge of detecting network attacks in IoT environments while preserving data privacy and minimizing communication overhead. The authors propose a federated learning framework using lightweight autoencoders...
Why it matters
A real-world testbed with ZigBee-enabled sensor nodes was constructed to evaluate the approach against redirection attacks, demonstrating that federated training can match centralized performance while significantly reducing data...
Main concern
The paper presents a credible real-world implementation of federated anomaly detection on resource-constrained devices, offering valuable empirical validation beyond simulation studies. The experimental setup using Raspberry Pi nodes with...
Community signal
0
0 up · 0 down
Sign in to vote with arrows
AI Review AI reviewed
Plain-language introduction

This paper addresses the challenge of detecting network attacks in IoT environments while preserving data privacy and minimizing communication overhead. The authors propose a federated learning framework using lightweight autoencoders deployed directly on Raspberry Pi edge devices to detect anomalies in real-time through reconstruction error $\mathcal{E}(t)=\|x_{t}-\hat{x}_{t}\|^{2}$. A real-world testbed with ZigBee-enabled sensor nodes was constructed to evaluate the approach against redirection attacks, demonstrating that federated training can match centralized performance while significantly reducing data transmission from 4.5 MB to 378 KB.

Critical review
Verdict
Bottom line

The paper presents a credible real-world implementation of federated anomaly detection on resource-constrained devices, offering valuable empirical validation beyond simulation studies. The experimental setup using Raspberry Pi nodes with XBee modules provides practical insights into edge-based detection, though the evaluation is constrained to a small-scale network of only nine nodes and a single attack vector. While the communication savings and privacy benefits are convincingly demonstrated, the limited scope of the attack scenarios and inconsistent performance across network positions prevent broader generalizability claims.

“A real-world IoT testbed using Raspberry Pi sensor nodes was developed to collect normal and attack traffic data.”
paper · Abstract
What holds up

The physical deployment on actual hardware (Raspberry Pi 3B+ with XBee S2C modules) lends credibility often missing in simulation-only studies, with clear documentation of the hierarchical network topology. The communication overhead analysis is concrete and well-quantified, demonstrating that federated learning requires only 378 KB compared to 4.5 MB for centralized learning over a 5-hour period. The autoencoder architecture is appropriately lightweight for resource constraints, with model weights requiring only 12.6 KB per transmission, and the FedAvg aggregation $W_{t+1}^{\text{global}}=\frac{1}{K}\sum_{k=1}^{K}W_{t}^{(k)}$ is correctly implemented.

“the federated learning method significantly reduces the communication overhead compared to the centralized method. Specifically, federated learning requires only 378 KB of data transfer over 5 hours, whereas the centralized method requires 4.5 MB.”
paper · Section V-E
Main concerns

The study is critically limited to redirection attacks only, explicitly acknowledging that "other attacks, such as DoS, DDoS, packet injection, or spoofing exist" but excluding them from evaluation. Performance varies dramatically across routers, with R3 achieving maximum F1-scores of only 0.4358 (federated) and 0.5870 (centralized) compared to R1's 0.8963 and 0.9012, suggesting the model struggles with certain network positions or traffic patterns that are not adequately analyzed. The threshold selection method using $\text{Threshold}=\text{Mean}+k\times\text{Standard Deviation}$ with $k \in \{1,2,3,4\}$ appears arbitrary, requiring different optimal $k$ values for each router in the federated setting (R1: $k=4$, R2: $k=1$, R3: $k=2$) without theoretical justification for this heterogeneity.

“Redirection attacks were chosen because they effectively alter network routing patterns... other attacks, such as DoS, DDoS, packet injection, or spoofing exist”
paper · Section IV
“R3 Federated k=2 F1: 0.4358; R3 Centralized k=4 F1: 0.5870”
paper · Table III
Evidence and comparison

The comparison between federated and centralized approaches is methodologically fair, with both using identical autoencoder architectures (31 input features, encoder layers of 32 and 16 neurons) and training hyperparameters (100 epochs, batch size 32, learning rate 0.001). However, the paper lacks comparison against other anomaly detection baselines such as isolation forests or one-class SVMs, or against alternative federated optimization algorithms beyond FedAvg. The claim that the method can detect "other attacks, such as Denial of Service (DoS) and man-in-the-middle" is speculative, as the authors admit these were not actually tested in the real network, limiting the validity of such generalization claims.

“In addition to redirection attacks, the proposed method can also detect other attacks, such as Denial of Service (DoS) and man-in-the-middle. Future work will include testing these attacks in real networks.”
paper · Section VI
Reproducibility

The hardware specifications and network topology are well-documented, including Raspberry Pi 3B+ platforms, XBee S2C modules, and the Python/Digi API software stack. Feature extraction is clearly described (31 features including delay metrics, Shannon entropy, and hop counts) and the model architecture is specified using Keras Functional API. However, no code repository or dataset link is provided, and the specific implementation details of the AT-command-based attacks are insufficient for full reproduction. The complexity analysis provides theoretical bounds $O(e \cdot m \cdot d^2)$ for training but omits actual measured latency, energy consumption, or memory utilization statistics from the physical devices.

“Each node is built on a Raspberry Pi 3B+ platform and equipped with an XBee S2C ZigBee radio module”
paper · Section III
“training the autoencoder on local data at each edge device involves $O(e*m*d^{2})$ operations”
paper · Section V-F
Abstract

The rapid expansion of the Internet of Things (IoT) and its integration with backbone networks have heightened the risk of security breaches. Traditional centralized approaches to anomaly detection, which require transferring large volumes of data to central servers, suffer from privacy, scalability, and latency limitations. This paper proposes a lightweight autoencoder-based anomaly detection framework designed for deployment on resource-constrained edge devices, enabling real-time detection while minimizing data transfer and preserving privacy. Federated learning is employed to train models collaboratively across distributed devices, where local training occurs on edge nodes and only model weights are aggregated at a central server. A real-world IoT testbed using Raspberry Pi sensor nodes was developed to collect normal and attack traffic data. The proposed federated anomaly detection system, implemented and evaluated on the testbed, demonstrates its effectiveness in accurately identifying network attacks. The communication overhead was reduced significantly while achieving comparable performance to the centralized method.

Challenge the Review

Pick a starting point or write your own. Challenges run in the background, so you can keep reading while the AI investigates.

No challenges yet. Disagree with the review? Ask the AI to revisit a specific claim.