These controls were prioritized based on our security compliance needs over the next 12-18 months and include controls related to SOC2 common criteria and PCI
Perform a gap analysis to establish a baseline/starting point for each of these prioritized controls
This gap analysis is currently underway. For more information on the methodology used for this project, please see the related project epic
Perform remediation work to bring each evaluated control to a state of "full compliance" (meaning we believe we would pass an audit of that control)
This work will begin in Q3 of FY2020
Perform testing of each control to validate that all control processes are operating effectively
This work will begin as controls are determined to be operating effectively
GitLab's Control Framework (GCF)
GitLab has adopted an umbrella control framework that provides compliance with a number of industry compliance requirements and best practices. For information about how we developed this framework and a list of all of our security controls, please see the security controls handbook page.
The GCF is mapped to the requirements for achieving a SOC2 certification, for more information please see our SOC2 page
SOX 404-focused IT general control testing: @MFarber
Controls: A control domain owner is the DRI for the rollout and operation for the controls in their respective domain(s):
The Security Compliance team is responsible for completing the activities which continually assess the design and operating effectiveness of the controls established by the GCF.
The purpose of a gap analysis is to identify gaps between GCF controls and documented GitLab process. Gap analysis project work is done in a private project due to the sensitive nature of the assessment findings. The project will have an issue for every GCF control in scope for the gap analysis. GitLab's first gap analysis can serve as an example for how future gap analyses can be organized and executed.
The remediation phase fills the gaps identified during the gap analysis and get each in-scope control into a state of audit readiness.
A control is considered to be remediated if:
The process addressing the requirements of the control (as defined by the security compliance team) is documented in the GitLab handbook
The process documented above is the same process being used by all GitLab team-member involved in operation of the security control
The collection of testing evidence that will prove the above 2 points can begin
Testing encompasses both "test of design" (sample of 1) and then if that passes, a test of "operating effectiveness" (random sampling)
**Note: If you have an urgent request and you're not getting a response from the above team tags, the security compliance managers (@mfarber & @jburrows001) have their cell phone numbers in their slack profiles. **