Shulou(Shulou.com)05/31 Report--

This article mainly shows you the "sample analysis of Openstack security update process and mechanism", which is easy to understand and well-organized. I hope it can help you solve your doubts. Let the editor lead you to study and study the "sample analysis of Openstack security update process and mechanism".

VMT (Vulnerability Management Team) this team is mainly responsible for dealing with security vulnerabilities in openstack and is responsible for developing related processes. My understanding is that VMT is actually a QA+ Release Management team, mainly from the process to ensure that security vulnerabilities can be properly addressed.

OSSG (Openstack Security Group) this team aims to improve the security of Openstack, including code, architecture, documentation, security recommendations for third-party components, etc. If OSSG discovers a security vulnerability, it needs to be handed over to VMT, and VMT needs to guarantee the handling and release of the vulnerability in the process; during this time, VMT will ask the OSSG team to evaluate and resolve the vulnerability. One of the most remarkable achievements of this team recently is the release of Openstack Security Guide. My personal understanding is that this team is mainly responsible for technical implementation, which is almost a Development Team.

OSSA (Openstack Security Advisories) OSSA is responsible for providing OSSG with Openstack's Security Advisories, that is, a solution to Openstack's own security vulnerabilities. Usually, once a security vulnerability in OSSA is identified, a cross-version patch needs to be released.

Generally speaking, Openstack officially maintains two stable versions (currently G and H) and a development version (currently I), and provides security patches for these versions at the same time. In order to improve system security, once OSSA is officially released, maintenance personnel should apply these patches in time to ensure that these security vulnerabilities will not be exploited by hackers.

SeriesStatusReleasesDateIcehouseUnder developmentDueApr 17, 2014HavanaCurrent stable release, security-supported2013.2Oct 17, 20132013.2.1Dec 16, 2013

2013.2.2Feb 13, 2014

GrizzlySecurity-supported2013.1Apr 4, 20132013.1.1May 9, 2013

2013.1.2Jun 6, 2013

2013.1.3Aug 8, 2013

2013.1.4Oct 17, 2013

2013.1.5Mar 20, 2014

FolsomEOL2012.2Sep 27, 20122012.2.1Nov 29, 2012

2012.2.2Dec 13, 2012

2012.2.3Jan 31, 2013

2012.2.4Apr 11, 2013

EssexEOL2012.1Apr 5, 20122012.1.1Jun 22, 2012

2012.1.2Aug 10, 2012

2012.1.3Oct 12, 2012

DiabloEOL2011.3Sep 22, 20112011.3.1Jan 19, 2012

CactusDeprecated2011.2Apr 15, 2011BexarDeprecated2011.1Feb 3, 2011AustinDeprecated2010.1Oct 21, 2010

Unlike OSSA, OSSN (Openstack Secuirty Notes) is responsible for providing security advice to commonly used third-party components since Openstack, because these components are not maintained by Openstack, such as a recent configuration of Mysql that caused a serious security vulnerability, then OSSN may publish a document instructing maintainers to bypass or not to use this configuration. It seems that OSSN has not been established for a long time. Here is the OSSN that has been released so far:

Https://wiki.openstack.org/wiki/Security_Notes

The above is all the contents of the article "sample Analysis of Openstack Security Update process and Mechanism". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.