|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH RFC v2] Expand eligibility for the pre-disclosure list
As discussed on the xen-devel mailing list, expand eligibilty of the pre-disclosure list to include any public hosting provider, as well as software project: * Change "Large hosting providers" to "Public hosting providers" * Remove "widely-deployed" from vendors and distributors * Add rule of thumb for what contitutes a "genuine" * Add an itemized list of information to be included in the application, to make expectations clear and (hopefully) applications more streamlined. NOTE: This RFC is meant to be a way to start a discussion on the exact wording which will be voted on. Once it has gone through review from the xen-devel mailing list, I will post an "RC" and announce it on the Xen blog, as well as on xen-users. Once discussion seems to have converged, I will post a "FINAL" one, which I will put up for a vote. I hope to post an RC on the blog and on xen-users before I begin my Christmas holidays, in mid-December. v2: - Include "genuine" software providers, and a rule of thumb for "genuine" - Include evidence for software providers - Allow "a key signed with a key in the PGP strong set" as evidence - Require applicants to state they have read and understand policy and will abide by it - Minor suggested clarifications - Added version message at bottom - Made security aliases a requirement Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx> --- security_vulnerability_process.html | 67 +++++++++++++++++++++++++++++------ 1 file changed, 56 insertions(+), 11 deletions(-) diff --git a/security_vulnerability_process.html b/security_vulnerability_process.html index e305371..9eb7aa5 100644 --- a/security_vulnerability_process.html +++ b/security_vulnerability_process.html @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> <html xmlns="http://www.w3.org/1999/xhtml";> <head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta http-equiv="Content-Type" content="text/html" /> <title>Xen.org Security Problem Response Process</title> <meta name="description" content="Xen.org, home of the Xenï hypervisor, the powerful open source industry standard for virtualization."> <meta name="keywords" content="xen 2.0, xen 3.0, hypervisor, server consolidation, open source, ian pratt, virtualization, virtualisation, xen, xensource, security, vulnerability, process"> @@ -14,7 +14,7 @@ if(ns4)_d.write("<scr"+"ipt type=text/javascript src=/globals/mmenuns4.js><\/scr </script> <script type="text/javascript" src="/globals/menu_data_xenorg_main.js"></script> - <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"> + <meta http-equiv="Content-Type" content="text/html"> <link rel="shortcut icon" href="/favicon.ico"> </head> @@ -194,16 +194,27 @@ if(ns4)_d.write("<scr"+"ipt type=text/javascript src=/globals/mmenuns4.js><\/scr addresses (ideally, role addresses) of the security response teams for significant Xen operators and distributors.</p> <p>This includes:<ul> - <li>Large-scale hosting providers;</li> + <li>Public hosting providers;</li> <li>Large-scale organisational users of Xen;</li> - <li>Vendors of widely-deployed Xen-based systems;</li> - <li>Distributors of widely-deployed operating systems with Xen support.</li> + <li>Vendors of Xen-based systems;</li> + <li>Distributors of operating systems with Xen support.</li> </ul></p> <p>This includes both corporations and community institutions.</p> - <p>Here as a rule of thumb "large scale" and "widely deployed" means an - installed base of 300,000 or more Xen guests; other well-established - organisations with a mature security response process will be considered on - a case-by-case basis.</p> + <p>Here "provider", "vendor", and "distributor" is meant to + include anyone who is making a genuine service, available to the + public, whether for a fee or gratis. For projects providing a + service for a fee, the rule of thumb of "genuine" is that you + are offering services which people are purchasing. For gratis + projects, the rule of thumb for "genuine" is measured in terms + of the amount of time committed to providing the service. For + instance, a software project which has 2-3 active developers, + each of whom spend 3-4 hours per week doing development, is very + likely to be accepted; whereas a project with a single developer + who spends a few hours a month will most likey be rejected.</p> + <p>For organizational users, a rule of thumb is that "large-scale" + means an installed base of 300,000 or more Xen guests. Other + well-established organisations with a mature security response + process will be considered on a case-by-case basis.</p> <p>The list of entities on the pre-disclosure list is public. (Just the list of projects and organisations, not the actual email addresses.)</p> <p>If there is an embargo, the pre-disclosure list will receive @@ -229,8 +240,41 @@ if(ns4)_d.write("<scr"+"ipt type=text/javascript src=/globals/mmenuns4.js><\/scr <li>The planned disclosure date</li> </ul></p> - <p>Organisations who meet the criteria should contact security@xen if they wish to receive pre-disclosure of advisories. Organisations should not request subscription via the mailing list web interface, any such subscription requests will be rejected and ignored.</p> - <p>Normally we would prefer that a role address be used for each organisation, rather than one or more individual's direct email address. This helps to ensure that changes of personnel do not end up effectively dropping an organisation from the list</p> + <p>Organisations who meet the criteria should contact security@xen + if they wish to receive pre-disclosure of advisories. Please + include in the e-mail: <ul> + <li>The name of your organization</li> + <li>A brief description of why you fit the criteria, along + with evidence to support the claim</li> + <li>A security alias e-mail address (no personal addresses -- + see below)</li> + <li>A link to a web page with your security policy + statement</li> + <li>A statement to the effect that you have read this policy + and agree to abide by the terms for inclusion in the list, + specifically the requirements to regarding confidentiality + during an embargo period</li> + </ul></p> + <p>Evidence that will be considered may include the following: <ul> + <li>If you are a public hosting provider, a link to a web page + with your public rates</li> + <li>If you are a software provider, a link to a web page where + your software can be downloaded or purchased</li> + <li>If you are an open-source project, a link to a mailing + list archive and/or a version control repository + demonstrating active development</li> + <li>A public key signed with a key which is in the PGP "strong + set"</li> + </ul></p> + + <p>Organisations should not request subscription via the mailing + list web interface, any such subscription requests will be + rejected and ignored.</p> + <p>A role address (such as security@xxxxxxxxxxx) should be used + for each organisation, rather than one or more individual's + direct email address. This helps to ensure that changes of + personnel do not end up effectively dropping an organisation + from the list.</p> <h3>Organizations on the pre-disclosure list:</h3> @@ -253,6 +297,7 @@ if(ns4)_d.write("<scr"+"ipt type=text/javascript src=/globals/mmenuns4.js><\/scr <h2>Change History</h2> <ul> + <li><b>v1.4 Nov 2012:</b> Predisclosure list criteria changes</li> <li><b>v1.3 Aug 2012:</b> Various minor updates</li> <li><b>v1.2 Apr 2012:</b> Added pre-disclosure list</li> <li><b>v1.1 Feb 2012:</b> Added link to Security Announcements wiki page</li> -- 1.7.9.5 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |