docs/security/obmc-security-response-team-guidelines.md

1 # Security response team guidelines
3 These are the guidelines for OpenBMC security responders, including the security
5 problems reported by the [security vulnerability reporting process][].
7 Each project within OpenBMC works independently to resolve security
8 vulnerabilities. The security response team helps the maintainers, provides
23    - Communicate by opening the GitHub draft security advistory as soon as the
36    - [Create the draft security advisory][] and populate its fields.
44    - Use private channels, for example, email, GitHub draft security advistory,
46    - Inform contacts this is private work as part of the OpenBMC security
55    - Submit the problem to another security response team, for example, the
56      [UEFI Security Response Team (USRT)][].
72       - Publish a security advisory to the affected OpenBMC repository.
79 github.com/openbmc/<REPO>/security/advisories. Please follow guidance in the
80 [OpenBMC Security Advisory Template][]. Add the openbmc security-response group
81 and other stakeholders to the advisory. 3. Review the security bulletin with
84 For example, independent bugs should have separate CVEs. A security advisory can
85 reference multiple CVEs. When the CVE is known, add it to the security advisory,
87 For example: This fixes CVE-yyyy-nnnnn. Doing so helps downstream security
90 coordinated disclosure, plan to release the fix and the security advisory on the
93 public) publish the security advisory, and email the security-response team.
95 [security vulnerability reporting process]: ./obmc-security-response-team.md
97 [uefi security response team (usrt)]: https://uefi.org/security
107 [create the draft security advisory]:
108 …https://docs.github.com/en/code-security/repository-security-advisories/creating-a-repository-secu…
109 [openbmc security advisory template]: obmc-github-security-advisory-template.md
113 The OpenBMC security response team has received the problem.
120 ## Template: OpenBMC Security Advisory
123 OpenBMC Security Advisory
141 ## Template: Security Advisory notice
143 When the Security Advisory is created, inform the OpenBMC community by sending
147 TO: openbmc-security@lists.ozlabs.org, openbmc@lists.ozlabs.org
148 SUBJECT: [Security Advisory] ${subject}
150 The OpenBMC Security Response team has released an OpenBMC Security Advisory:
153 An OpenBMC Security Advisory explains a security vulnerability, its severity,
155 about OpenBMC Security Response, see:
156 https://github.com/openbmc/docs/blob/master/security/obmc-security-response-team.md
164 - https://www.kernel.org/doc/html/v4.16/admin-guide/security-bugs.html
165 - https://oss-security.openwall.org/wiki/mailing-lists/distros
170 The security response team (SRT) is controlled by the OpenBMC Technical Steering
178   - Share OpenBMC security vulnerability information within their organization
181   OpenBMC security response. Here are some examples to consider:
183     publicly available and disclose security bugs to their users.  This includes
185   - Organizations which focus on BMC security research or security response.
187   roles, technical skills, and expertise responding to security incidents.
189   to avoid premature disclosure of security vulnerabilities by limiting
192 The security response team uses the `openbmc-security at lists.ozlabs.org`
194 membership reflects the composition of the security response team. The list
196 `https://lists.ozlabs.org/listinfo/openbmc-security`.
206 `for privately reporting OpenBMC security vulnerabilities` with description:
207 This email list is for privately reporting OpenBMC security vulnerabilities.
208 List membership is limited to the OpenBMC security response team. For more
210 https://github.com/openbmc/docs/blob/master/security/how-to-report-a-security-vulnerability.md
215 Thanks for your interest in OpenBMC security.  Subscriptions to the
216 openbmc-security@lists.ozlabs.org email list are by invitation only
217 and are typically extended only to security response team members.
218 For more information, see https://github.com/openbmc/docs/security or
219 attend a security working group meeting:
220 https://github.com/openbmc/openbmc/wiki/Security-working-group.
223 OpenBMC security response team