Answer: You can request a hardening portfolio for a standard, deep, or change scan with reportable findings; Codex writes the portfolio to `hardening/hardening.md`, structured analysis to `hardening/hardening.json`, and supporting proposals or diagrams under `hardening/`. Keep the full scan directory together so the links from `report.md` remain usable. Status: Confirmed Entry: tool/codex/permissions-and-security/use-hardening-guidance-from-scan Revision: 2 Digest: sha256:5546a2675dbd6f11 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:40Z Last changed: 2026-11-18T13:35:54Z (portfolio link source: — → report.md) Last verified: 2026-11-20T13:42:12Z Next check: 2026-11-21T13:42:12Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of portfolio file | hardening/hardening.md | [1] | 2026-11-20 structured analysis file | hardening/hardening.json | [1] | 2026-11-20 supporting files location | hardening/ | [1] | 2026-11-20 scan types | standard, deep, or change scan | [1] | 2026-11-20 portfolio link source | report.md | [1] | 2026-11-20 Sources: [1] OpenAI. "Propose security hardening". https://learn.chatgpt.com/docs/security/plugin/security-hardening.md Role: primary. Accessed: 2026-11-20T13:42:12Z Quote: "Codex writes the portfolio to `hardening/hardening.md`" (Supports: portfolio file) Quote: "structured analysis to `hardening/hardening.json`" (Supports: structured analysis file) Quote: "supporting proposals or diagrams under `hardening/`" (Supports: supporting files location) Quote: "for a standard, deep, or change scan with reportable findings" (Supports: scan types) Quote: "The scan links the portfolio from `report.md`" (Supports: portfolio link source) Snapshot SHA-256: 2a805e0f0af6057db6477a0251b6b3d35a60cfa02128f7aa5383ce0cf5bae89d (captured 2026-11-17T14:07:27Z) 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:07:28Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:42:12Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:42:12Z Last attempt: 2026-11-20T13:42:12Z Notes and limitations: Extracted automatically from a single official source (section "Use hardening guidance from a scan"). Related: https://latestn.com/tool/codex/permissions-and-security/vulnerability-report-without-scan Can Codex write vulnerability reports without a Codex Security scan? https://latestn.com/tool/codex/permissions-and-security/write-vulnerability-reports-workflow How do I use Codex to write vulnerability reports from findings and PoCs? https://latestn.com/tool/codex/pricing-and-limits/auto-review-limits What are the limits of Codex Auto-review and when does it trigger? https://latestn.com/tool/codex/permissions-and-security/track-findings-issue-advisory How do I get Codex to create a GitHub issue or draft security advisory for findings? https://latestn.com/tool/codex/permissions-and-security/triage-security-backlog How do I triage a backlog of security findings in Codex? https://latestn.com/tool/codex/permissions-and-security/use-chatgpt-auth-instead-of-api-key How do I make Codex Security CLI use my ChatGPT sign-in instead of an API key for scans? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:35:54Z | changed | portfolio link source: — → report.md | [1] 2026-11-18T13:35:54Z | changed | linked from: report.md → — | [1] 2026-11-13T03:53:40Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/use-hardening-guidance-from-scan/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/use-hardening-guidance-from-scan POST: https://latestn.com/dispute/tool/codex/permissions-and-security/use-hardening-guidance-from-scan with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/use-hardening-guidance-from-scan?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I use hardening guidance from a Codex Security scan? Revision 2, last verified 2026-11-20T13:42:12Z. https://latestn.com/tool/codex/permissions-and-security/use-hardening-guidance-from-scan (accessed 2026-11-21T10:04:38Z). @misc{LatestN_tool_codex_permissions_and_security_use_hardening_guidance_from_scan_r2, title = {How do I use hardening guidance from a Codex Security scan?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/use-hardening-guidance-from-scan}}, note = {Revision 2; digest sha256:5546a2675dbd6f11; last verified 2026-11-20T13:42:12Z; accessed 2026-11-21T10:04:38Z} } 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/use-hardening-guidance-from-scan