Add Industry Insights as core competency for Dedicated SecComp team

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.

Our team, along with Public Sector Sales, are the closest to the changes that are proposed and ultimately made to authoritative sources of security and compliance requirements. This is way more than updates to regulations, but often the executive orders, directives, and even "guidance that is actually mandatory". We often find out about these changes early before they go into effect, and are regularly asked to weigh in on them. Finally, it is our job as security compliance practitioners who focus on the US public sector to influence these changes and give GitLab as much time as possible to prepare for them.

Examples of where we contribute include:

• Public comment on FedRAMP guidance and control baselines
• RFIs related to public sector security/compliance topics
• Executive orders and follow-up guidance
• NSA/CISA guidance that will become mandatory requirements via updated control baselines
• Following CMMC rulemaking process

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

---