[Starlingx-discuss] Intel security process.....

[Jones, Bruce E]

As discussed at the team meeting today, we're going to provide more transparency on the Intel internal security process.  While this is very much our burden to carry, the work impacts the project and needs to be discussed with the community.

We have completed the first two phases of the process.  The second phase included a deep security threat review which resulted in several new work items for the team to address.

The major deliverables of the 3rd phase of the security process are:

*         Don't implement backdoors

*         Document APIs and Interfaces

*         Do not use banned C functions

*         Validate inputs

*         Compile with defenses enabled

*         Conduct manual code reviews

*         Complete static analysis

*         Create security and privacy validation plan

*         Complete security risk evaluation of open source components

*         Remove software debug access

Some of these items are in progress (e.g. API documentation, static analysis) and have or will result in work items for the project.  Some of them are entirely internal (e.g. security risk evaluation).  Some will result in code changes, some will not.   Some are binary (thou shall / shall not) and some are quite nuanced.   The purpose behind it all is to help the project identify, manage and address security and privacy issues.

We have been tracking this work internally.  In the interests of openness and collaboration, I'm going to ask the team to also open Stories for this work and work more openly.

I would like to suggest that the Security team needs to meet soon and have a discussion as to how to prioritize this work, and in particular, how to handle potential Critical/High vulnerabilities in the software that may be found in the course of this work.

There is one more thing I'd like to clarify.  This work does not need to be complete for the October release.  I would like to see this part of the work complete by the end of the year, if possible.  Of course, any Critical/High vulnerabilities or issues found need to be addressed urgently.

I am happy to answer any questions on this topic.

          brucej
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20180822/3f30680b/attachment.html>