Answer: To fail on high or critical findings from a completed scan, set `fail-on-severity: high` in the PR workflow's setting. For each protected target branch, require the matching check from the GitHub Actions app, such as **Codex Security / main** on `main`. Status: Confirmed Entry: tool/codex/permissions-and-security/configure-severity-policy Revision: 1 Digest: sha256:9ad53bf5a5f72265 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:04Z Last changed: 2026-11-13T03:53:04Z Last verified: 2026-11-20T13:41:36Z Next check: 2026-11-21T13:41:36Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of severity policy setting | fail-on-severity: high | [1] | 2026-11-20 default scheduled workflow setting | fail-on-severity: none | [1] | 2026-11-20 required check example | Codex Security / main | [1] | 2026-11-20 exit code for passed policy | 0 | [1] | 2026-11-20 exit code for failed policy | 1 | [1] | 2026-11-20 gate check example | Codex Security gate / main | [1] | 2026-11-20 Sources: [1] OpenAI. "Run Codex Security in GitHub Actions". https://learn.chatgpt.com/docs/security/cli/ci/github.md Role: primary. Accessed: 2026-11-20T13:41:36Z Quote: "fail-on-severity: high" (Supports: severity policy setting) Quote: "The scheduled workflow starts with `fail-on-severity: none`." (Supports: default scheduled workflow setting) Quote: "such as **Codex Security / main** on `main`" (Supports: required check example) Quote: "Exit code `0` sets `scan-status: completed` and `policy-status: passed`." (Supports: exit code for passed policy) Quote: "Exit code `1` sets `scan-status: completed` and `policy-status: failed`;" (Supports: exit code for failed policy) Quote: "require **Codex Security gate / main** and **Codex Security / main**" (Supports: gate check example) Snapshot SHA-256: 888cc3aa1b06e72f841c1ac8e201b76e37e0cab0f271a9c0421448ba14709e5e (captured 2026-11-13T03:53:03Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:53:04Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:41:36Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:41:36Z Last attempt: 2026-11-20T13:41:36Z Notes and limitations: Extracted automatically from a single official source (section "Choose a severity policy"). Related: https://latestn.com/tool/codex/permissions-and-security/configure-windows-sandbox How do I configure the Windows sandbox for Codex CLI? https://latestn.com/tool/codex/permissions-and-security/control-browser-computer-use How do I control browser and Computer Use access for Codex and ChatGPT Work? https://latestn.com/tool/codex/permissions-and-security/create-rules-file How do I create a rules file to control which commands Codex can run outside the sandbox? https://latestn.com/tool/codex/permissions-and-security/configure-network-access How do I configure network access requirements for Codex and ChatGPT Work? https://latestn.com/tool/codex/permissions-and-security/configure-networking-allowed-destinations How do I configure networking and allowed destinations for Codex in the Agent Security UI? https://latestn.com/tool/codex/permissions-and-security/configure-sandbox-defaults How do I configure the default sandbox permissions in Codex? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:53:04Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/configure-severity-policy/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/permissions-and-security/configure-severity-policy POST: https://latestn.com/dispute/tool/codex/permissions-and-security/configure-severity-policy with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/configure-severity-policy?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure a severity policy to enforce Codex Security scan results in GitHub Actions? Revision 1, last verified 2026-11-20T13:41:36Z. https://latestn.com/tool/codex/permissions-and-security/configure-severity-policy (accessed 2026-11-21T10:04:04Z). @misc{LatestN_tool_codex_permissions_and_security_configure_severity_policy_r1, title = {How do I configure a severity policy to enforce Codex Security scan results in GitHub Actions?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/configure-severity-policy}}, note = {Revision 1; digest sha256:9ad53bf5a5f72265; last verified 2026-11-20T13:41:36Z; accessed 2026-11-21T10:04:04Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/permissions-and-security/configure-severity-policy