Repository navigation
Security Policies #430
Description
We should have well documented policies around vulnerability disclosure, reporting and security advisory notices.
I bet @evilpacket has things to say :)
We should have well documented policies around vulnerability disclosure, reporting and security advisory notices.
I bet @evilpacket has things to say :)
Activity
evilpacket commentedon Jan 14, 2015
Here is what I provided to the Node.js project in the past based on other policies and structure that I thought was well thought through. Specifically the ember security process which has links to other great sources. Welcome comments on any of it.
Important aspects are the communication with the disclosing party (read 1337 haxor) and then with the public once a patch is in place. I simply can't stress good communication enough. So a clear channel to get security issues on and a good output channel to broadcast them once addressed.
The other important thing is what happens in the middle. Obviously communication as to what is going on with a fix, but timely fixes as well. Pretty sure that is already engrained in the spirit of io.js based on the wanting to get latest v8 in quickly and release quickly, so not that worried about being able to execute on that.
Reporting a Bug
All security bugs in io.js are taken seriously and should be reported by email to security@iojs.org. This will be delivered to a subset of the core team who handle security issues.
Your email will be acknowledged within 24 hours, and you’ll receive a more detailed response to your email within 48 hours indicating the next steps in handling your report.
After the initial reply to your report, the security team will endeavor to keep you informed of the progress being made towards a fix and full announcement, and may ask for additional information or guidance surrounding the reported issue. These updates will be sent at least every five days, in practice, this is more likely to be every 24-48 hours.
If you have not received a reply to your email within 48 hours, or have not heard from the security team for the past five days, there are a few steps you can take:
Security bugs in third party modules should be reported to their respective maintainers and can also be coordinated through the Node Security Project.
Thank you for improving the security of Node.js. Your efforts and responsible disclosure are greatly appreciated and will be acknowledged.
Disclosure Policy
Here is the security disclosure policy for Node.js
Receiving Security Updates
Security notifications will be distributed via the following methods.
Core Security Team
The following people make up the io.js core security team.
Comments on this Policy
If you have suggestions on how this process could be improved please submit a pull request or email security@iojs.org to discuss.
brendanashworth commentedon Feb 7, 2015
Seems like the structure put forward by @evilpacket is uncontested. Would a
SECURITY.mdfile in the root of the project do the job? I think a pull request is the next step now.mikeal commentedon Feb 8, 2015
yes please! :)
brendanashworth commentedon Feb 10, 2015
@evilpacket would you like to send in a PR with your policy?
evilpacket commentedon Feb 10, 2015
Yes. I'll hit that up after node summit.
mikeal commentedon Feb 13, 2015
@evilpacket poke! it's after Node Summit :)
Fishrock123 commentedon Mar 30, 2015
@evilpacket Status?
Initial checkin
brendanashworth commentedon May 20, 2015
ping @evilpacket, I can PR this in if you'd like.
Qard commentedon Aug 14, 2015
Is anything happening with this? We have some security process in-place, and a note in the readme. Do we still want this more detailed document?
silverwind commentedon Oct 9, 2015
No movment here since a long time, and some information above is already outdated with the node merger. I'll close this.