add third party vuln process

processes/third_party_vuln_process.md

@@ -0,0 +1,95 @@
+This document describes the management of vulnerabilities within the Node.js
+ecosystem. Vulnerabilities in Node.js core are out of this scope.
+
+# Definitions
+
+* package: in this document, a package is a module available for use with Node.js
+ and hosted on the npmjs.org repository.
+
+# Process
+
+Individuals who find potential vulnerabilities in a package are invited 
+to complete a vulnerability report on the dedicated HackerOne organization:
+
+[https://hackerone.com/nodesecurity](https://hackerone.com/nodesecurity)
+
+Vulnerabilities can also be reported by emailing security-ecosystem@nodejs.org.
+
+When a potential vulnerability is reported, the following actions are taken:
+
+## Triage
+
+**Who:** The triage team
+
+**Delay:** 48 hours
+
+Within 48 hours, a member of the triage team provides a first answer to the
+individual who submitted the potential vulnerability. The possible responses
+can be:
+
+* Acceptance: what was reported is considered as a new vulnerability
+* Rejection: what was reported is not considered as a new vulnerability
+* Need more information: the triage team needs more information in order to evaluate what was reported.
+
+## Correction follow-up
+
+**Who:** A member of the triage team
+
+**Delay:** 45 days
+
+When a vulnerability is confirmed, a member of the triage team is
+designated to follow up on this report.
+
+With the help of the individual who reported the vulnerability, they contact
+the maintainers of the vulnerable package to make them aware of the
+vulnerability.
+
+With the package maintainer, they define a release date for the publication
+of the vulnerability. Ideally, this release date should not happen before
+the package has been patched.
+
+If the maintainers are unreachable, the vulnerability is to be made public
+45 days after the triage date.
+
+
+## Publication
+
+**Who:** A member of the triage team
+
+**Delay:** 45 days
+
+Within 45 days after the triage date, the vulnerability must be made public.
+
+If a patch is being actively developed by the package maintainer, an additional delay
+can be added with the approval of the triage team and the individual who
+reported the vulnerability (this is a simple vote where each member of the
+triage team and the vulnerability reporter have 1 vote each).
+
+The vulnerability is considered as published when a Pull Request adding it
+to this repository is opened.
+
+Within HackerOne, this is handled through a "public disclosure request".
+
+## Vulnerabilities found outside this process
+
+Vulnerabilities found and fixed outside this process should be added into
+the vulnerability database. This can be done by anyone through a Pull Request on 
+this repository.
+
+# The triage team
+
+The triage team is composed of 5 or more members of the security working group.
+This team is approved and modified by a vote from the working group.
+
+They are responsible for the management of this process.
+
+Each member of the triage team is expected to handle vulnerabilities on a 
+regular basis.
+
+Members of this team are required to follow the same NDA and privacy measures 
+as the [Node.js Security Team](https://github.com/nodejs/security-wg/blob/master/processes/security_team_members.md).
+
+Members of the security teams should indicate that they accept the privacy policies 
+by PRing their acceptance to this file:
+
+* @vdeturckheim - Vladimir de Turckheim