Security Working Group

Table of Contents

• Vulnerability Management
  • Security Announcement Process
  • Security Release Process
  • Node.js CVE management process
  • Responsible Disclosure Policy
  • Third-Party Ecosystem Triage Process
  • Third-Party HackerOne Submission form
  • Vulnerability Database
  • Recognition for Security Researchers
• Processes for Security WG Members
  • Security Team Membership Policy
  • On-boarding Team Members
  • Off-boarding Team Members
• Private Node.js core security group
• Node.js Bug Bounty Program
• Participate in Responsible Security Disclosure
• Charter
• Code of Conduct
• Moderation Policy
• Current Project Team Members
• Emeritus Members

Charter

The Security Working Group manages all aspects and processes linked to Node.js security.

Responsibilities include:

• Define and maintain security policies and procedures for:
  • the core Node.js project
  • other projects maintained by the Node.js Technical Steering Committee (TSC).
• Work with the Node Security Platform to bring community vulnerability data into the foundation as a shared asset.
• Ensure the vulnerability data is updated in an efficient and timely manner. For example, ensuring there are well-documented processes for reporting vulnerabilities in community modules.
• Review and recommend processes for handling of security reports (but not the actual administration of security reports, which are reviewed by a group of people directly delegated to by the TSC).
• Define and maintain policies and procedures for the coordination of security concerns within the external Node.js open source ecosystem.
• Offer help to npm package maintainers to fix high-impact security bugs.
• Maintain and make available data on disclosed security vulnerabilities in:
  • the core Node.js project
  • other projects maintained by the Node.js Foundation technical group
  • the external Node.js open source ecosystem
• Promote the improvement of security practices within the Node.js ecosystem.
• Recommend security improvements for the core Node.js project.
• Facilitate and promote the expansion of a healthy security service and product provider ecosystem.

Private Node.js core security group

The Node.js Security Working Group is not responsible for managing incoming security reports to the security@nodejs.org address, nor is it privy to or responsible for preparing embargoed security patches and releases.

The Node.js TSC maintains primary responsibility for the management of private security activities for Node.js core but relies on the Node.js Security Working Group to recommend and help maintain policies and procedures for that management.

Node.js Bug Bounty Program

The Node.js project engages in an official bug bounty program for security researchers and responsible public disclosures.

The program is managed through the HackerOne platform at https://hackerone.com/nodejs with further details.

Participate in Responsible Security Disclosure

As a module author you can provide your users with security guidelines regarding any exposures and vulnerabilities in your project, based on a responsible dislcosure policy document we've already put in place.

You can show your users you take security matters seriously and drive higher confidence by following any of the below suggested actions:

1. Adding a SECURITY.md file in your repository that you can copy&paste from us. Just like having a contribution of code of conduct guidelines, a security guideline will help user or bug hunters with the process of reporting a vulnerability or security concern they would like to share.

2. Adding our Responsible Security Dislosure badge to your project's README which links to the SECURITY.md document.

Current Project Team Members

• bengl - Bryan English
• brycebaril - Bryce Baril
• ChALkeR - Сковорода Никита Андреевич
• cjihrig - Colin Ihrig
• dgonzalez - David Gonzalez
• deian - Deian Stefan
• drifkin - Devon Rifkin
• elexy - Alex Knol
• grnd - Danny Grander
• lirantal - Liran Tal
• MarcinHoppe - Marcin Hoppe
• mdawson - Michael Dawson
• mgalexander - Michael Alexander
• pxlpnk - Andreas Tiefenthaler
• sam-github - Sam Roberts
• SomeoneWeird - Adam Brady
• vdeturckheim - Vladimir de Turckheim

Emeritus Members

• digitalinfinity - Hitesh Kanwathirtha
• dougwilson - Doug Wilson
• evilpacket - Adam Baldwin
• gergelyke - Gergely Nemeth
• gibfahn - Gibson Fahnestock
• jasnell - James M Snell
• jbergstroem - Johan Bergström
• joshgav - Josh Gavant
• mcollina - Matteo Collina
• ofrobots - Ali Ijaz Sheikh
• roccomuso - Rocco Musolino
• shigeki - Shigeki Ohtsu

Code of Conduct

The Node.js Code of Conduct applies to this WG.

Moderation Policy

The Node.js Moderation Policy applies to this WG.