Security Release Process #458
Merged
Conversation
This file contains 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
✅ Deploy Preview for kurator-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Xieql
reviewed
Nov 20, 2023
| @@ -0,0 +1,130 @@ | |||
| # Security Release Process | |||
|
|
|||
| Kurator has always attached great importance to vulnerability management in development and maintenance. The kurator community has adopted this security disclosures and response policy to ensure we responsibly handle critical issues. | |||
There was a problem hiding this comment.
Suggested change
| Kurator has always attached great importance to vulnerability management in development and maintenance. The kurator community has adopted this security disclosures and response policy to ensure we responsibly handle critical issues. | |
| Kurator has always attached great importance to vulnerability management in development and maintenance. The Kurator community has adopted this security disclosures and response policy to ensure we responsibly handle critical issues. |
| - [Stepping Down](#stepping-down) | ||
| - [Responsibilities](#responsibilities) | ||
| - [Associate](#associate) | ||
| - [Process a undisclosed vulnerability](#process-a-undisclosed-vulnerability) |
There was a problem hiding this comment.
Suggested change
| - [Process a undisclosed vulnerability](#process-a-undisclosed-vulnerability) | |
| - [Process an undisclosed vulnerability](#process-a-undisclosed-vulnerability) |
|
|
||
| ## Vulnerability handling process | ||
|
|
||
| The following flowchart shows the vulnerability handling process. we will strictly handle the reporting vulnerability according to this procedure. |
There was a problem hiding this comment.
Suggested change
| The following flowchart shows the vulnerability handling process. we will strictly handle the reporting vulnerability according to this procedure. | |
| The following flowchart shows the vulnerability handling process. We will strictly handle the reporting vulnerability according to this procedure. |
|
|
||
| ### Fix Disclosure Process | ||
|
|
||
| With the Fix Development underway the Security Team needs to come up with an overall communication plan for the wider community. This Disclosure process should begin after the Security Team has developed a Fix or mitigation so that a realistic timeline can be communicated to users. Emergency releases for critical and high severity issues or fixes for issues already made public may affect the below timelines for how quickly or far in advance notifications will occur. |
There was a problem hiding this comment.
Suggested change
| With the Fix Development underway the Security Team needs to come up with an overall communication plan for the wider community. This Disclosure process should begin after the Security Team has developed a Fix or mitigation so that a realistic timeline can be communicated to users. Emergency releases for critical and high severity issues or fixes for issues already made public may affect the below timelines for how quickly or far in advance notifications will occur. | |
| With the Fix Development underway, the Security Team needs to come up with an overall communication plan for the wider community. This Disclosure process should begin after the Security Team has developed a Fix or mitigation so that a realistic timeline can be communicated to users. Emergency releases for critical and high severity issues or fixes for issues already made public may affect the below timelines for how quickly or far in advance notifications will occur. |
hzxuzhonghu
approved these changes
Nov 20, 2023
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hzxuzhonghu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: LiZhenCheng9527 <lizhencheng6@huawei.com>
LiZhenCheng9527
force-pushed
the
security-release-process
branch
from
3f38996 to
998b694
Compare
Signed-off-by: LiZhenCheng9527 <lizhencheng6@huawei.com>
|
/lgtm |
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.
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Kurator does not have a regulated process for handling security breaches at this time. In order to better manage security risks and improve response efficiency, a standardised process for handling security breaches in Kurator is proposed.