Update SECURITY advisory #22
Conversation
Rewrite to remove email address and provide new advisory. Could be a model for a project wide advisory. Signed-off-by: Alex Sirota <alex@newpathconsulting.com>
asirota
added
documentation
| If you observe a security vulnerability in one of our packages or libraries, please responsibly report it to support@aspirepress.org. We will respond to notify you that we received your query, and we will credit you in the fix we provide. We ask for 30 days to fix any vulnerability before you disclose it. | ||
| If you observe a security vulnerability in any of our projects, please responsibly report it by opening a new security advisory within the project repository. The project lead or manager will respond to discuss the issue with you, and AspirePress will credit you in the fix shoild one be published. | ||
|
|
||
| We ask for 30 calendar days to fix any serious vulnerability before disclosure to AspirePress. AspirePress asks for any vulnerabilties not to be shared publicly. |
There was a problem hiding this comment.
We ask for 30 calendar days to fix any serious vulnerability before disclosure to Public.
There was a problem hiding this comment.
Yeah, the standard is responsibly report to the maintainers, and give them at least 30 days to rectify the issue before disclosing it publicly. "serious" is also somewhat subjective, so I'd suggest we generalise to any vulnerability.
We ask for 30 calendar days to fix any vulnerability before it is publicly disclosed.
| # Security | ||
|
|
||
| If you observe a security vulnerability in one of our packages or libraries, please responsibly report it to support@aspirepress.org. We will respond to notify you that we received your query, and we will credit you in the fix we provide. We ask for 30 days to fix any vulnerability before you disclose it. | ||
| If you observe a security vulnerability in any of our projects, please responsibly report it by opening a new security advisory within the project repository. The project lead or manager will respond to discuss the issue with you, and AspirePress will credit you in the fix shoild one be published. |
|
Let's collect feedback here. |
| # Security | ||
|
|
||
| If you observe a security vulnerability in one of our packages or libraries, please responsibly report it to support@aspirepress.org. We will respond to notify you that we received your query, and we will credit you in the fix we provide. We ask for 30 days to fix any vulnerability before you disclose it. | ||
| If you observe a security vulnerability in any of our projects, please responsibly report it by opening a new security advisory within the project repository. The project lead or manager will respond to discuss the issue with you, and AspirePress will credit you in the fix shoild one be published. |
There was a problem hiding this comment.
We have a lot of repos, and people shouldn't need a map just to find where to report an issue. Can we just turn "opening a new security advisory" into a link to an org-wide security report form? If it's not possible to do it org-wide, we can appoint a repo as canonical or just create a new repo.
If a project has special needs as security reporting goes, it can modify the template, but I'd encourage a centralized process for this sort of thing.
There was a problem hiding this comment.
Bear in mind that an advisory can have private pull requests attached to it. I'm not entirely sure that's possible if we do it at an organisation level or in a dedicated security repo.
This may be a good reason to standardize the security policy, but place it in each individual repo with a link to its respective advisories section.
There was a problem hiding this comment.
Alternatively, a relative URL would change from github.com/org/repo/security/policy to github.com/org/repo/security/advisories which would be correct. It would require the repo to have advisories of course.
Rewrite to remove email address and provide new advisory. Could be a model for a project wide advisory.
Pull Request
What changed?
Remove email added new wording
Why did it change?
Use GitHub security advisory process not email
Did you fix any specific issues?
#21
CERTIFICATION
By opening this pull request, I do agree to abide by the Code of Conduct and be bound by the terms of the Contribution Guidelines in effect on the date and time of my contribution as proven by the revision information in GitHub.