Open Brain
arXivPaperNeeds Review

Simulated Control Evals

Simulated tool responses predicted deployment-specific control safety more closely than a separate executed setting, offering a cheaper way to test agent safeguards before deployment.

arXiv · Oct 22, 2026
Open Source Open MarkdownOpen JSON
Source Summary

On LinuxArena, simulated control evaluations achieved **3.6 percentage-point RMSE** when predicting safety across five monitors at a 5% audit budget. BashArena, a separate executed control setting, reached **10.1 points**.

Practical Implication

Builders testing high-risk agents should model deployment-specific tools and tasks instead of relying only on a generic control environment. Simulation can also surface attack strategies that improve monitors on held-out executed attacks.

Agent-Ready Context
On LinuxArena, simulated control evaluations achieved **3.6 percentage-point RMSE** when predicting safety across five monitors at a 5% audit budget. BashArena, a separate executed control setting, reached **10.1 points**.

Builders testing high-risk agents should model deployment-specific tools and tasks instead of relying only on a generic control environment. Simulation can also surface attack strategies that improve monitors on held-out executed attacks.

SCEs explained **78–85% of between-environment variance** and used fewer than 5% as many task-pair draws as the deployment set. The evidence comes from LinuxArena, so transfer to other tools and workflows remains open.
Connected Context · Feed7 Judgment

This makes simulated control evaluation a cheaper, deployment-specific forecasting layer rather than a substitute for executed safety tests. It extends prior calls for small eval loops and adversarial testing by showing that modeled tools and tasks can explain much of the safety variation and generate attacks that improve monitors, while the Linux-only evidence leaves transfer to other agent environments unresolved.

EpiSEM-Bench: Evaluating Safety and Evidence Recovery in LLM Agents under Missing EvidenceEpiSEM-Bench isolates safe behavior under missing evidence, while simulated control evals address whether such control performance will transfer to a particular deployment environment; the latter can therefore complement capability-specific safety tests with environment-fit estimates.RedEvoAgent: Automatic Red-Teaming Agent with Experience-Driven Skill EvolutionBoth use evolving attack experience to strengthen safety evaluation: RedEvoAgent retains validated attack skills, while simulated control evals surface strategies that can improve monitors when tested on held-out executed attacks.How Evals and Prompts Shape Agent Behavior — Preetika Bhateja & Daniel Bump, YouTube AdsThe production loop of small eval sets and trace review gains a scaling mechanism here: simulation can cheaply sample deployment-shaped conditions, but executed checks remain necessary to calibrate whether those predictions hold.Vulnerability Localization Benchmark: Measuring Agentic Security Analysis at Repository ScaleVLoc Bench shows that security evaluation must isolate specific capabilities; this work adds that control results also depend on the surrounding tool-and-task environment, so both capability decomposition and deployment matching matter.
Context Map
benchmarkcodingsecurity#agent-evals#agent-reliability#tool-use
Uncertainty
SCEs explained **78–85% of between-environment variance** and used fewer than 5% as many task-pair draws as the deployment set. The evidence comes from LinuxArena, so transfer to other tools and workflows remains open.