Garden Linux has a growing community of volunteers and users. The Garden Linux community has adopted the following security response process to ensure we responsibly handle critical issues.

Security vulnerabilities should be handled quickly and sometimes privately. The primary goal of this process is to reduce the total time users are vulnerable to publicly known exploits. The Garden Linux Security Team is responsible for organizing the entire response including internal communication and external disclosure but will need help from relevant developers and release managers to successfully run this process. The Garden Linux Security Team consists of the following volunteers:

• Christian Cwienk, (@ccwienk)
• Dirk Marwinski, (@marwinski)
• Andre Russ, (@gehoern)
• Matthias Sohn, (@msohn)
• Frederik Thormaehlen, (@ThormaehlenFred)
• Martin Vladev, (@mvladev)

The Garden Linux community asks that all suspected vulnerabilities be privately and responsibly disclosed. If you've found a vulnerability or a potential vulnerability in Garden Linux please let us know by writing an e-mail to [email protected]. We'll send a confirmation e-mail to acknowledge your report, and we'll send an additional e-mail when we've identified the issue positively or negatively.

If you know of a publicly disclosed vulnerability please IMMEDIATELY e-mail to [email protected] to inform the Garden Linux Security Team about the vulnerability, so they may start the patch, release, and communication process.

If possible the Garden Linux Security Team will ask the person making the public report if the issue can be handled via a private disclosure process (for example if the full exploit details have not yet been published). If the reporter denies the request for private disclosure, the Garden Linux Security Team will move swiftly with the fix and release process. In extreme cases GitHub can be asked to delete the issue but this generally isn't necessary and is unlikely to make a public disclosure less damaging.

For each vulnerability a member of the Garden Linux Security Team will volunteer to lead coordination with the "Fix Team" and is responsible to send disclosure e-mails to the rest of the community. This lead will be referred to as the "Fix Lead." The role of the Fix Lead should rotate round-robin across the Garden Linux Security Team. The Garden Linux Security Team may decide to bring in additional contributors for added expertise depending on the area of the code that contains the vulnerability. All of the time lines below are suggestions and assume a private disclosure. The Fix Lead drives the schedule using his best judgment based on severity and development time. If the Fix Lead is dealing with a public disclosure, all time lines become ASAP (assuming the vulnerability has a CVSS score >= 7; see below). If the fix relies on another upstream project's disclosure time line, that will adjust the process as well. We will work with the upstream project to fit their time line and best protect our users.

The Fix Lead will work quickly to identify relevant engineers from the affected projects and packages and CC those engineers into the disclosure thread. These selected developers are the Fix Team. The Fix Lead will give the Fix Team access to a private security repository to develop the fix.

The Fix Lead and the Fix Team will create a CVSS using the CVSS Calculator. The Fix Lead makes the final call on the calculated CVSS; it is better to move quickly than make the CVSS perfect. The Fix Team will notify the Fix Lead that work on the fix branch is complete once there are LGTMs on all commits in the private repository from one or more maintainers. If the CVSS score is under 7.0 (a medium severity score) the Fix Team can decide to slow the release process down in the face of holidays, developer bandwidth, etc. These decisions must be discussed on the private Garden Linux Security mailing list.

With the fix development underway, the Fix Lead needs to come up with an overall communication plan for the wider community. This Disclosure process should begin after the Fix Team has developed a Fix or mitigation so that a realistic time line can be communicated to users. The Fix Lead will inform the Garden Linux mailing list that a security vulnerability has been disclosed and that a fix will be made available in the future on a certain release date. The Fix Lead will include any mitigating steps users can take until a fix is available. The communication to Garden Linux users should be actionable. They should know when to block time to apply patches, understand exact mitigation steps, etc.

The Release Managers will ensure all the binaries are built, publicly available, and functional before the Release Date. The Release Managers will create a new patch release branch from the latest patch release tag + the fix from the security branch. As a practical example if v184.0 is the latest patch release in Garden Linux, a new branch will be created called v184.1 which includes only patches required to fix the issue. The Fix Lead will cherry-pick the patches onto the master branch and all relevant release branches. The Fix Team will LGTM and merge. The Release Managers will merge these PRs as quickly as possible. Changes shouldn't be made to the commits even for a typo in the CHANGELOG as this will change the git sha of the already built and commits leading to confusion and potentially conflicts as the fix is cherry-picked around branches. The Fix Lead will request a CVE from the SAP Product Security Response Team via email to [email protected] with all the relevant information (description, potential impact, affected version, fixed version, CVSS v3 base score and supporting documentation for the CVSS score) for every vulnerability. The Fix Lead will inform the Garden Linux mailing list and announce the new releases, the CVE number (if available), the location of the binaries, and the relevant merged PRs to get wide distribution and user action.

As much as possible this e-mail should be actionable and include links how to apply the fix to users environments; this can include links to external distributor documentation. The recommended target time is 4pm UTC on a non-Friday weekday. This means the announcement will be seen morning in Pacific, early evening in Europe, and late evening in Asia. The Fix Lead will remove the Fix Team from the private security repository.

These steps should be completed after the Release Date. The retrospective process should be blameless.

The Fix Lead will send a retrospective of the process to the Garden Linux mailing list including details on everyone involved, the time line of the process, links to relevant PRs that introduced the issue, if relevant, and any critiques of the response and release process. The Release Managers and Fix Team are also encouraged to send their own feedback on the process to the Garden Linux mailing list. Honest critique is the only way we are going to get good at this as a community.

The private or [public disclosure process(#public-disclosure-process) should be triggered exclusively by writing an e-mail to [email protected].

Garden Linux security announcements will be communicated by the Fix Lead sending an e-mail to the Garden Linux mailing list (reachable via [email protected]) as well as posting a link in the Garden Linux Slack channel. Public discussions about Garden Linux security announcements and retrospectives, will primarily happen in the Garden Linux mailing list. Thus Garden Linux community members who are interested in participating in discussions related to the Garden Linux Security Release Process are encouraged to join the Garden Linux mailing list (how to find and join a group)

The members of the Garden Linux Security Team are subscribed to the private [Garden Linux Security mailing list](https://groups.google.com/forum/#!forum/gardenlinux-security (reachable via [email protected].