diff options
| author | Ed Maste <emaste@FreeBSD.org> | 2026-05-06 20:23:59 +0000 |
|---|---|---|
| committer | Ed Maste <emaste@FreeBSD.org> | 2026-05-07 13:46:16 +0000 |
| commit | cbd9256f85402c9710ee100a2d0b886d253deb5b (patch) | |
| tree | 19bcb952c444f92324b62dd062ed95bd7e53ae8c | |
| parent | c06ad42897d56a7b1b7414a03d0b880d16fec834 (diff) | |
Vulnerability reporting: Ask for more information
- Extend "Example code" to reference PoC explicitly
- Preferred "Credits" attribution
- AI use
Reviewed by: markj, oshogbo
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D56861
| -rw-r--r-- | website/content/en/security/reporting.adoc | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/website/content/en/security/reporting.adoc b/website/content/en/security/reporting.adoc index 1331f85dad..f38df608ab 100644 --- a/website/content/en/security/reporting.adoc +++ b/website/content/en/security/reporting.adoc @@ -27,7 +27,9 @@ All reports should contain at least: * A description of the vulnerability. * What versions of FreeBSD seem to be affected if possible. * Any plausible workaround. -* Example code if possible. +* Example code if possible, including a minimal, self-contained proof of concept (PoC) where feasible. +* The reporter's preferred form of attribution for the "Credits" line in any resulting Security Advisory, if desired. +* Whether any automated tools or artificial intelligence systems were used as part of the discovery process, and if so, which tools or models. Whenever possible, including the background, problem description, impact, and workaround (if applicable) using the templates for link:../advisory-template.txt[security advisories] and link:../errata-template.txt[errata notices] as appropriate would also be helpful. |