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

DM.4.02 - Encryption of Data at Rest Control Guidance

DM.4.02 - Encryption of Data at Rest

Control Statement

Red, orange, and yellow data at rest is encrypted.

Context

Encrypting data at rest helps ensure the confidentiality and integrity of that data. In the event a production instance, data store, or backup is compromised, without encryption, the data is near certain to be accessed, modified, and/or stolen. Encrypting sensitive data at rest adds another roadblock and layer of complexity for the adversary and helps protect customer, employee, and partner data.

Scope

This control applies to red, orange, and yellow data stored in the production environment and to any enduser devices that store such data. The production environment includes all endpoints and cloud assets used in hosting GitLab.com and its subdomains. This may include third-party systems that support the business of GitLab.com

Ownership

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 Encryption of Data at Rest control issue.

Examples of evidence an auditor might request to satisfy this control:

Guidance

This control can be tested by verifying the at-rest encryption status for any production resources. For compute instances, this can be done by verifying the compute resource's drive encryption status. For other resources such as managed databased (e.g., RDS and CloudSQL), this can be done by verifying the at rest encryption status through the resource's dashboard or other summary. For vendors such as GCP who encrypt data at rest by default, consider providing vendor's documentation showing the default at rest encryption.

Policy Reference

Framework Mapping