doc: add CPython Threat Model and update security policy (#1803) by nayanraj864-cmyk · Pull Request #1901 · python/devguide · GitHub
Skip to content

doc: add CPython Threat Model and update security policy (#1803) - #1901

Closed
nayanraj864-cmyk wants to merge 3 commits into
python:mainfrom
nayanraj864-cmyk:doc-threat-model-security-policy
Closed

nayanraj864-cmyk wants to merge 3 commits into
python:mainfrom
nayanraj864-cmyk:doc-threat-model-security-policy

Conversation

@nayanraj864-cmyk

Copy link
Copy Markdown

This PR creates an explicit CPython Threat Model document and updates the Security Policy to set clear guidelines for vulnerability reports submitted to the Python Security Response Team (PSRT).

Changes Included:

  • security/threat-model.rst: Created a new threat model detailing CPython's security boundaries, trusted execution assumptions (command-line flags, environment variables, memory/C-API), non-sandboxing policy (eval, exec, pickle), availability constraints, and standard library module threat models (ssl, urllib, xml, subprocess, tarfile).
  • security/policy.rst: Linked the threat model, added explicit LLM model disclosure requirements for reporters, and emphasized Code of Conduct prioritization.
  • security/index.rst: Registered threat-model in the section Table of Contents.

Closes #1803

@nayanraj864-cmyk

Copy link
Copy Markdown
Author

@read-the-docs-community

read-the-docs-community Bot commented Sep 8, 2026

Copy link
Copy Markdown

Documentation build overview

📚 CPython devguide | 🛠️ Build #34456508 | 📁 Comparing f004588 against latest (9d481ef)

  🔍 Preview build  

2 files changed
+ security/threat-model/index.html
± security/policy/index.html

@StanFromIreland

Copy link
Copy Markdown
Member

have recently started contributing to organizations that participate in Google Summer of Code (GSoC).

I'm sorry, but we're not part of GSoC this year.

Also some notes on the documents, it largely duplicates existing information (that's in the docs and/or the security policy), so in it's current state I'm afraid it's not particularly helpful. Also, did you use an LLM to generate the page?

Comment thread security/policy.rst

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a separate change, not related to the threat model. I also don't see any particular need for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create a Threat Model and Security Policy for CPython

2 participants