Skip to content
29 changes: 29 additions & 0 deletions doc/guides/security-steward-on-off-boarding.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Security Steward Onboarding/OffBoarding

## Onboarding

* Confirm the new steward agrees to keep all private information confidential
to the project and not to use/disclose to their employer.
* Add them to the security-stewards team in the GitHub nodejs-private
Comment thread
mhdawson marked this conversation as resolved.
organization
* Add them to the standard team in H1 using this
[page](https://hackerone.com/nodejs/team_members);
Comment thread
mhdawson marked this conversation as resolved.
Outdated
* Add them to the
[jenkin-admins team](https://GitHub.com/orgs/nodejs/teams/jenkins-admins)
in the GitHub nodejs org. This is needed for them to be able
to lock/unlock the CI during a security release.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't object to this, but this is a change -- currently locking/unlocking the CI for a security release is documented as being something to request the build team to do (see the template issue text for "Notify build-wg of upcoming security release date by opening an issue in nodejs/build to request WG members are available to fix any CI issues." in https://github.com/nodejs/node/blob/master/doc/guides/security-release-process.md).

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Ok that makes sense to me. I'll remove that part for now.

Comment thread
mhdawson marked this conversation as resolved.
Outdated
* Add them as managers of the
[nodejs-sec](https://groups.google.com/g/nodejs-sec/members) mailing list.

## Offboarding

* Remove them from security-stewards team in the GitHub nodejs-private
organization
Comment thread
mhdawson marked this conversation as resolved.
Outdated
* Unless they have access for another reason, remove them from the
standard team in H1 using this
[page](https://hackerone.com/nodejs/team_members).
* Unless they are a Jenkins admin for another reason, remove them from the
[jenkin-admins team](https://GitHub.com/orgs/nodejs/teams/jenkins-admins)
in the GitHub nodejs org.
Comment thread
mhdawson marked this conversation as resolved.
Outdated
* Downgrade their account to regular member in the
[nodejs-sec](https://groups.google.com/g/nodejs-sec/members) mailing list.