Answer: Start with advisory results, reviewing representative findings, scan coverage, cost, and runtime before deciding which outcomes should block a merge. The severity policy considers findings from the current scan at or above your threshold, and enforcement is configured in the GitHub Actions or GitLab CI/CD guides. Status: Confirmed Entry: tool/codex/permissions-and-security/ci-severity-policy Revision: 2 Digest: sha256:71c97674064a7b32 (changes whenever the content changes) Timeline: Created: 2026-11-13T13:25:39Z Last changed: 2026-11-17T14:06:38Z (scan completeness note: — → an incomplete scan can report no findings) Last verified: 2026-11-20T13:41:34Z Next check: 2026-11-21T13:41:34Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of starting approach | advisory results | [1] | 2026-11-20 review factors | representative findings, scan coverage, cost, and runtime | [1] | 2026-11-20 policy scope | findings from the current scan at or above your threshold | [1] | 2026-11-20 earlier findings | Earlier open findings don't affect it. | [1] | 2026-11-20 scan completeness note | an incomplete scan can report no findings | [1] | 2026-11-20 Sources: [1] OpenAI. "Codex Security CI/CD overview". https://learn.chatgpt.com/docs/security/cli/ci.md Role: primary. Accessed: 2026-11-20T13:41:34Z Quote: "Start with advisory results." (Supports: starting approach) Quote: "Review representative findings, scan coverage, cost, and runtime before deciding which outcomes should block a merge." (Supports: review factors) Quote: "The severity policy considers findings from the current scan at or above your threshold." (Supports: policy scope) Quote: "Earlier open findings don't affect it." (Supports: earlier findings) Quote: "Check scan completeness separately, since an incomplete scan can report no findings." (Supports: scan completeness note) Snapshot SHA-256: 0ad309e123789eff2de9df21a275a8e7cd6b7dbecf26f123f75192d32746ce84 (captured 2026-11-17T14:06:35Z) 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-17T14:06:38Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:41:34Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:41:34Z Last attempt: 2026-11-20T13:41:34Z Notes and limitations: Extracted automatically from a single official source (section "Choose a severity policy"). Related: https://latestn.com/tool/codex/permissions-and-security/cloud-internet-access-settings How do I enable or disable internet access for the Codex agent in cloud chats? https://latestn.com/tool/codex/permissions-and-security/codex-security-review-setup How do I set up and request a Codex Security Review on a pull request? https://latestn.com/tool/codex/permissions-and-security/common-permission-profiles What common Codex permission profiles exist, such as read-only with network allowlist or workspace write without network? https://latestn.com/tool/codex/permissions-and-security/auto-review-blocked-actions What does Codex Auto-review block and what does the reviewer see? https://latestn.com/tool/codex/permissions-and-security/bedrock-authentication How do I authenticate Codex Security scans with Amazon Bedrock? https://latestn.com/tool/codex/permissions-and-security/choose-security-scan-method How do I choose between Daybreak Defense Factory and the Codex Security plugin for scanning code? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T14:06:38Z | changed | scan completeness note: — → an incomplete scan can report no findings | [1] 2026-11-17T14:06:38Z | changed | review factors: — → representative findings, scan coverage, cost, and runtime | [1] 2026-11-17T14:06:38Z | changed | enforcement configuration: Configure enforcement in the [GitHub Actions guide] → — | [1] 2026-11-17T14:06:38Z | changed | incomplete scan: An incomplete scan can leave areas without a review even when it reports no findings → — | [1] 2026-11-17T14:06:38Z | changed | earlier findings: Earlier open findings in the repository summary don't affect that policy → Earlier open findings don't affect it. | [1] 2026-11-17T14:06:38Z | changed | policy scope: findings from the current scan at or above the configured threshold → findings from the current scan at or above your threshold | [1] 2026-11-17T14:06:38Z | changed | what to review: Review representative findings, scan coverage, cost, and runtime before deciding which outcomes should block a merge → — | [1] 2026-11-17T14:06:38Z | changed | starting approach: Start with advisory results → advisory results | [1] 2026-11-13T13:25:39Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/ci-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/ci-severity-policy POST: https://latestn.com/dispute/tool/codex/permissions-and-security/ci-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/ci-severity-policy?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I choose a severity policy for Codex Security findings in CI? Revision 2, last verified 2026-11-20T13:41:34Z. https://latestn.com/tool/codex/permissions-and-security/ci-severity-policy (accessed 2026-11-21T10:01:21Z). @misc{LatestN_tool_codex_permissions_and_security_ci_severity_policy_r2, title = {How do I choose a severity policy for Codex Security findings in CI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/ci-severity-policy}}, note = {Revision 2; digest sha256:71c97674064a7b32; last verified 2026-11-20T13:41:34Z; accessed 2026-11-21T10:01:21Z} } 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/ci-severity-policy