Minerval
Sourceunknowntext stored

AI Control: Improving Safety Despite Intentional Subversion

Greenblatt, Ryan, Shlegeris, Buck, Sachan, Kshitij, Roger, FabienarXiv.orgPublished Dec 12, 2023Original︎ ↗Archived copy

Claims3
ExaminationsNone
Text46 sections
VersionsOne known
CopiesNone recorded
CorrectionsNone recorded
Facts checked Nov 2, 2026
ReachNo copies recorded
StructureIn 3 claims' maps0 sources downstream across 3 claims
EvidenceNot yet read

Examinations

None recorded.

Text60 passages · 2 marked

No examination yetMarked passage
Skip to main content0 passages
Search1 passage
Log in0 passages
Search arXiv0 passages
Press Enter to search · Advanced search0 passages
Computer Science > Machine Learning2 passages
Title: AI Control: Improving Safety Despite Intentional Subversion0 passages
Authors: Ryan Greenblatt , Buck Shlegeris , Kshitij Sachan , Fabien Roger11 passages · 2 marked

Abstract: As large language models (LLMs) become more powerful and are deployed more autonomously, it will be increasingly important to prevent them from causing harmful outcomes. Researchers have investigated a variety of safety techniques for this purpose, e.g. using models to review the outputs of other models, or red-teaming techniques to surface subtle failure modes. However, researchers have not evaluated whether such techniques still ensure safety if the model is itself intentionally trying to subvert them. In this paper, we develop and evaluate pipelines of safety techniques ("protocols") that are robust to intentional subversion.

We investigate a range of protocols and test each against strategies that the untrusted model could use to subvert them. One protocol is what we call trusted editing. This protocol first asks GPT-4 to write code, and then asks GPT-3.5 to rate the suspiciousness of that code. If the code is below some suspiciousness threshold, it is submitted. Otherwise, GPT-3.5 edits the solution to remove parts that seem suspicious and then submits the edited code. Another protocol is untrusted monitoring. This protocol asks GPT-4 to write code, and then asks another instance of GPT-4 whether the code is backdoored, using various techniques to prevent the GPT-4 instances from colluding. These protocols improve substantially on simple baselines.

Focus to learn more1 passage
Submission history7 passages
View PDF1 passage
TeX Source8 passages
References & Citations0 passages
NASA ADS0 passages
Google Scholar0 passages
Semantic Scholar1 passage
BibTeX formatted citation3 passages
Bookmark0 passages
Bibliographic Tools0 passages
Bibliographic and Citation Tools0 passages
Bibliographic Explorer Toggle1 passage
Connected Papers Toggle1 passage
Litmaps Toggle3 passages
Code, Data, Media0 passages
Code, Data and Media Associated with this Article2 passages
Links to Code Toggle1 passage
DagsHub Toggle1 passage
GotitPub Toggle1 passage
Huggingface Toggle1 passage
ScienceCast Toggle1 passage
Demos0 passages
Demos0 passages
Replicate Toggle1 passage
Spaces Toggle1 passage
Spaces Toggle1 passage
Related Papers0 passages
Recommenders and Search Tools0 passages
Link to Influence Flower1 passage
Core recommender toggle1 passage
IArxiv recommender toggle1 passage
Author0 passages
Venue0 passages
Institution0 passages
Topic0 passages
About arXivLabs7 passages
Major funding support from0 passages

Lineage across 3 claims

Draws on · none recorded
This source
AI Control: Improving Safety Despite Intentional Subversion
in 3 claims' maps
Drawn on by · none recorded

Record

Kind
unknown
Authors
Greenblatt, Ryan, Shlegeris, Buck, Sachan, Kshitij, Roger, Fabien
Publisher
arXiv.org
Published
Dec 12, 2023
DOI
None
Link
https://arxiv.org/abs/2312.06942
Archived copy
https://web.archive.org/web/20261012025703/https://arxiv.org/abs/2312.06942
Stored text
5,551 characters, retrieved Nov 2, 2026 · 46 sections, 60 passages
Claims extracted
Versions
One known
Copies
None recorded
Corrections
None recorded
Facts checked
Nov 2, 2026

History 3

  1. Nov 2, 2026DividedSegmenter · Divided into 106 parts by its own structure
  2. Nov 2, 2026FactsFacts fetcher · Facts looked up
  3. Nov 2, 2026Entered the graphEntered the graph; copy stored