Add SPEC 11 on vulnerability disclosure #391
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mihaimaruseac
force-pushed
the
patch-1
branch
3 times, most recently
from
7b9a2f9 to
0ce4a6e
Compare
I used SPEC 11 name as that was selected from the last year, but I am happy to switch to a different number if needed. This is to be paired with scientific-python#390 and currently a draft. Signed-off-by: Mihai Maruseac <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new SPEC focused on responding to security incidents and disclosure of vulnerabilities.
The SPEC outlines creating a Security Response Team (SRT) and how this team can react to security incidents, notify affected projects, manage the fixing of the security issues and disclose the vulnerability and the releases that contain the fix, following responsible disclosure methods. The SRT also handles vulnerabilities under embargo (using the Traffic Lights Protocol (TLP)).
There have been ongoing conversations in the community, particularly at the Developer Summit 2024 and Developer Summit 2025 (see scientific-python/summit-2025#8) about improving how we handle vulnerability disclosure
Due to the complexity of the broader disclosure process, we decided to split the work into two separate SPECs:
This SPEC will hopefully encourage all projects in the ecosystem to follow similar standards. The SRT can be a team across all projects, or just some of the projects, and each project can also select a single team to handle vulnerabilities for that specific project.
I used SPEC 11 name as that was selected from the last year, but I am happy to switch to a different number if needed.
This is to be paired with #390 and currently a draft.
Link to issue
Discourse post