Skip to content

Update Composition Analysis page with near breached SLA vulns

Orin Naamanrequested to merge
add-near-miss-vulns-to-ca-handbook-page into main

Why is this change being made?

This merge request makes several minor editorial improvements to documentation for a security team's rotation process. The changes include fixing grammar and punctuation (like changing "e.g." to "e.g.," and "help resolving" to "help resolve"), improving sentence clarity and flow, and adding a new section that provides specific guidance on handling security vulnerabilities that are approaching their deadline for resolution. The updates also clarify procedures for incident management and security scanning processes, making the documentation more precise and easier to follow for engineers working on security-related tasks.

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

CHANGEME

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
    • The when to get approval handbook section explains when DRI approval is required
    • The who can approve handbook section explains how to identify the DRI
    • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
    • The approver may merge the MR. If they approve but don't merge, you can merge.
  • 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

  • Update Composition Analysis page with near breached SLA vulns

Merge request reports