What Is AI Safety and How Is It Measured in AI Research?
Updated
AI safety is the part of AI research that studies how models behave in risky or high-stakes situations and how to measure and reduce harm before and after deployment. It is closely tied to evaluation (how capability and risk are tested) and alignment (whether model behavior matches human intent and values). Scale Labs, for example, lists safety alongside agents, post-training, reasoning, evaluation, and alignment as a core research focus, and publishes safety benchmarks such as DistressBench.
What AI Safety Covers
AI safety is broader than "does the model refuse bad requests." It spans three layers:
- Model behavior: harmful outputs, unsafe refusals, sycophancy, and failure in sensitive contexts such as crisis support.
- Deployment risk: how agents behave when given tools, autonomy, or enterprise workflows, and whether failures are contained.
- Safety capability: whether a model can recognize risk, respond appropriately, and remain reliable under adversarial or ambiguous input.
This is why safety work overlaps with evaluation and alignment but is not identical to either.
Safety, Alignment, and Evaluation: How They Differ
| Concept | Core question | Typical output |
|---|---|---|
| AI safety | What can go wrong, and how do we measure and reduce harm? | Safety benchmarks, risk taxonomies, guardrails |
| Alignment | Does model behavior match human intent and values? | Preference data, post-training methods, behavior audits |
| Evaluation | How capable or reliable is the model on a defined task? | Benchmarks, leaderboards, scored test sets |
In practice, a safety benchmark is an evaluation instrument built around safety concerns. Alignment methods are one way to improve safety outcomes, but safety also includes deployment controls and monitoring that sit outside the model itself.
How Safety Is Measured
Safety measurement follows the same basic logic as other AI evaluation: define a risky scenario, build a test set, score model responses against explicit criteria, and compare results across models or versions.
Scale Labs' DistressBench illustrates this. It is described as evaluating "multi-dimensional crisis support in large language models" and is categorized under Safety & Oversight. The key design choices in such a benchmark are:
- Scenario selection: what kinds of crisis or distress situations are tested.
- Response criteria: what counts as helpful, safe, or harmful, broken into multiple dimensions rather than a single pass/fail.
- Scoring and comparison: how responses are rated and how models are ranked or compared over time.
A single aggregate score hides a lot. Multi-dimensional scoring matters because a model can be safe on one axis (avoiding harmful advice) while failing on another (failing to point to appropriate help).
Common Safety Concerns in Frontier AI
- Crisis and distress support: whether models respond appropriately to users in acute distress.
- Harmful outputs and jailbreaks: whether adversarial prompts can bypass safeguards.
- Agentic deployment risk: whether agents with tools and autonomy can cause unintended actions; Scale Labs' READY or Not paper addresses reliable enterprise agent deployment.
- Medical and clinical reasoning: benchmarks such as CliniCARE-Bench audit medical reasoning in EHR contexts, where errors carry real consequences.
Why Safety Evaluation Is Part of Frontier Research
Safety benchmarks serve the same function as capability benchmarks: they make claims comparable and testable. Publishing a safety benchmark lets researchers compare models on defined risk scenarios, track regressions between versions, and surface failure modes that ordinary capability tests miss. That is why safety appears alongside evaluation and alignment in research agendas and why safety benchmarks are listed next to capability leaderboards.
If you are choosing how to assess a model's safety, start by matching the benchmark to your deployment context: crisis-support benchmarks for consumer-facing chat, agent-deployment evaluations for tool-using systems, and domain audits for regulated settings. Check what dimensions the benchmark scores and whether its scenarios resemble your actual use case before treating a result as decisive.