public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wang, Jian J" <jian.j.wang@intel.com>
To: "bugs@edk2.groups.io" <bugs@edk2.groups.io>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Laszlo Ersek <lersek@redhat.com>,
	"Zimmer, Vincent" <vincent.zimmer@intel.com>,
	"Cetola, Stephano" <stephano.cetola@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>
Subject: [RFC] Propose update of security bug handling process
Date: Fri, 12 Apr 2019 08:43:10 +0000	[thread overview]
Message-ID: <D827630B58408649ACB04F44C5100036258E05B7@SHSMSX107.ccr.corp.intel.com> (raw)

Hi,

Currently, we generally follow below process to handle security bugs.
But there're no document to describe the detailed working flow. There're
also discussions on lacking of important information, poor issue description
and no timely notification on update, etc.

       "0 - New Security Bug"
  -> "1 - Triage"
  -> "2 - Mitigation"
  -> "3 - Embargo"
  -> "4 - Disclosure"
  -> "5 - Exit";

I have a proposal at following page to elaborate the process and try to address
all problems reported so far. Following content is for discussion only. Once the
process is finalized, it will be moved to official edk2 wiki page.

https://github.com/jwang36/tianocore.github.io/wiki/Proposal-of-security-issue-process

Any opinions and suggestions are welcomed.

Regards,
Wang, Jian J


             reply	other threads:[~2019-04-12  8:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12  8:43 Wang, Jian J [this message]
2019-04-12 12:51 ` [RFC] Propose update of security bug handling process Laszlo Ersek
2019-04-15  5:36   ` [edk2-devel] " Wang, Jian J
2019-04-15 17:04     ` Laszlo Ersek
2019-04-16  6:06       ` Wang, Jian J
2019-04-16  6:33         ` Andrew Fish
2019-04-16  0:03     ` Vincent Zimmer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D827630B58408649ACB04F44C5100036258E05B7@SHSMSX107.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox