|
| 1 | +# Node.js Security Team Meeting 2025-03-27 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: https://www.youtube.com/watch?v=K4IFJUZoxAo |
| 6 | +* **GitHub Issue**: https://github.com/nodejs/security-wg/issues/1460 |
| 7 | +* **Minutes Google Doc**: https://docs.google.com/document/d/1-GLK0d3N6Y7a0t1qX88W-U6e3d9-XrWOx99BE6bxr9Y/edit?tab=t.0 |
| 8 | + |
| 9 | +## Present |
| 10 | + |
| 11 | +* Security wg team: @nodejs/security-wg |
| 12 | +* Ulises Gascón: @UlisesGascon |
| 13 | + |
| 14 | +* Nguyen Duc Thien: @iuuukhueeee |
| 15 | +* Rafael Gonzaga: @RafaelGSS |
| 16 | +* Michael Dawson: @mhdawson |
| 17 | +* Marco Ippolito: @marco-ippolito |
| 18 | + |
| 19 | +## Agenda |
| 20 | + |
| 21 | +## Announcements |
| 22 | + |
| 23 | +*Extracted from **security-wg-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. |
| 24 | + |
| 25 | +- [X] Vulnerability Review - https://github.com/nodejs/nodejs-dependency-vuln-assessments/issues |
| 26 | +- [X] OpenSSF Scorecard Monitor Review: |
| 27 | +- The pkgjs org will probably track it too (separately) |
| 28 | +- No PR yet. Ulises is fixing the author commit |
| 29 | + |
| 30 | +### nodejs/node |
| 31 | + |
| 32 | +* src: add WDAC integration (Windows) #54364 |
| 33 | + * We did a careful review with Robert on this feature again |
| 34 | + * Three new change requests |
| 35 | + * Add typings |
| 36 | + * Update documentation to REPLACEME instead of v24.0.0 |
| 37 | + * Update PR description for Notable Change section |
| 38 | + * We’ll see if Yagiz will have time to review this PR again or dismiss his request changes |
| 39 | + * We’ll mention it in the next TSC meeting for visibility |
| 40 | + * No objections so far, so unless there new ones after mention in TSC meeting, we’ll plan to |
| 41 | + land after current comments are addressed. |
| 42 | + |
| 43 | +* \[StepSecurity\] Apply security best practices #57535 |
| 44 | + * Have being doing security course with Carlos |
| 45 | + * CodeQL could fill some important security gaps, have enabled on security wg repo |
| 46 | + * Have been learning some good stuff |
| 47 | + * Next action is to create an internal blog post to Node.js collaborators which share what was |
| 48 | + learned and next steps. |
| 49 | + * Most urgent is to document how to be more secure when using GitHub Actions |
| 50 | + |
| 51 | +### nodejs/security-wg |
| 52 | + |
| 53 | +* Update on CVEs for EOL Release Lines – MITRE Removal & Next Steps #1443 |
| 54 | + * Marco is working with HackerOne to update some existing CVEs for older EOL lines |
| 55 | + * The next step is to create a ticket in their support |
| 56 | + |
| 57 | +* Node.js maintainers: Threat Model #1333 |
| 58 | + * Update to include: add impairing ability to the project day 2 day |
| 59 | + |
| 60 | +* OpenJS Security Compliance Checker [#1440](https://github.com/nodejs/security-wg/issues/1440) |
| 61 | + * Ulises has replaced the issue body to use the current IDs, issues and docs. Also he will do a demo in the next meeting on the visionBoard + FortSphere capabilities for Node.js Org (ref) |
| 62 | + |
| 63 | +* OpenSSF Scorecard Report Updated #1459 |
| 64 | + |
| 65 | +* Review Code Scanning Alerts #1453 |
| 66 | + * The plan is to review it on the next meeting |
| 67 | + |
| 68 | +* Audit build process for dependencies #1037 |
| 69 | + * No updates this week |
| 70 | + |
| 71 | +* Automate security release process #860 |
| 72 | + * Changelog and commit message fix for security releases |
| 73 | + |
| 74 | +## Q&A, Other |
| 75 | + |
| 76 | +## Upcoming Meetings |
| 77 | + |
| 78 | +* **Node.js Project Calendar**: <https://nodejs.org/calendar> |
| 79 | + |
| 80 | +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |
| 81 | + |
0 commit comments