Add back link to the ASF blog about severity to the policy #33691
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
The security policy should be the place where researchers are looking on how to assign severity to their reports. We had the link to the ASF blog post decribing how we assess the severity but it has been moved out in apache#32496 somewhat accidentally to the information about the security team. It can stay there (as a reference for the security team members/internal, but it would be great to keep it in our Policy targeted for the researchers.
eladkal
approved these changes
Aug 24, 2023
pankajkoti
approved these changes
Aug 24, 2023
Co-authored-by: Pankaj Koti <[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.
The security policy should be the place where researchers are looking on how to assign severity to their reports. We had the link to the ASF blog post decribing how we assess the severity but it has been moved out in #32496 somewhat accidentally to the information about the security team. It can stay there (as a reference for the security team members/internal, but it would be great to keep it in our Policy targeted for the researchers.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.