Repository navigation
Add SECURITY.md vulnerability disclosure policy - #11
Closed
AndrewAPico wants to merge 1 commit into
Closed
AndrewAPico wants to merge 1 commit into
AndrewAPico wants to merge 1 commit into
Conversation
Contributor
|
Accepted |
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
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.
Adds
SECURITY.mdto the root of this repository.The policy covers private vulnerability reporting, response targets, supported versions, the CRA Article 13 security support period, scope, and third-party components. It is aligned with the EU Cyber Resilience Act (Regulation (EU) 2024/2847) and coordinated disclosure practice in ISO/IEC 29147 and ISO/IEC 30111.
Merging this enables the Security tab and the Report a vulnerability button on this repository.
The canonical copy lives in
picotech/picosdk-repo-standards(PR #1). This file is a byte-identical copy; future changes should be made there first and redistributed.Notes for review
sbom/folder, so the SBOM links in the policy resolve correctly.masterbranch under Supported versions and Support period. That is correct for this repository, but 6 of the organization's repositories default tomain— wording such as "the repository's default branch" would travel better.