cyberstrikeus 4.10 Ensure secrets are not stored in Dockerfiles (Manual)
Profile Applicability
- Level 1 - Docker - Linux
Description
Do not store any secrets in Dockerfiles.
Rationale
Docker images are not opaque and contain information about the commands used to build them. As such secrets should not be included in Dockerfiles used to build images as they will be visible to any users of the image.
Impact
A proper secrets management process will be required for Docker image building.
Audit Procedure
Run the below command to get the list of images:
docker images
Run the below command for each image in the list above, and look for any secrets:
docker history <IMAGE_ID>
Alternatively, if you have access to Dockerfile for the image, verify that there are no secrets as described above.
Remediation
Do not store any kind of secrets within Dockerfiles. Where secrets are required during the build process, make use of a secrets management tool, such as the buildkit builder included with Docker.
Default Value
By default, there are no restrictions on storing config secrets in the Dockerfiles.
References
CIS Controls
v8
3 Data Protection
Develop processes and technical controls to identify, classify, securely handle, retain, and dispose of data.
v7
13 Data Protection
Data Protection