Page History

...

During the investigation and mitigation of a security issue, the CloudStack PPMC may involve other members of the community as necessary to verify a vulnerability or work on its mitigation. For the purpose of this wiki, this group of community members will be referred to as the "Remediation team."

• Upon receiving notice of a potential security issue, a remediation security team member will create a bug to track the investigation, this bug must be flagged as a security issue. Security flag should mean contents of ticket are not visible to non-security team members
• Remediation Security team investigates the issue to confirm/deny the presence of a vulnerability within CloudStack
• If issue is confirmed as a CloudStack vulnerability:
  • Remediation Security team notifies the Apache Security team
  • Remediation Security team assigns a risk rating to the vulnerability using the Common Vulnerability Scoring System
  • Remediation Security team works with reporter to get a chance to investigate and mitigate the issue in a timely manner before public announcement. This should be between 15-30 days, depending on the severity and complexity of the issue
  • Remediation Security team works with Apache Security Team to reserve a CVE Identifier for future public release
  • Remediation Security team works with appropriate code maintainer(s) to create patch to mitigate the issue
  • Testing is conducted to verify patch mitigates issue and does not cause regression errors
  • Remediation Security team creates a vulnerability announcement
  • Patch is committed to trunk and other supported branches that are affected.
  • A new CloudStack release is prepared and tested, containing the new security patch.
  • Remediation Security team posts vulnerability announcement to...
    • CloudStack dev list
    • CloudStack users list
    • CloudStack Security alerts web page
    • The Bugtraq mailing list
  • After announcement, CHANGES and NEWS files need to be updated to reflect the vulnerability and fix. This must happen AFTER the announcement.
  • Also after announcement, modify the Jira ticket so that the issue is now publicly viewable.
• After the vulnerability is addressed, the CloudStack community should review development processes to see how the community can minimize the chance of similar vulnerabilities being introduced in the future.

...

• Initial security information is only shared on a need-to-know basis outside the PPMC to verify the issue and work on mitigation.
• It is expected that for committers who are employed by companies using CloudStack, it is likely the companies will learn about the vulnerability before the general public. What must be stressed is the company must ensure the confidentiality of the issue before general release.
• As an issue is verified and mitigation is developed and tested, the remediation security team will communicate the latest information to all involved. For companies who have employees on the remediation security team, this can allow them to prepare (not publish) announcements and patches to provide to their customers.
• During the response procedure, the remediation security team will communicate their timeline. This is done to allow both remediation security team members and their employers to prepare their own announcements and patches for their customers.
• The target result is an orchestrated, simultaneous announcement across CloudStack and vendors. It is expected that the CloudStack remediation security team may announce shortly before vendors - we are ultimately responsible for CloudStack and to our community. The reverse, where vendors announce before CloudStack, is not acceptable.

...