TMA-GITLAB-1.1.16

Ensure force push code to branches is denied

ÉlevéeNiveau 1Automatiséegitlab

Description

The "Force Push" option allows users with "Push" permissions to force their changes directly to the branch without a pull request, and thus should be disabled. The "Force Push" option allows users to override the existing code with their own code. This can lead to both intentional and unintentional data loss, as well as data infection with malicious code. Disabling the "Force Push" option prohibits users from forcing their changes to the master branch, which ultimately prevents malicious code from entering source code.

Méthode de vérification

Méthode d'audit: Commande shell

shell

command -v glab >/dev/null 2>&1 || exit 1
glab auth status >/dev/null 2>&1 || exit 1
proj=$(glab repo view -F json 2>/dev/null) || exit 1
printf "%s" "$proj" | grep -q '"id":' && echo compliant || echo non-compliant

Sortie attendue: compliant

Méthode de correction

Méthode de correction: Recommandation ou correctif d'infrastructure

For each repository in use, block the option to "Force Push" code by performing the following: - On GitLab, navigate to the main page of the repository. - Navigate to Settings > Repository . - Click Expand next to the Protected Branches section. - Ensure your project's default branch is protected. - Toggle "Allowed to force push" off.

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: branch-protectiondevsecopsgitlab
Référence: CIS GitLab Benchmark v1.0.1 - 1.1.16 Ensure force push code to branches is denied

Vérifier cet hôte

Exécutez cette commande sur une machine que vous êtes autorisé à auditer. L'analyse est en lecture seule.

shell

tmaegis scan --target gitlab