- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper audits two LLM attack detectors and examines whether their alerts measure the intended behavior. For DualSentinel, the authors find that its real-time implementation repeatedly reads the first token rather than the current token, and the results also depend on retained state and can flag legitimate tasks. For ICLScan, they show that its benchmark can keep producing the same attack alerts even after much of the scoring rule is removed, largely because the benchmark targets contain overlapping wording. Based on these findings, the paper proposes a practical audit procedure to bridge these gaps.
Critical strengths
-
The paper finds concrete, consequential problems in two released detectors.
-
The paper turns the case studies into a simple set of checks. This provides a concrete way to catch misleading detector results.
Critical weaknesses
-
The main findings are based on a fairly narrow set of cases, and some of the results/conclusions do not hold in the additional tests. For example, the strongest DualSentinel result comes from a synthetic task set on one model. In another test on the same model, the detector can catch some attacks without flagging legitimate tasks, and the results on the other model also look different. It is unclear to me whether the authors found a broader problem with the detector or just a problem with a particular setup.
-
Another weakness is about the proposed auditing procedure. I think the proposed procedure is useful, but many of its core ideas are fairly general evaluation principles and they lack a structure overall. This brings two issues: (1) the gaps being filled are driven by the two case studies, so it's unclear how comprehensive and generalizable they are; and (2) the design of this procedure lacks a sense of systematic analysis in general.
Questions for authors
- Are the proposed audit steps intended as a general protocol for LLM attack detectors, or mainly for detectors with structures similar to DualSentinel and ICLScan? I have this question because some steps (e.g., checking state lifetime or keyword redundancy) are very specific to these systems.
No response from the authors
The authors chose not to include any response, so I will keep my original scores.