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

Security WG meeting 2017-10-12 #52

Closed
vdeturckheim opened this issue Oct 10, 2017 · 8 comments
Closed

Security WG meeting 2017-10-12 #52

vdeturckheim opened this issue Oct 10, 2017 · 8 comments

Comments

@vdeturckheim
Copy link
Member

vdeturckheim commented Oct 10, 2017

When

Thursday, Aug 12th, 2017, 20:00 UTC: other timezones

Where

Agenda

@evilpacket
Copy link
Contributor

Would be good to recap quickly some of the discussion that happened at Node Interactive security dinner and raise those items for group commentary.

Things I remember discussing not already on the agenda

  • Committing to HackerOne for core & community (modules) reporting of vulnerabilities
  • Defining who can see what during the process
  • Documenting in detail the process for vulnerability ingesting, triage, management and disclosure,
    ISO 29147 [zip]

Some additional evidence with regard to HackerOne in the form of compliance with the ISO 29147 / ISO 30111

@joshbw
Copy link

joshbw commented Oct 12, 2017

I can't make it today, but for "Have node become a CNA, so it can issue its own CVEs" one discussion point is whether it makes sense to make that effort ourselves, or simply use HackerOne (which is a CNA) to issue CVEs

@sam-github
Copy link
Contributor

I'll setup the call info in 20 minutes, doing it late makes the hangouts work better.

@sam-github
Copy link
Contributor

I posted the call URL: https://hangouts.google.com/hangouts/_/jyz5dlubsnh4vjajxajcwmgoeae

The call starts in one hour, the Node.js calendar is wrong, I'll see if I can change it (I think I was given permission).

@sam-github
Copy link
Contributor

@Trott I think you tried to give me edit permission on the Node.js Foundation calendar, but I can't move the sec-wg meeting time to the correct one (an hour from now, 1pm PST).

Can you try again? Or did I miss an invite email I had to accept? Not really sure how it works.

Or @mhdawson or @MylesBorins , do either of you have the power to give me edit access to the foundation calendar? Michael, can you sync up the calendar time with the correct time for this meeting?

@Trott
Copy link
Member

Trott commented Oct 12, 2017

@Trott I think you tried to give me edit permission on the Node.js Foundation calendar, but I can't move the sec-wg meeting time to the correct one (an hour from now, 1pm PST).

No, wasn't me. Maybe @williamkapke?

I moved the meeting time to 1PM PDT.

@williamkapke
Copy link

RE: Calendar Access:
https://github.com/nodejs/admin#nodejs-foundation-calendar

@sam-github
Copy link
Contributor

sam-github commented Oct 12, 2017

reminder: meeting starting in a couple minutes @nodejs/security-wg

patrickm68 added a commit to patrickm68/security-wg-process that referenced this issue Sep 14, 2023
Close: nodejs/security-wg#52
Close: nodejs/security-wg#53
PR-URL: nodejs/security-wg#55
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
mattstern31 added a commit to mattstern31/security-wg-process that referenced this issue Nov 11, 2023
Close: nodejs/security-wg#52
Close: nodejs/security-wg#53
PR-URL: nodejs/security-wg#55
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants