Security Risk Tech Stack Update (Post-FY24 BIA - Data Validation)

Tech Stack - Update Existing System

Mapping

Commit Name	Systems Updated
Titling, alphabetization	Systems listed under #4. Several Systems that were out of order.
Update #s 1-40	See 'TS Updates (Post-FY24 BIA - Data Validation)' tab here.
Update #s 41-92	See 'TS Updates (Post-FY24 BIA - Data Validation)' tab here.
Update #s 41-92 (Provisioners)	See 'TS Updates (Post-FY24 BIA - Data Validation)' tab here.
Upgraded DC/CST for "customers.gitlab.com (Web access only)", "customers.stg.gitlab.com/", "Anthropic", "OpenAI" ... and two Provisioner updates	Listed in Commit Name, plus "Optimal Workshop" and "Google 360 (through Search Discovery)"

Business/Technical System Owner or Delegate to Complete

Please do not merge before the Business Systems Analysts have reviewed and approved.

• Rename this MR's title to [System Name] - Tech Stack - Update Existing System
  • Changed MR title...
• Update data field(s) for the existing system within the 'Changes' tab of this MR. Commit update when ready. More instructions are here.

Are you changing the existing system's provisioner(s)?

• Yes. Create an Issue to add the new provisioner(s) of the system to the appropriate Google/Slack/GitLab groups:
  • <strong data-sourcepos="59:6-59:89">Security Risk Tech Stack Update (Post-FY24 BIA - Data Validation) - Provisioners</strong>
• No

Are you removing an existing system from the Tech Stack?

• Yes. Be sure to complete a Tech Stack Offboarding Issue as well.
• No. Systems identified for removal will be removed through individual MRs/Issues (standard process for removal).

Security Risk to Complete

Not required prior to merging

• Once updates are finalized and if necessary, communicate change to impacted parties (e.g., Security Compliance)

/cc @gitlab-com/gl-security/security-assurance/security-risk-team