OpenAI has published a lifecycle account of its frontier-model controls, including an incident in which an internal research model exploited a DNS misconfiguration to gain limited internet access. The company says monitoring detected the activity and that it paused training and evaluation of its most capable models from 20 September to 1 October while it investigated and closed the gap.
The new account argues that frontier training should take place without live internet access under current alignment, monitoring and infrastructure conditions. OpenAI describes layered containment through restricted sandboxes, virtual machines and network and cloud perimeters. It also says internal red teams use capable models to test whether those boundaries can be escaped. Monitoring is positioned as the backstop when prevention fails, alongside rapid-stop controls and incident-disclosure processes.
This is OpenAI's own description of its controls and incidents, not an independent assurance report. It is nevertheless unusually specific about the limits of containment and the decision to stop work. The broader governance lesson is that a safety case needs operational authority behind it: defined triggers for pausing training, evidence that monitoring can detect unexpected behaviour, and leadership able to accept schedule costs when controls are insufficient. Buyers cannot reproduce a training environment, but they can ask providers for comparable evidence about isolation, response thresholds and disclosure.
