Beyond Attack Success Rate: Temporal Logit Observability for LLM Safety Failures
This paper introduces Temporal Logit Observability (TLO), a training-free diagnostic that analyzes temporal logit patterns during decoding to distinguish between different failure modes of LLM jailbreaks—providing deeper safety insights than traditional Attack Success Rate metrics and enabling effective early stopping without false alarms.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are a security guard at a very smart, polite robot factory. Your job is to stop the robots from saying anything dangerous when someone asks them a tricky question.
For a long time, the only way to check if your security system was working was to look at the final answer the robot gave. If the robot said "No, I can't do that," you marked it as a success. If it said "Sure, here is how," you marked it as a failure. This is what researchers call the Attack Success Rate (ASR).
The Problem: The "Yes/No" Blind Spot
The paper argues that this "Yes/No" check is like judging a movie only by its final scene.
- Scenario A: The robot starts to say "No," gets confused by a trick, and then says "Yes."
- Scenario B: The robot never even thinks about saying "No" and jumps straight to "Yes."
Both scenarios end with the robot saying "Yes." Under the old system, both are just "Failures." But they happened for totally different reasons. The old system can't tell the difference, so you don't know how to fix the robot.
The Solution: Watching the "Thought Process" (TLO)
The authors introduce a new tool called Temporal Logit Observability (TLO).
Think of the robot's "thought process" as a tug-of-war rope. On one end is the Refusal Team (saying "No"), and on the other is the Compliance Team (saying "Yes").
- Every time the robot picks a word, it pulls the rope slightly one way or the other.
- The old system only looked at where the rope ended up.
- TLO watches the rope move step-by-step as the robot speaks.
How TLO Works (The "2D Map")
Instead of just a single score, TLO plots the robot's performance on a 2D map with two axes:
- The "Before" Axis: Did the robot feel the pull of the "No" team before it even started speaking?
- The "During" Axis: Did the "No" team ever get a chance to pull the rope while the robot was talking?
By looking at this map, the researchers found something surprising:
- Two robots that had the exact same failure rate (e.g., both failed 50% of the time) were actually failing in completely different ways. One might have been confused right at the start, while the other started strong but gave up halfway through.
- The map acts like an X-ray, showing the hidden path the robot took to get to the wrong answer.
The "Early Stop" Trick
Because TLO can see the "No" team trying to pull the rope early in the conversation, the researchers built a simple safety rule:
- The Rule: "If the robot starts to pull the 'No' rope but then suddenly stops and switches to 'Yes' within the first few words, cut the power immediately."
- The Result: This simple rule stopped more than half of the successful attacks.
- The Bonus: It didn't accidentally stop the robot from answering normal, safe questions. It was like a motion detector that only trips when someone is sneaking around, not when someone is just walking through the door.
What the Paper Actually Says (and Doesn't Say)
- It does: Show that we can see how a safety failure happens just by looking at the numbers the robot uses to pick its words (logits), without needing to open the robot's brain (hidden states).
- It does: Prove that different robots fail in different patterns, even if they look the same on the surface.
- It does not: Claim this is a perfect, permanent fix for all AI safety issues.
- It does not: Say this works on every single type of robot or language (it focused on English and specific models).
- It does not: Suggest using this for medical diagnoses or other real-world critical systems yet. It is a diagnostic tool for researchers to understand why safety breaks.
In a Nutshell
The paper says: "Stop just checking the final answer. Watch the whole movie. By watching the robot's internal tug-of-war in real-time, we can spot failures earlier, understand why they happened, and stop them before the robot even finishes its sentence."
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.