GitLab's information security policies and standards are reviewed, updated if required, and approved by management, annually. Information security policies and standards are communicated to personnel through the GitLab Handbook.
The purpose of this control is to ensure GitLab's policies and procedures are kept up-to-date and relevant, changes are appropriately reviewed and approved, and GitLab team members have a way to track those changes.
Due to the nature of how GitLab operates and it's value of being iterative, continual updates are made to the related security policies and standards (as deemed necessary) that have been listed as in-scope for this control. Changes made to these procedures are always reviewed prior to being updated in GitLab's handbook. Evidence of changes can be identified via the related handbook page's markdown file in the www-gitlab-com project repo or by visiting the Handbook Changelog.
All policies and standards having a direct impact to how GitLab carries out it's IT/Security practices are in-scope for this control. Policies and standards impacting the broader organization have been determined to be entity level policies which are considered as part of the Entity Level Controls (ELC) documented within the Sarbanes-Oxley (SOX) Compliance Handbook page.
The specific policies and standards described in the Policy Reference section below are subject to this control.
On an annual cadence, GitLab's Information Security Policies are reviewed and approved by the appropriate level of management.
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 Policy and Standard Review control issue.