GitLab
TMA-GITLAB-2.1.8
Ensure the build infrastructure is automatically scanned for vulnerabilities
Description
Scan the build infrastructure and its dependencies for vulnerabilities. It is recommended that this be done automatically. Automatic scanning for vulnerabilities detects known vulnerabilities in the tooling used by the build infrastructure and its dependencies. These vulnerabilities can lead to a potentially massive breach if not handled as fast as possible, as attackers might also be aware of such vulnerabilities.
Méthode de vérification
Méthode d'audit: Revue manuelle
Verify that your build infrastructure is reviewed for vulnerabilities. GitLab Runner is designed to run user-controlled scripts. To reduce the attack surface if a job is malicious, you can consider running them in their own network segment. This would provide network separation from other infrastructure and services.
Méthode de correction
Méthode de correction: Recommandation ou correctif d'infrastructure
Ensure security hardening for your build infrastructure. For a cloud environment, this could include: - Configuring runner virtual machines in their own network segment - Blocking SSH access from the Internet to runner virtual machines - Restricting traffic between runner virtual machines - Filtering access to cloud provider metadata endpoints For static host runner, whether bare-metal or virtual machine, you should implement security best practices for the host operating system: Malicious code executed in the context of a CI job could compromise the host, so security protocols can help mitigate the impact. Other points to keep in mind include securing or removing files such as SSH keys from the host system that may enable an attacker to access other endpoints in the environment.
Propriétés
- Systèmes d'exploitation
- Tous
- Étiquettes
- devsecopsgitlab
- Référence
- CIS GitLab Benchmark v1.0.1 - 2.1.8 Ensure the build infrastructure is automatically scanned for vulnerabilities