> For the complete documentation index, see [llms.txt](https://handbook.harmonic.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.harmonic.security/by-ai-vendor/openai.md).

# OpenAI

Security configuration, governance controls, and risk guidance for ChatGPT Work and ChatGPT Codex.

{% hint style="info" %}
This section focuses on the two OpenAI workforce products that need the clearest security ownership: ChatGPT Work for general business tasks and ChatGPT Codex for software-development work.
{% endhint %}

## Products covered in this handbook

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-briefcase" style="color:$primary;">:briefcase:</i></h3></td><td><strong>ChatGPT Work</strong></td><td>Focus first on managed workspace use, connector and plugin scope, browser and Computer Use policy, scheduled work, artifact sharing, and evidence gaps. Related: sandboxing.</td><td><a href="/by-ai-vendor/openai/chatgpt-work.md">ChatGPT Work</a></td></tr><tr><td><h3><i class="fa-code" style="color:$primary;">:code:</i></h3></td><td><strong>ChatGPT Codex</strong></td><td>Focus first on local and cloud boundaries, managed requirements, sandbox mode, approvals, hooks, MCP, network access, and runtime telemetry. Related: sandboxing, hooks, and OTel.</td><td><a href="/by-ai-vendor/openai/chatgpt-codex.md">ChatGPT Codex</a></td></tr></tbody></table>

## Security considerations specific to OpenAI

**Unmanaged usage is the first risk.** ChatGPT Work and Codex are available through the unified desktop app and can appear on corporate devices through personal accounts. Find unmanaged use, claim accounts into the managed workspace, and assign access by group and use case before tuning fine-grained controls.

**Work and Codex share technology, but not one policy surface.** Work is for research, analysis, documents, spreadsheets, presentations, Sites, and business workflows. Codex is for codebases, terminals, repositories, cloud tasks, and development automation. Review them separately even when they run in one desktop app.

**Connectors, plugins, browser access, and Computer Use need explicit decisions.** Source-system permissions still apply, but Work and Codex can combine data and actions across systems. Separate read, write, send, delete, publish, and share permissions.

**Evidence is split across systems.** Compliance exports are useful for supported messages and responses, but they do not prove every file, action, approval, or tool call. Pair platform evidence with endpoint, browser, source-system, repository, SIEM, and OpenTelemetry records where applicable.

## Current provider documentation

* [ChatGPT Work and Codex](https://help.openai.com/en/articles/20001275/)
* [ChatGPT desktop app](https://learn.chatgpt.com/docs/app)
* [Codex overview](https://developers.openai.com/codex/overview)
* [Codex agent approvals and security](https://learn.chatgpt.com/docs/agent-approvals-security)
* [Managed configuration](https://learn.chatgpt.com/docs/enterprise/managed-configuration)
* [Governance and observability](https://learn.chatgpt.com/docs/enterprise/governance)

*Last reviewed: August 18, 2026*

## Applicable Harmonic guidance

* [Securing ChatGPT Work: A Practitioner's Guide](https://www.harmonic.security/resources/securing-chatgpt-work-a-practitioners-guide)
* [Securing Codex Best Practice](https://www.harmonic.security/resources/securing-codex-best-practice)

## Related handbook guidance

* [AI Security Handbook](/ai-security-handbook.md)
* [ChatGPT Work](/by-ai-vendor/openai/chatgpt-work.md)
* [ChatGPT Codex](/by-ai-vendor/openai/chatgpt-codex.md)
* [7.4 The vendor-neutral control matrix](/handbook/7.-rollout-and-operations/7.4-the-vendor-neutral-control-matrix.md)
* [1.3 Tenant restrictions: blocking personal accounts](/handbook/1.-identity-and-access/1.3-tenant-restrictions-blocking-personal-accounts.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://handbook.harmonic.security/by-ai-vendor/openai.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.