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

TRN.1.01 - General Security Awareness Training Control Guidance

TRN.1.01 - General Security Awareness Training

Control Statement

All GitLab team-members complete security awareness training, which includes updates about relevant policies and how to report security events to the authorized response team. Records of training completion are documented and retained for tracking purposes.

Context

At GitLab, we use internal training modules developed by the Security Operations team as GitLab's security awareness training. In the past, security awareness training has only been a task associated with on-boarding as a new GitLab team-member. As we adopt new compliance frameworks and work towards an audit certification of some of these frameworks, we will need to increase the cadence of this training. Security awareness training can be seen as a hassle and disruption from normal work, but these trainings can have real value not only to GitLab as a company, but also to GitLab team members in their personal lives. Taking the time to go through this training will ensure team members are up to date on security best practices which will help to minimize GitLab's risk as a company.

Scope

This control applies to all GitLab team-members.

Ownership

Control ownership:

Process Owner:

People Ops are responsible for deploying the process to ensure 100% of employee testing. The GitLab compliance team is responsible for validating that every GitLabber has completed training in the last year. Security Ops is the owner of the content and effectiveness of the control. All GitLab team-members are responsible for completing their security awareness training.

Additional control information and project tracking

Non-public information relating to this security control as well as links to the work associated with various phases of project work can be found in the General Security Awareness Training control issue.

Policy Reference

Framework Mapping