Add definition of fixed and remediated for GitLab vulnerabilities
Why is this change being made?
💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.
Following a discussion regarding vulnerabilities SLAs, whilst clarifying when a specific vulnerability finding would be considered fixed on a private issue it became clear that we have not specifically outlined when, from a security and especially an SLA perspective, a vulnerability can be considered fixed in the context of self hosted versus SaaS versus Dedicated environments. This MR seeks to address that lack of clarify and solicit input to ensure we're considering different team member concerns and perspectives on when we consider a vulnerability to be fully remediated. This is especially necessary to clearly define given our hybrid deployment models for GitLab, and different packaging mechanisms. Ultimately this MR seeks to be as transparent as possible on a shared definition of remediated to ensure our SLAs and procedures for addressing vulnerabilities fully consider the ways in which we need to remediate vulnerabilities, and when team members and GitLab users can consider a vulnerability fixed.
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-