Jump to: navigation, search

StarlingX/Security

StarlingX Security Sub-project

Vulnerability Management Team Information

Team Operations

The Vulnerability Management Team meets biweekly to discuss ongoing security issues. These meetings are private and closed to the community as a whole until the embargo is lifted on a particular security issue. For ongoing security hardening and feature development, these discussions and specifications are completed in the open. Technical discussions beyond the specifications and reviews will be held on the community call held every Wednesday.

Vulnerability Management Process

The StaringX 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.
    1. “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)
      • Click “Next” button.
        • “Launchpad Web Page” should come back with “Further information:” text field.
        • Please take a look if similar bugs were identified by “Launchpad Web Page” to avoid duplicate bugs.
      • Please go to Starlingx bug reporting guidelines and use the template suggested.
        • 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)
      • Go to the bottom of the page and select “ √ This bug is a security vulnerability” checkbox.
      • Click under “Extra Options” arrow.
        • Add “stx.security” TAG.
        • Please add attachments to help development team to troubleshoot the bug.
      • Click “Submit Bug Report” button.
    2. Once the bug is created please go to “Other bug subscribers” at the right side frame.
      • Left click on “+ Subscribe someone else” link and you should get a “Subscribe someone else” pop up search window.
      • Please add the following users:
        • Ghada Khalil (gkhalil) WR
        • Bill Zvonar (billzvonar) WR
        • Brent Rowsell (brent-rowsell) WR
        • Cindy Xie (xxie1) Intel
        • Bruce Jones (brucej) Intel
        • Victor Rodriguez (vm-rod25) Intel
      • Link the CVE# if applicable using the "Link to CVE" option on the right hand side
  2. 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:

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

  • ToDo:
    • Evaluate this report and create Stories to address it (if needed).
    • Address issues raised in the Intel internal SAFE review