touch-up security policy #48280
Merged
touch-up security policy #48280
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
Member
Author
|
cc @IanColdwater @rachel-taylor-docker (fyi) There's probably more touching up possible (one step at a time); we have copies of this file in other repositories, so if we are ok with this version, I can update those in a follow-up. |
d61c32e to
58c8c4c
Compare
vvoland
approved these changes
Aug 1, 2024
thaJeztah
commented
Aug 1, 2024
58c8c4c to
b81a721
Compare
corhere
approved these changes
Aug 1, 2024
Member
Author
|
Waiting for some minor changes, we can merge after. |
Slightly touch-up the security policy in this repository to describe the process in more details. - Describe process around reporting, triage, and review. - Describe timelines for acknowledging reports. - Refer to supported versions / branches. Some of this wording was adopted from containerd's policy, adjusting where needed (e.g. the project currently does not have an embargoed security announce list, and no formal definition of security advisors). Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
b81a721 to
dfe36fa
Compare
laurazard
approved these changes
Aug 2, 2024
This was referenced Oct 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
I noticed the OpenSSF scorecard (https://securityscorecards.dev/viewer/?uri=github.com/docker/docker) ranked a 9 out of 10 for the policy, as it had some warnings:
This PR slightly touch-up the security policy in this repository to describe the process in more details.
Some of this wording was adopted from containerd's policy (https://github.com/containerd/project/blob/main/SECURITY.md), adjusting where needed (e.g. the project currently does not have an embargoed security announce list, and no formal definition of security advisors).