Encryption Policy

Encryption is a process in which data is encoded so that it remains hidden from or inaccessible to unauthorized users. It helps securely protect data that you don’t want anyone to have access to. By encrypting our data at rest and in transit, we can better protect private, proprietary and sensitive data and can enhance the security of communication between client applications and servers.

Scope

This control is applicable to the production environment and any end user devices that store such data. The production environment includes all endpoints and cloud assets used in hosting GitLab.com and its subdomains. This also includes the GitLab Dedicated single-tenant SaaS offering. This may also include third-party systems that support the business of GitLab.com.

Note on Scope

This control does not define security access controls, standards that may apply differently to data depending on what type of data it is, or recommendations on cryptographic settings for encryption. Those are managed in other documents. Refer to the GitLab Security Compliance Controls, the Data Classification Standard, and the GitLab Cryptography Standard respectively.

Roles & Responsibilities

Role Responsibility
GitLab Team Members Responsible for following the requirements in this policy
Business or System Owners Alignment to this policy and any related standards
Security Threat Mgmt Team Maintain this Encryption Policy and associated standards
Security Management (Code Owners) Responsible for approving significant changes and exceptions to this policy

Procedure

Encryption at Rest

Data at rest is defined as data that is physically stored and not actively moving from one location to another (i.e.: device to device or network to network). This includes data stored on laptops, flash drives and hard drives.

Encryption Method

GitLab encrypts data at rest using a variety of tools including:

Encryption in Transit

Data in transit is defined as data that is actively moving from one location to another (i.e: device to device or network to network). This includes data transferred over public networks such as the internet.

Encryption Method

GitLab encrypts data in transit using a variety of tools including:

  • TLS Strict (SSL-Only Origin Pull), Always Use HTTPS, Universal SSL enabled through Cloudflare
  • Utilizing Google Cloud’s Technology which encrypts data in transit by default. Encryption keys are centrally managed by Google using Google’s Cloud Key Management feature. GitLab is responsible for basic key configuration including assigning key ring location and key rotation cadence.
  • Utilizing AWS default capabilities which encrypts all network traffic between AWS data centers at the physical layer and all traffic at the network layer within a VPC and between peered VPCs where applicable and when using supported Amazon EC2 instance types.
  • Conducting Third Party Risk Management activities which includes a review of encryption methods utilized by our third party vendors where applicable.

Rolling your own Crypto

Please don’t roll your own crypto. If you really think you have a situation where it makes sense to do this, please don’t. If you really really think this is a good idea, it is still not and please don’t. If you’re absolutely sure you have an edge case where this makes sense, please engage with the GitLab Security Team first so they can work with you on finding an alternative.

Exceptions

Exceptions to this procedure will be tracked as per the Information Security Policy Exception Management Process.

References

Last modified April 10, 2024: Update product security section of the handbook to reflect current department structure (54e13e98)
View page source - Edit this page - please contribute. Creative Commons License