StarlingX/Security

Vulnerability Management Team Information

 * Project Lead: Ghada Khalil <[mailto:Ghada.Khalil@windriver.com Ghada.Khalil@windriver.com]>
 * Technical Lead: Ghada Khalil <[mailto:Ghada.Khalil@windriver.com Ghada.Khalil@windriver.com]>
 * Contributors: Yue Tao <[mailto:Yue.Tao@windriver.com Yue.Tao@windriver.com]>; Mitch Thebeau <[mailto:Michel.Thebeau@windriver.com Michel.Thebeau@windriver.com]>; Zhixiong Chi <[mailto:zhixiong.chi@windriver.com zhixiong.chi@windriver.com]>
 * Past Contributors: Bruce Jones <[mailto:bruce.e.jones@intel.com bruce.e.jones@intel.com]>; Sanjay K Mukherjee <[mailto:sanjay.k.mukherjee@intel.com sanjay.k.mukherjee@intel.com]>; Cindy Xie <[mailto:cindy.xie@intel.com cindy.xie@intel.com]>; Gopi Bhat <[mailto:gopalkrishna.bhat@intel.com gopalkrishna.bhat@intel.com]>; Brent Rowsell; Ken Young

Team Operations
The Security/Vulnerability Management Team meets bi-weekly on Mondays to discuss ongoing security issues. These meetings are currently private. If you wish to join these meetings, please send your request to Ghada Khalil.

Vulnerability Management Process
The StarlingX Vulnerability Management team is the first point of contact for StarlingX security issues. They are responsible for the vulnerability handling and disclosure process.

See https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management

Banned C-Function Policy
The StarlingX Vulnerability Management team is recommending limiting the use of certain c functions given that they are prone to introducing security issues. The page below outlines the current policy:

See https://wiki.openstack.org/wiki/StarlingX/Security/Banned_C_Functions

Ongoing CVE Maintenance Policy
The StarlingX Vulnerability Management team is promoting ongoing security maintenance for StarlingX including CVE Analysis and Support. The current policy is outlined at: https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_Policy

StarlingX uses "vuls" (https://vuls.io/) for CVE scanning. The detailed scanning procedure is documented at: https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Scanning_Procedure

How to report security issues to StarlingX
If you think you’ve identified a vulnerability, please work with us to rectify and disclose the issue responsibly. By default, StarlingX considers all issues private until they have been triaged by the StarlingX Vulnerability Management Team. We provide two ways to report issues to the StarlingX VMT depending on how sensitive the issue is:
 * 1) Open the StarlingX bug tracking page and click the ‘Report a bug’ link at the top right of the page.
 * 2) “Launchpad Web Page” get back with “Report a bug --> Summary:” text field. Please describe the bug in a few words (include the CVE# if there is one)
 * 3) * Click “Next” button.
 * 4) ** “Launchpad Web Page” should come back with “Further information:” text field.
 * 5) ** Please take a look if similar bugs were identified by “Launchpad Web Page” to avoid duplicate bugs.
 * 6) * Please go to Starlingx bug reporting guidelines and use the template suggested.
 * 7) ** If you are reporting an existing CVE, please provide the CVE#, Vector (CVSSv2), Description, Link to NVD DB, Link to CentOS/RHEL bug (if applicable), CentOS Package version which includes the fix (if available)
 * 8) * Go to the bottom of the page where it says "This bug contains information that is:"
 * 9) ** Select "Public Security" if there is no embargo/sensitivity around the reported issue (ex: reporting a public CVE in an open-source package)
 * 10) ** Select "Private Security" if the issue is considered embargoed/sensitive. Only use this option if absolutely necessary.
 * 11) * Click under “Extra Options” arrow.
 * 12) ** Add “stx.security” TAG.
 * 13) ** Please add attachments to help development team to troubleshoot the bug.
 * 14) * Click “Submit Bug Report” button.
 * 15) Optional: Once the bug is created, please go to “Other bug subscribers” at the right side frame.
 * 16) * Left click on “+ Subscribe someone else” link and you should get a “Subscribe someone else” pop up search window.
 * 17) * Please add the following users:
 * 18) ** Ghada Khalil (gkhalil) - WR
 * 19) ** Yue Tao (wrytao) - WR
 * 20) * Link the CVE# if applicable using the "Link to CVE" option on the right hand side
 * 21) If the issue is extremely sensitive or you’re otherwise unable to use the bug tracker directly, please send an e-mail message to the Security Team’s members:
 * 22) *Ghada Khalil <[mailto:Ghada.Khalil@windriver.com Ghada.Khalil@windriver.com]>
 * 23) *Yue Tao <[mailto:yue.tao@windriver.com yue.tao@windriver.com]>

Team Objective / Priorities

 * Responsible for work items related StarlingX security

Tags
All story board stories and launchpad bugs created for this team should use the tag "stx.security".

Team Work Items

 * Story Board
 * All
 * Active Stories
 * Merged Stories
 * Launchpad Bugs
 * All
 * Open Bugs
 * Fixed Bugs