ProdSecEng Handbook Updates - For Act 2 Mission

Why is this change being made?

💡 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.

As part of the plan to make Act 2 changes official, I suggest we change our ProdSecEng team charter (and related pages) to reflect our new mission and way we will work. A few key changes:

• Removing the SecCapEng page, and moving the ways of working details into our team page. I rolled these out a few months ago, and as I understand it only ProdSecEng were following these workflows.
• Updated the team charter to cover the new mission, making clear call out to what is out of scope (tool intake, integration, and maintenance)
• Updated the ProdSec to Product page to focus on co-create, and de-emphasize the intake, maint, and sunset processes as those will gradually wind down as we hand tools over.

Updating this now means we have clear documentation to share with Product/Engineering when we being aligning on our new epics/initiatives.

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
    • 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

Commits

• Updating ProdSecEng handbook pages for new mission
• Updating ProdSecEng handbook to cover new mission and remove SCE page

---