Removal of fields from Tech Stack Applications HB Page
Why is this change being made?
The Security Risk team, in collaboration with Security Compliance and IT, has identified the below fields as being largely inaccurate or not necessary to have documented within the Tech Stack:
Discussion on need_to_move_to_okta and saas here. These fields are not consistently utilized and maintained.
Discussion regarding compliance_scope here. Conversations have indicated that no teams utilize this field, scoping for Compliance activities is maintained as-needed by those DRIs outside of the tech stack. This field has been found to be inaccurate and not consistently maintained.
Related MR for removal of these fields from current Tech Stack entries
Author Checklist
-
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
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.