Skip to content

Add controlled document/policy for monitoring of GitLab.com

Marin Jankovski requested to merge mj/monitoring-policy into main

Why is this change being made?

Part of https://gitlab.com/gitlab-com/gl-security/security-assurance/governance-and-field-security/governance/security-governance/-/issues/132

This document is created to extract the specific requirements from https://handbook.gitlab.com/handbook/engineering/monitoring to ensure that the policy/definition section is not mixed with developer facing documentation.

The document itself is not only a policy, but based on https://handbook.gitlab.com/handbook/security/controlled-document-procedure/#creation, it should be sufficient to move us forward (confirmed in https://gitlab.com/gitlab-com/gl-security/security-assurance/governance-and-field-security/governance/security-governance/-/issues/132#note_1913182308).

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
  • 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
    • Division: If the update affects your division, share the MR in your division 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

Commits

  • Add controlled document policy for monitoring of GitLab.com
Edited by Marin Jankovski

Merge request reports