mlsanityData to 14 Oct 2026

Benchmark Early and Red Team Often: A Framework for Assessing and Managing Dual-Use Hazards of AI Foundation Models

arXiv 2405.10986 ↗First posted 15 May 2024cs.CR cs.AI cs.CYcited by 9

On the map: LLM safety and security → Prompt injection and agent security

Abstract (arXiv)

A concern about cutting-edge or "frontier" AI foundation models is that an adversary may use the models for preparing chemical, biological, radiological, nuclear, (CBRN), cyber, or other attacks. At least two methods can identify foundation models with potential dual-use capability; each has advantages and disadvantages: A. Open benchmarks (based on openly available questions and answers), which are low-cost but accuracy-limited by the need to omit security-sensitive details; and B. Closed red team evaluations (based on private evaluation by CBRN and cyber experts), which are higher-cost but can achieve higher accuracy by incorporating sensitive details. We propose a research and risk-management approach using a combination of methods including both open benchmarks and closed red team evaluations, in a way that leverages advantages of both methods. We recommend that one or more groups of researchers with sufficient resources and access to a range of near-frontier and frontier foundation models run a set of foundation models through dual-use capability evaluation benchmarks and red team evaluations, then analyze the resulting sets of models' scores on benchmark and red team evaluations to see how correlated those are. If, as we expect, there is substantial correlation between the dual-use potential benchmark scores and the red team evaluation scores, then implications include the following: The open benchmarks should be used frequently during foundation model development as a quick, low-cost measure of a model's dual-use potential; and if a particular model gets a high score on the dual-use potential benchmark, then more in-depth red team assessments of that model's dual-use capability should be performed. We also discuss limitations and mitigations for our approach, e.g., if model developers try to game benchmarks by including a version of benchmark test data in a model's training data.

Key facts. Cited by 9 papers in the map (data through 14 Oct 2026). Placed in Prompt injection and agent security, one of 12 directions in LLM safety and security. First posted on arXiv 15 May 2024.

Builds on

0 of 0 references.

No references here yet.

Built on by

Cited by year (2026 to 14 Oct)

Citing papers per year: 2024: 5; 2025: 1; 2026: 3.

9 papers.

Similar, not cited

Close in wording, no citation either way

  1. 2025OpenAI's Approach to External Red Teaming for AI Models and Systems
  2. 2026A Translational Note on AI Safety Evaluation
  3. 2026Benchmark-Based Comparative Assessment of Publicly Benchmarked Indian Foundation Models: A Capability and Evaluation-Maturity Framework
  4. 2024RE-Bench: Evaluating frontier AI R&D capabilities of language model agents against human experts
  5. 2026Red Teaming LLMs as Socio-Technical Practice: From Exploration and Data Creation to Evaluation
  6. 2024The WMDP Benchmark: Measuring and Reducing Malicious Use With Unlearning
  7. 2025Safety by Measurement: A Systematic Literature Review of AI Safety Evaluation Methods
  8. 2026Comparison requires valid measurement: Rethinking attack success rate comparisons in AI red teaming