<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Dear All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Probably you are already aware that Nova is moving towards reviewing Blueprints using Gerrit, and proposing a new template with several sections as you can find here:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://github.com/openstack/nova-specs/blob/master/specs/template.rst">https://github.com/openstack/nova-specs/blob/master/specs/template.rst</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On the other side, currently there is the effort being held by OSSG for performing a threat model analysis for OpenStack, which is great in my opinion and would lead to a baseline threat model analysis.
<o:p></o:p></p>
<p class="MsoNormal">But new features/Blueprints are being integrated all the time, and with them new potential Security risks at design time.
<o:p></o:p></p>
<p class="MsoNormal">(Please let me know if I am wrong, but I am not aware of required Security analysis for new Blueprints besides what the reviewers may identify during the approval process.)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">That said, I was wondering if it would be worth to push the inclusion of a “Security impact” section as part of the Blueprints definitions; and probably to start with the new Nova template approach.<o:p></o:p></p>
<p class="MsoNormal">I am not talking about requesting a detailed threat model analysis at the Blueprint definition stage, but to document at least high level Security implications that the Blueprint owner could identify for leveraging Security analysis/reviews
in earlier stages of features/components definitions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any thoughts appreciated.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks and Regards.<o:p></o:p></p>
<p class="MsoNormal">Cristian.<o:p></o:p></p>
</div>
</body>
</html>