Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a Security Policy #3151

Closed
diogoteles08 opened this issue Jun 16, 2023 · 1 comment · Fixed by #3152
Closed

Add a Security Policy #3151

diogoteles08 opened this issue Jun 16, 2023 · 1 comment · Fixed by #3152
Assignees
Labels
Component - Misc Anything else (CODEOWNERS, etc.) Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Improvement Improvements that don't add a new feature or functionality Type - New Feature Add a new API call, functionality, or tool

Comments

@diogoteles08
Copy link
Contributor

Hey! I'm here again (see #2973) hoping to offer a bit more help with security enhancements.

This time I'm here to suggest that you expose a way that users can report eventual vulnerabilities in a safe and efficient way. This is usually described in a Security Policy, which is a GitHub standard document (SECURITY.md) added on the root of the repo and will be visible to the users in the "Security Tab".

image

It is a recommendation from Github itself, and from Scorecard (being a security measure of medium priority).

Aiming to make this change easier, I'll take the liberty of submitting one suggestion of a Security Policy as a PR. Please feel free to edit it directly or ask me for editions until it is in compliance with how HDFGroup/hdf5 would best handle vulnerability reports.

@byrnHDF byrnHDF added Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Improvement Improvements that don't add a new feature or functionality Type - New Feature Add a new API call, functionality, or tool Component - Misc Anything else (CODEOWNERS, etc.) labels Jun 17, 2023
@denandz
Copy link

denandz commented Jun 18, 2023

In the mean time - is there an existing security contact email where advisory documents / new vulnerabilities should be sent?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component - Misc Anything else (CODEOWNERS, etc.) Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Improvement Improvements that don't add a new feature or functionality Type - New Feature Add a new API call, functionality, or tool
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants