Reported operating use · AI infrastructure and security
Test agent containment and verify security repairs
OpenAI
Reported internal security work in isolated copies of research infrastructure; published 23 October 2026.
A published third-party example, not a Nuvepro customer case or evidence of a partnership.
What the source reports
OpenAI reports using agent teams to test containment in copies of its research infrastructure. Automated triage grouped candidate findings; security and infrastructure teams reproduced findings and verified configuration repairs. Cloud partners helped supervise the experiments. The account describes monitoring and programmatic checks designed to pause runs on out-of-scope activity and treats continued testing as necessary after repairs.
Reported technology: OpenAI internal models and security teams. Scope and outcomes are source-reported.
What the enterprise environment would need
The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.
- Authorized test scope
- Proposed: an isolated copy of an agreed application environment, synthetic records and credentials, and a written list of permitted tests. No access to customer production systems.
- People and decisions
- Proposed: a security owner approves scope, engineers reproduce candidate findings, and a separate reviewer decides whether repair evidence is sufficient.
- Records and outputs
- Proposed: versioned configurations, attempt logs, a finding register, repair diffs and repeatable checks. Preserve unsuccessful attempts and disputed findings.
A proposed simulation
An illustrative practice design derived from this work, not an executed assessment.
Proposed: inspect a supplied test environment, record a permission-boundary finding and prepare a repair for engineer review.
Review gate: A separate reviewer can reproduce the finding and confirm the repair against the agreed permission matrix. The security owner decides acceptance.
Challenge the result: A candidate finding cannot be reproduced, or its proposed repair grants broader permissions. Keep it unresolved and route it to the security owner.
What needs checking
- Proposed: compare allowed and denied actions against an owner-approved permission matrix before and after each repair.
- Proposed: independently reproduce a reported boundary failure, then verify the repair without expanding access.
- Proposed: test that an out-of-scope attempt stops the run and produces an actionable record for the responsible engineer.
Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.
Shape this around your enterprise
Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.
Sources and limitations
Curation review: . This is the date this source example was reviewed, separate from source publication dates.
- This is an operator account, not an independent security certification or a generally available service.
- The report concerns internal research infrastructure; it does not establish the safety of another enterprise environment.
- The proposed project is not a replica of OpenAI infrastructure or an executed Nuvepro assessment.
- Securing our frontier model training environmentSource publication: 2026-10-23