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

docs: add working group details #5

Merged
merged 10 commits into from
Mar 10, 2024
66 changes: 64 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,2 +1,64 @@
# security-wg
Express.js Security Working Group
# Security Working Group

## Charter

The Security Working Group manages all aspects and processes linked to the Express Project's security, and is responsible for managing incoming security reports, and responsible also to prepare patches or releases. The nature of this task is sensitive, so only the Security triage team, Repo Captains and TC members will be involved in it.

### Responsibilities

- Define the Security triage role
- Define and maintain security policies and procedures for the project and the packages in scope (see [this spreadsheet for scope details](https://docs.google.com/spreadsheets/d/1Qi7B78K6R_RyFloAcrcizL2oYawwMEmdKjgzC_Lik9Q/edit#gid=475621832))
- Provide guidance to the ecosystem on how to build more secure middleware
- Review and recommend processes for handling of security reports.
- Promote improvement of security practices within the Express project's ecosystem (For example: [OSSF Scorecard](https://github.com/expressjs/discussions/issues/162), threat model, etc..)
- Recommend security improvements for the project and the packages in scope
- Support the TC team on security triage as needed
- Support initiatives from the [OpenJS Foundation Security Collab Space](https://github.com/openjs-foundation/security-collab-space).
- Support initiatives from the OpenSSF [Best Practices for Open Source Developers Working Group](https://github.com/ossf/wg-best-practices-os-developers).

## Current Initiatives

We are currently defining the Initiatives for 2024, [feel free to participate](https://github.com/expressjs/security-wg/issues/1).

| Initiative | Champion | Status | Links |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will fix the pretty format of this table for md in a follow-on PR :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes 🙏

|------------|----------|--------|-------|
| OSSF Scorecard | [@inigomarquinez](https://github.com/inigomarquinez) | In progress | [#2](https://github.com/expressjs/security-wg/issues/2)|
UlisesGascon marked this conversation as resolved.
Show resolved Hide resolved
| Threat Model | _TBC_ | In progress | [#3](https://github.com/expressjs/security-wg/issues/3) |
| Support OSTIF Audit | [@UlisesGascon](https://github.com/ulisesgascon) | In progress | [#6](https://github.com/expressjs/security-wg/issues/6)

## Members

The Security Working Group is composed of two groups of members: the Security Triage Team and the Regular members. The regular members are responsible for the public facing activity of the group, while the Security Triage Team is responsible for the security triage process.

### Security Triage Team

- [Adam Ruddermann](https://github.com/ruddermann)
- [Chris de Almeida](https://github.com/ctcpip)
- [Jean Burellier](https://github.com/sheplu)
- [Marco Ippolito](https://github.com/marco-ippolito)
- [Rafael Gonzaga](https://github.com/RafaelGSS)
- [Ulises Gascón](https://github.com/UlisesGascon)
- [Wes Todd](https://github.com/wesleytodd)

### Team Members
- [Adam Ruddermann](https://github.com/ruddermann)
- [Carlos Serrano](https://github.com/carpasse)
- [Chris de Almeida](https://github.com/ctcpip)
- [Íñigo Marquínez Prado](https://github.com/inigomarquinez)
- [Jean Burellier](https://github.com/sheplu)
- [Marco Ippolito](https://github.com/marco-ippolito)
- [Rafael Gonzaga](https://github.com/RafaelGSS)
- [Ulises Gascón](https://github.com/UlisesGascon)
- [Wes Todd](https://github.com/wesleytodd)

## Meetings

The Security Working Group meets every two weeks. Meetings are held on Zoom and are recorded or directly streamed to Youtube. The meeting is open to the public. The agenda and meeting notes are published in this repository. The calendar entries are available in the [OpenJS Foundation calendar](https://openjsf.org/collaboration).

## Offline Discussions

The Security Working Group uses the [GitHub issues](https://github.com/expressjs/security-wg/issues) for offline discussions. The discussions are open to the public and anyone can participate. Also, the group uses the channel `#express-security-wg` in the [OpenJS Foundation Slack](https://openjsf.org/collaboration) for real-time discussions.

## Code of Conduct

The [Express Project's CoC](https://github.com/expressjs/express/blob/master/Code-Of-Conduct.md) applies to this repo.