Limits of AI safety monitors shown to stem from oversight not ability

The Oversight Gap: What LLM Safety Monitors Miss, and Why It Is Not Capability

Machine LearningCryptography and Security

Summary

AI safety monitors are tools meant to catch tricky problems in large language models (LLMs) by checking for certain safety issues. The authors show that some safety properties need comparing two runs to detect, but single-run monitors struggle because they can only guess how likely differences are. They define an "oversight gap" measuring how much these monitors miss, and find most of the gap isn’t due to the AI’s ability but to not knowing exactly what to check or lacking proper procedures. They show that having clear information about what to compare greatly improves detection, and that re-running tests or storing extra info is crucial. This means improving AI safety requires better oversight methods, not just more capable models.

large language modelssafety monitors2-safety hyperpropertiestotal variation distanceoversight gapnoninterferencenondeterminismreplaybenchmark validity

Authors

Xin Xu

Abstract

Several properties safety monitors are asked to certify, among them cross-tenant noninterference, sandbagging and evaluation awareness, are 2-safety hyperproperties, witnessed only by two executions. The standard consequence is a binary impossibility: one trace cannot decide them. We replace the binary with a measurement. A tight bound puts the balanced accuracy of any single-trace monitor at $\tfrac12+\tfrac12\,TV(P_0,P_1)$, turning undecidability into a graded detectability frontier and defining an oversight gap: a monitor's shortfall below it. On a leak family with closed-form $TV$, nine LLM monitors are optimal at $TV=0$ but capture little signal as $TV$ grows; at $TV=1$, where a 20-line membership check scores $100\%$, they average $60.9\%$. That shortfall is mostly not capability: naming what to check closes $61\%$ of it while leaving the $TV=0$ control at chance. The same split runs through a $2{\times}2$ factorial: an imagined second run leaves monitors at chance ($50.4\%$) while the same rule on an executed second run reaches $90.0\%$, and a stored oracle without a comparison procedure yields only $68.2\%$. Information and procedure are each necessary and neither is capability. Under nondeterminism, replay tracks a closed-form $k$-replay curve only under the right projection, and a projection frontier shows the resulting dilemma is forced: narrow misses $98.6\%$ of off-channel leaks, broad flags $75.7\%$ of clean traffic, and attainable accuracy decays like $1/(qm)$ in the benign-variation rate and the channel count. Finally, two frontier LLM judges certified an earlier version of our own benchmark as sound while a sign test found a directional bias ($p=2.7\times10^{-5}$) that invalidated three of our findings. Construction validity for hyperproperty benchmarks should be proved mechanically, not audited by models.