Answer: In the desktop app, open a completed scan from Security > Scans and under Artifacts select Findings JSON or SARIF report; when Codex offers to export the scan's findings, ask for JSON, CSV, or SARIF. To export from a terminal, use the saved scan directory with the CLI export command. Status: Check failed Entry: tool/codex/permissions-and-security/export-security-findings-formats Revision: 1 Digest: sha256:d0907eafb5fdac9c (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:30Z Last changed: 2026-11-13T03:53:30Z Last verified: 2026-11-16T13:21:22Z Last attempt: 2026-11-20T13:42:04Z (failed) Next check: 2026-11-20T14:42:04Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Desktop export location | Security | [1] | 2026-11-16 JSON artifact option | Findings JSON | [1] | 2026-11-16 SARIF artifact option | SARIF report | [1] | 2026-11-16 Terminal export method | CLI export command | [1] | 2026-11-16 CSV export path | exports/findings.csv | [1] | 2026-11-16 CSV use case | Review findings in a spreadsheet. | [1] | 2026-11-16 SARIF use case | Send findings to tools that support the SARIF interchange format. | [1] | 2026-11-16 Sources: [1] OpenAI. "Export and track security findings". https://learn.chatgpt.com/docs/security/plugin/export-findings.md Role: primary. Accessed: 2026-11-16T13:21:22Z Quote: "open a completed scan from **Security** > **Scans**" (Supports: Desktop export location) Quote: "select **Findings JSON** to open the structured findings" (Supports: JSON artifact option) Quote: "**SARIF report** if the scan produced one" (Supports: SARIF artifact option) Quote: "use the saved scan directory with the [CLI export command]" (Supports: Terminal export method) Quote: "Open `exports/findings.csv` in the scan directory." (Supports: CSV export path) Quote: "| CSV | Review findings in a spreadsheet." (Supports: CSV use case) Quote: "| SARIF | Send findings to tools that support the SARIF interchange format." (Supports: SARIF use case) Snapshot SHA-256: 0481b9a7a0c71d2b7da6f3ef391c37004b3d9f91744e87d626902df208666716 (captured 2026-11-13T03:53:30Z) 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:30Z, so the values verified then were kept. Cross-check: not-available at 2026-11-16T13:21:22Z. No independent second source is configured for this entry Last successful check: 2026-11-16T13:21:22Z Last attempt: 2026-11-20T13:42:04Z (failed) Notes and limitations: Extracted automatically from a single official source (section "Export a portable artifact"). Related: https://latestn.com/tool/codex/permissions-and-security/export-with-triage-status How do I include triage status, close reasons, or notes when exporting Codex findings? https://latestn.com/tool/codex/permissions-and-security/fix-finding-in-conversation How do I fix a security finding from a conversation in Codex? https://latestn.com/tool/codex/permissions-and-security/fix-finding-in-ui How do I generate, review, apply, and verify a patch for a security finding in Codex? https://latestn.com/tool/codex/permissions-and-security/enable-local-codex-access How do I enable or disable local Codex access for workspace members? https://latestn.com/tool/codex/permissions-and-security/enable-mxc-windows-sandbox How do I enable MXC for the Codex Windows sandbox? https://latestn.com/tool/codex/permissions-and-security/enable-verified-remediation How do I enable verified remediation in Codex Security for GitLab? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T14:07:18Z | check-failed | Extraction did not pass verification: section "Export a portable artifact" not found in the source (the page may have been reorganized) | — 2026-11-13T03:53:30Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/export-security-findings-formats/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/export-security-findings-formats POST: https://latestn.com/dispute/tool/codex/permissions-and-security/export-security-findings-formats with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/export-security-findings-formats?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I export Codex security scan findings as JSON, CSV, or SARIF? Revision 1, last verified 2026-11-16T13:21:22Z. https://latestn.com/tool/codex/permissions-and-security/export-security-findings-formats (accessed 2026-11-21T10:03:32Z). @misc{LatestN_tool_codex_permissions_and_security_export_security_findings_formats_r1, title = {How do I export Codex security scan findings as JSON, CSV, or SARIF?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/export-security-findings-formats}}, note = {Revision 1; digest sha256:d0907eafb5fdac9c; last verified 2026-11-16T13:21:22Z; accessed 2026-11-21T10:03:32Z} } 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/export-security-findings-formats