Adding Cognism to Tech Stack (Fixing 116947)
Tech Stack - Add New System
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 - Add New System
General Tech Stack Entry Tasks
-
Link the approved Procurement Requisition for the new system (if third-party system): - [Requisition link]
-
Populate all data fields for the new system within the 'Changes' tab of this MR. Commit when ready. More instructions are here. - Is this new system replacing an existing system in the Tech Stack?
-
Yes - Delete that existing system's entry from the Tech Stack using this MR as well. Next, create a Tech Stack Offboarding Issue. - [Issue link]
-
No
-
Access Tasks
-
Create an Issue to add the provisioners of the new system to the appropriate Google/Slack/GitLab groups: - [Issue link]
-
Add the new system to one of two Offboarding templates below. More instructions are here. -
Main Team Member Offboarding template - [MR link]
-
Department-level Offboarding template folder - [MR link]
-
Data Warehouse Question
- Does data from the new system need to be integrated into the Enterprise Data Warehouse (EDW) for reporting and analytics?
-
Yes - Create a 'New Data Source' Issue in the Data Project to discuss cost, development, etc. with the Data team. -
No
-
Examples of system data integrated into the EDW:
- The data will be used as part of a new Key Performance Indicator or Performance Indicator.
- The data needs to be part of lead-to-cash analysis.
- The data needs to be joined with Marketo, Salesforce, or NetSuite data for cross-system analysis.
Privacy Team to Complete
If the new system contains Personal Data, has a Privacy Review been completed?:
-
If system contains Orange/Red Personal Data: -
Yes - Link a completed Vendor Privacy Review Issue, Coupa approval, or Zip approval (https://gitlab.coupahost.com/requisition_headers/2344) -
No - Complete Privacy Review Issue
-
-
If system contains Yellow Personal Data (GitLab Team Member Names/Emails): -
Yes - a Data Processing Agreement (DPA) was executed between GitLab and the Vendor -
No - a DPA is not in place - Privacy Team will be in contact about completing a DPA, which is required for this Tech Stack Addition
-
-
If system contains only Green Data or contains no Personal Data, a Privacy Review is not required.
Security Risk to Complete
-
If applicable, the Security Risk Engineer who created this MR should self-assign and unassign @ndevarajan
-
Create TS Add and BIA Tracking Issue: - [Tracking Issue link]
Business Technology to Complete
@marc_disabatino)
To-dos before merging (-
Ensure all sections/action items are completed.
/cc @gitlab-com/internal-audit @disla @gitlab-com/gl-security/security-assurance/security-risk-team
Edited by Eugene McCrann