- Rating
- 3
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper studies how query pricing can limit model extraction while controlling the extra cost to benign users. It analyzes how query rewriting and observable features affect pricing, and proposes FGP to select a pricing policy under protection and cost constraints, with the option to abstain from deployment. The experiments cover classification, recommendation, and language models, including evaluations with trained student models.
Critical strengths
-
The theory addresses relevant aspects of the problem. It accounts for attackers rewriting queries to reduce their charges and explains why protecting against extraction can also increase costs for benign users.
-
The experiments are broad, with rewriting attacks, adaptive attacks, and comparisons with other defenses. Evaluating trained students and reporting cases where deployment is unsuitable make the findings more convincing.
Critical weaknesses
-
The practical effectiveness still depends on how attacker query value is estimated. The theory assumes that an attacker buys a query when its value exceeds its price, while the experiments mainly measure value through entropy or query counts. These measures may not reflect what an attacker is willing to pay. Adaptive attacks are already considered, but it remains unclear how well the pricing holds up when the attacker uses a different value estimate.
-
The stability of capability-based deployment decisions could be better established. This evaluation selects policies using the mean plus one standard error and reports results on one seed split. All nine deployments meet their targets in held-out mean performance, which is encouraging. However, some results are close to the boundary, such as the 0.6 target on CIFAR. Repeating the split would help establish whether these decisions are stable.
-
Some preprocessing choices need to be ruled out as factors in the language-model results. The appendix notes that output entropy includes generation steps after individual responses have ended. The GSM8K experiments also use different generation limits for benign and attacker prompts. These choices may affect the output features and pricing comparisons. The authors acknowledge these limitations, but results with consistent preprocessing would strengthen this part of the evaluation.
Questions for authors
-
With the pricing rule fixed, does protection remain effective when the attacker uses a different estimate of query value?
-
Are the nine deployment and six abstention decisions consistent across repeated splits of the selection and evaluation seeds?
-
Do the relevant pricing comparisons and deployment decisions change when entropy is computed only up to each response’s stopping point and GSM8K uses the same generation limit for benign and attacker prompts?
2 comments
Thank you for the additional checks and clarifications. These address my concerns, and I will maintain my positive rating.
Thank you for suggesting these checks on the stability of our results.
Q1. With the pricing rule fixed, does protection remain effective when the attacker uses a different estimate of query value?
Both positive-spend MovieLens deployments still meet their capability targets under the alternative extraction-value proxy. We hold the pricing rules fixed and replace unit value per query with uncertainty from a separate SASRec surrogate. The attacker ranks the entire pool by uncertainty per unit surcharge. At the original budgets, held-out mean remaining capability is 0.684 at target 0.8 and 0.528 at target 0.6. Both meet their targets. MovieLens-0.4 is unchanged at zero spend (0.3775). It misses when the attacker can spend 12.5% of the pool's total surcharge. That test changes both the budget and how the attacker buys.
At equal spend, three of four positive-spend deployments still pass across all three tested purchase strategies. CIFAR-0.6 is the sole exception: changing how the attacker buys raises the mean from 0.5995 to 0.6023 even though its extraction-value proxy stays fixed.
With the new purchase strategies in the selection screen, FGP can select a different pricing policy or abstain. In the separate budgeted selection test, it selects a pricing policy for CIFAR-0.6 that passes on held-out seeds (burden 0.70, worst mean 0.572) and abstains on MovieLens-0.4 with the original candidate menu (Appendix C.4).
Q2. Are the nine deployment and six abstention decisions consistent across repeated splits of the selection and evaluation seeds?
Most deploy-or-abstain decisions are stable across splits. CIFAR-0.6 is the main exception: the original margin of one standard error of the mean (SEM) let a policy qualify even when the selection mean was close to the capability target. We keep that primary analysis and run a stricter 1.645-SEM screen with the same FGP procedure. The policy at burden 0.70 also meets the target when evaluated on 50 new seeds.
We first repeated the original selection and evaluation. Across 2,000 splits, seven of nine CIFAR, MovieLens, and Beauty workload-target pairs always make the same deploy-or-abstain decision, and every deployment for those seven pairs meets its target. Among the other two pairs, MovieLens-0.4 misses in 0.3% of deployments and CIFAR-0.6 in 14.2%, with a median excess of 0.0044 for CIFAR-0.6.
On the reported split, the stricter screen changes the CIFAR-0.6 selection from burden 0.55 to 0.70 and preserves all nine passing deployments (Appendix C.3). In the separate test against four purchase strategies on 50 new seeds, the highest held-out mean remaining capability is 0.576. The highest mean plus 1.645 SEM is 0.597, still below 0.6. The policy at burden 0.65 meets the target on its mean but not with the margin (0.607). This test validates the policy at 0.70. Selection still varies across seed sets (Appendix C.4).
On broad instruction at target 0.8, FGP deploys on all 12,870 splits and meets the target in 96.8% of them. At targets 0.6 and 0.4, FGP abstains over 99% of the time. The revised evaluation has nine passing deployments and three abstentions on the reported split: the three former GSM8K abstentions are no longer part of the capability evaluation, as explained below.
Q3. Do the relevant pricing comparisons and deployment decisions change when entropy is computed only up to each response's stopping point and GSM8K uses the same generation limit for benign and attacker prompts?
Correcting entropy does not change the comparison between demand rarity and the output signature on broad instruction. FGP reruns the same selection screen with the corrected data and the same capability targets and burden cap. The deploy-or-abstain decisions on the reported split stay the same.
At the same benign burden of 0.4, demand rarity still reduces imitation fidelity more than the output signature. Held-out negative log-likelihood (NLL) is higher by 0.010 for the 3B victim and 0.015 for the 7B victim. A higher NLL means the student imitates the victim less closely. On the reported split, FGP still deploys at 0.8 and abstains at 0.6 and 0.4. At 0.8, it switches from demand rarity (held-out mean 0.752) to the portfolio (0.767), with both policies meeting the capability target in their respective evaluations.
We recomputed entropy by replaying each recorded answer (teacher forcing) through its own stopping point, including the end-of-sequence token when emitted, and retrained the affected students. On GSM8K, we also used the same 256-token limit for benign and attacker queries. After these corrections, the portfolio reaches blocked-value targets up to 0.85 at benign burden at most 0.04. This measures blocked value, not a reduction in student capability. We keep GSM8K in the query-level evaluation because its measured capability range is small relative to seed variability.