Proposing High Residual Risk Rating for clean Very High Inherent Risk Vendors
Why is this change being made?
Currently, Very High (RED) and High (Orange SaaS) Inherent Risk vendors are assigned a Moderate Residual Risk if they meet Security Requirements. I am proposing that clean Very High Inherent Risk vendors are assigned a Residual Risk of High rather than Moderate. Logic as follows:
- Very High Residual Risk vendors (such as AWS) will always be more risky to GitLab than Orange SaaS vendors (such as Workday) even if they meet our requirements
- Stratification in our vendor population will aid reporting and allow us to quickly isolate our riskiest vendors
- Dropping residual risk one level for clean vendors will create uniformity and potentially enable us to avoid confusion related to a two level bump down for RED vendors
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
-