Gitlab hero border pattern left svg Gitlab hero border pattern right svg

GCF Security Control Lifecycle

GCF Security Control Lifecycle

Process Overview

graph TD; 1[Preparation]-->2[Test of Design]; 2[Test of Design]-->3[Decision: TOD Pass]; 2[Test of Design]-->4[Decision: TOD Fail]; 4[Decision: TOD Fail]-->9[Remediation]; 3[Decision: TOD Pass]-->5[Test of OE]; 5[Test of OE]-->6[Decision: TOE Pass]; 6[Decision: TOE Pass]-->7[Operating]; 5[Test of OE]-->8[Decision: TOE Fail]; 8[Decision: TOE Fail]-->9[Remediation]; 9[Remediation]-->2[Test of Design]; 7[Operating]-->1[Preparation];

Lifecycle Phases Explained

As new GitLab security controls are identified that need to be implemented by the security compliance team for compliance or regulatory reasons, these controls follow an established process in order to make that implementation successful.

Preparation

As new GCF security controls are identified they first must be researched and contextualized to GitLab as a company and to the applicable GitLab systems. The Preparation phase of the control lifecycle covers this initial work required to get controls into a state of ready to be tested.

Additionally, GCF controls that have been previously tested but have an upcoming requirement for renewed testing enter this Preparation phase as well to research and confirm that any changes to the control processes are captured in the updated testing activity.

Testing

The testing activity consists of 3 major components:

  1. Filling out a control testing worksheet as described by the GitLab control testing manual (GitLab internal link)
  2. Validating observations (if any were noted during testing) with the observation owners
  3. Recording those observations (if any) according to the Security Compliance Observation Management process

After testing a decision is made about the controls:

Remediation

Remediation is the phase of the lifecycle where required changed are made to the design of the security control or the process of the control's operation. Remediation is either performed by the observation owner or is tracked by the observation owner if the observation remediation is blocked by another GitLab team's work. The security compliance team is responsible for tracking all validated observation and continually reporting on those observations to ensure they are tracked, prioritized appropriately, and escalated as needed to meet the security compliance program goals.

Operating

Controls that are tested with no observations noted during that testing activity are determined to be in an operational state. This indicates that the design and operating effectiveness of this control are at or above the level required to meet the current needs of the security compliance program.

Controls in an operating state will still need to be re-tested annually or quarterly (as determined by the risk rating of the control) to ensure no substantive changes have occured which would impact the design or operating effectiveness of that control; controls move from the operating state back into the preparation state to prepare the control for the next iteration of testing.

GIT is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license