- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
APTI-FL detects federated backdoors using a small trusted server dataset. It searches for triggers that cause both natural and adversarially perturbed samples to predict the same target. It then checks which clients strengthen this response and excludes them from aggregation, using client history to stabilize the decisions. Experiments on five datasets show substantial reductions in attack success under CBA and DBA, including settings with a malicious-client majority.
Critical strengths
- The detection idea is reasonable. Testing what a client adds beyond the incoming global model can help distinguish new backdoor contributions from an inherited backdoor. Matched control inputs also help account for ordinary class preference.
- The results are promising within the tested settings. The evaluation covers five datasets and both centralized and distributed patch attacks, and shows that the full method can remain effective when malicious clients outnumber benign clients.
Critical weaknesses
- The baseline comparisons and ablations do not sufficiently establish the method’s added benefit. The main tables use 50% and 60% malicious-client ratios, which do not ensure a benign majority among participating clients. Several baselines depend on this condition; for example, FLAME explicitly assumes fewer than 50% malicious clients. Failure when this assumption is violated cannot by itself establish general superiority. The authors should state each baseline’s assumptions and add comparisons within its supported operating range. APTI-FL also uses 250 trusted server samples, but does not compare with FLTrust, which uses the same type of resource and is already cited. A comparison using the same trusted data is needed to judge whether the more complex design provides an additional benefit. Trigger inversion has been studied in prior work, but the paper does not sufficiently explain its improvements over existing methods. It should discuss representative inversion methods and clarify what adversarial guidance adds and which difficulty in the federated setting it addresses. The paper also does not directly test its key component: adversarial guidance. Fig.6 varies loss weights, but does not isolate the benefit of this component. Keeping the client-detection pipeline fixed, the authors could compare with an existing inversion method, remove PGD, or replace it with random perturbations. Such comparisons would help establish the added benefit of the proposed design.
- The experiments leave important operating conditions and costs untested. The malicious-client sweep begins at 40%, although Fig.4 already shows deterioration at that ratio in some cases. Results at 10–30% and with no attackers are important: weaker backdoor signals may be harder to invert, while benign-only training reveals unnecessary client exclusion. The paper also fixes the trusted dataset at 250 samples and does not test smaller or class-biased sets. The minimum Dirichlet parameter is 0.35; stronger label skew and actual client class distributions should be examined. Trigger inversion runs every round. The stated CIFAR-100 budget implies 9,000 discrete inversion optimizer steps per round, before other stages. Without measured runtime, it is difficult to judge whether the benefit justifies this recurring computation.
Questions for authors
- What attacker-fraction assumptions do the baselines make, and do they hold for the participating clients in these experiments? Can you add comparisons within their supported ranges and with FLTrust using the same trusted samples?
- What does the trigger-inversion design add over prior work? With the client-detection pipeline held fixed, how do results compare when using an existing inversion method, removing PGD, or replacing PGD with random perturbations?
- What are the results at 0–30% malicious clients, with smaller or class-biased trusted datasets, and under stronger label skew? Please include client FPR and clean accuracy.
- What are the measured per-round server time and peak memory, compared with FedAvg and a trusted-data baseline? Please state the hardware and participating-client count.