Skip to content

Secure & Defend cross-group approval process

Thiago Figueirórequested to merge
follow-up-secure-defend-delineation into master

Why is this change being made?

Iterate on the initial approval process for changes to Vulnerability Management schemata:

  1. Clarify boundaries with a diagram.
  2. Update the boundary from report schema to database schema.
  3. Specify change controls.

Related issues and MRs:

Author Checklist

  • Correct MR template applied (e.g blog post)
  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • 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.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack

Merge request reports