- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
RAISE is a post-training defense intended to reduce membership signals for designated fine-tuning records without rerunning the original fine-tuning procedure. It localizes spans with unusually low reference-relative loss, selects reference-quantile loss targets, and applies constrained model editing. The main experiment evaluates ten attacks across six domains and reports a mean AUC reduction from 0.855 to 0.576 and TPR at 1% FPR from 25.1% to 2.8%. Additional experiments examine localization, write layer, protection coverage, other model configurations, and trimmed-loss adaptive attacks.
Critical strengths
-
Protecting a selected set of audited records in an existing checkpoint is a useful practical setting. The paper states that the protection is empirical and limited to the designated records, and reference-relative localization is a plausible design that receives supporting ablations.
-
The primary before/after effect is substantial across six domains and ten attacks on the same evaluation records. Reporting per-attack/domain results, utility measurements, bootstrap variability, and additional model configurations provides more evidence than a single aggregate attack score.
Critical weaknesses
-
The comparative evidence does not yet establish how the defense's privacy–utility advantage varies across operating points. Table 2 gives one point per baseline on Pile-CC. NPO and RAISE have nearly matched perplexity (12.58 versus 12.59), which supports RAISE at that operating point. However, baseline hyperparameters and matched-utility sweeps are insufficiently documented; other comparisons, such as Forget-CE at perplexity 11.76, also change utility cost. A retrain-without-the-protected-set reference would calibrate both residual membership and utility in the small evaluated fine-tuning setup; it need not be a deployable defense to be useful as a reference. The judge-based utility experiment also needs its judge identity, prompts, question set, and variability. Without these details and a fair operating-point comparison, the large primary effect is promising but its advantage over existing post-training interventions is uncertain.
-
Several evaluation and specification gaps affect the broader protection claims. Table 9 includes below-chance post-edit AUCs: the Llama-3.2-3B SPV-MIA AUC 0.4063 corresponds to 0.5937 under score reversal. Applying max(AUC, 1−AUC) separately to its ten attacks gives mean 0.5441, compared with the reported one-sided mean 0.4989. This is an orientation-invariant diagnostic, not an operational attacker selected using test labels; an attacker should choose orientation using independent auxiliary data. Importantly, this issue does not overturn the main Table 1 results or by itself falsify the stated below-0.58 point estimates for the trimmed adaptive attacks, which remain below that threshold after reversal. It does require qualification of cross-model “near chance” interpretations and broader defense claims. Separately, Table 1's GitHub mean 0.625 and Table 7's selected-layer result 0.5865 need a run/configuration reconciliation, and the hidden-state objective and writeback specification need enough detail to reproduce the intervention.
Overall assessment: I currently lean against acceptance, narrowly. The main reduction is promising and the problem is useful, but fair privacy–utility comparisons, operationally calibrated attack evaluation, and reproducible intervention details are needed to assess the claimed advantage. Addressing these points could change my recommendation.
Questions for authors
- What privacy–utility curves do the baselines achieve under documented tuning, and how does RAISE compare at matched utility? What does a retrain-without-the-protected-records reference show?
- Please report both score orientations, with attack orientation/calibration chosen on independent data. Was the learned Ensemble attack trained or recalibrated on defended-model features? How does it perform as an adaptive attacker?
- What explains the GitHub 0.625-versus-0.5865 results? Please identify the run, evaluation population, default settings, and selected write layer for each.
- Given the module families specified in Appendix B.6, please identify the exact edited layer and its relationship to the target-search layer, and specify the complete hidden-state objective, request batching, preservation keys, and parameter-selection procedure. Appendix C.3 states that MIA outcomes were not used to choose the write layer; were evaluation attack outcomes used to tune other settings?
- Are the main evaluation non-members disjoint from the defender/reference pools and attack auxiliary data? Please provide the judge configuration, actual editing cost, and uncertainty across fine-tuning/edit seeds, beyond record bootstrap alone.