Ensure scanners are in place to identify and prevent sensitive data in pipeline files

Como é verificado

Método de auditoria: Comando 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

Saída esperada

compliant

Como é corrigido

Método de correção: Orientação ou patch de infraestrutura

For every pipeline that is in use, set scanners that will identify and prevent sensitive data within it. - On the left sidebar, select Search or go to and find your project. - Select Build > Pipeline editor. - Copy and paste the following to the bottom of the .gitlab-ci.yml file. If an include line already exists, add only the template line below it. include: - template: Jobs/Secret-Detection.gitlab-ci.yml - Select the Validate tab, then select Validate pipeline. The message Simulation completed successfully indicates the file is valid. - Select the Edit tab. - Optional. In the Commit message text box, customize the commit message. In the Branch text box, enter the name of the default branch. - Select Commit changes.

Verificar este host

Execute isto em uma máquina que você tenha permissão para auditar. A varredura é somente leitura.

tmaegis scan --target gitlab --level 2