Skip to content
ML Academy

LLMs, GenAI, RAG, agents, evaluation · insight-0543

Rerun safety and refusal tests after every fine-tune, even on benign data

Evidence type
empirical finding
Difficulty
medium
Roles
Applied AI, ML engineer
Industries
cross-industry

Summary: situation, action, reason, boundary

  1. Situation

    A team fine-tunes an aligned model on harmless customer-service transcripts and evaluates only task quality.

  2. Action

    Keep a safety and refusal regression suite (harmful requests, policy boundaries, data-leak probes) and make it a release gate for every fine-tuned version alongside the task eval.

  3. Reason

    Research showed fine-tuning on a few adversarial examples broke safety guardrails and that fine-tuning on benign, common datasets also degraded safety to a lesser degree.

  4. Boundary

    Any fine-tuning or preference tuning of an aligned model.

Symptom or risk

The tuned model now complies with requests the base model refused, and the regression is discovered by users.

Exceptions

None for customer-facing systems; internal prototypes still benefit from a small suite.

Trade-offs

Safety suites need upkeep and expert review.

Pitfalls

Assuming the base model's safety evaluation transfers to the fine-tuned model.

Lessons and concepts

Claims and their sources