SpyBara
Go Premium

security/threat-model.md 2026-10-15 23:00 UTC to 2026-10-16 23:02 UTC

This page contains 21 additions and 18 deletions.

2026
Fri 16 23:02

Improve the Cloud threat model

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to the page URL.

Update a monitored repository's threat model when the generated version misses security assumptions or deployment context. This guide applies to Codex Security Cloud. For local plugin policy, see Configure the scan.

What a threat model is

A threat model is a short security summary of how your repository works. Codex Security creates the first draft from the code and uses it to guide future commit scans and prioritize findings.

A threat model describes:

  • Entry points and who can supply input to them
  • Trust boundaries and authentication or authorization assumptions
  • Sensitive data and privileged actions
  • Areas that need particular attention

For example:

The public account API accepts authenticated users' JSON requests and file uploads. Users may change only accounts in their own tenant. The identity service authenticates the caller, but each handler must check tenant access. Billing changes go through a privileged internal service. Prioritize missing tenant checks and upload paths that can reach that service.

Identify uncertain assumptions. For example, don't describe an endpoint as internal-only unless that is true of the deployment you want assessed.

Edit the threat model

  1. Open the Codex Security Cloud plugin. See Cloud setup if you haven't installed it or configured commit monitoring.
  2. Open Repositories and select the monitored repository.
  3. Open Monitoring settings.
  4. Edit Threat model, then select Save.

Changes apply to future scans.

Revisit the model after changes to authentication, tenant boundaries, or exposed services. Keep facts about the deployment separate from priorities for the scan.