Skip to content

Updating the StORM Handbook Page to include linkage between Appetite and Tolerance

Kyle Smith requested to merge ks-update-storm-appetite-tolerance into master

Why is this change being made?

There is no linkage between GitLab's Security Risk Appetite and it's effect on what is considered within tolerance. This update creates a linkage between the risk appetite and our tolerance. Other changes were made as well:

  1. Distinguish between Appetite and Tolerance
  2. Emphasize this is specific to Operational Security Risk Management
  3. Update risk appetite guidance
  4. Add line to Historical and Current Record of GitLab's Risk Appetite for FY24
  5. Removed collapsable sections to enable scroll only (no clicks)
  6. Simplified scoring table and updated what's considered Low/Moderate/High
  7. Fixed typo and removed unused footnote.
  8. Replaced Risk Treatment with Risk Response

Closes https://gitlab.com/gitlab-com/gl-security/security-assurance/security-risk-team/storm/-/issues/300+

Author Checklist

  • 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 changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Kyle Smith

Merge request reports