Explorador de reglas
Explore todas las reglas de endurecimiento del catálogo. Filtre por plataforma, severidad, nivel de perfil y si la verificación puede automatizarse.
122 reglas encontradasde 16.927Página 3 de 5
| ID | Título | Plataforma | Severidad | Nivel | Verificación |
|---|---|---|---|---|---|
| TMA-GITLAB-1.4.3 | Ensure the access granted to each installed application is limited to the least privilege neededgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-1.5.1 | Ensure scanners are in place to identify and prevent sensitive data in codegitlab · Nivel 2 | gitlab | Media | 2 | Automatizada |
| TMA-GITLAB-1.5.2 | Ensure scanners are in place to secure Continuous Integration (CI) pipeline instructionsgitlab · Nivel 2 | gitlab | Media | 2 | Revisión manual |
| TMA-GITLAB-1.5.3 | Ensure scanners are in place to secure Infrastructure as Code (IaC) instructionsgitlab · Nivel 2 | gitlab | Media | 2 | Revisión manual |
| TMA-GITLAB-1.5.4 | Ensure scanners are in place for code vulnerabilitiesgitlab · Nivel 2 | gitlab | Media | 2 | Automatizada |
| TMA-GITLAB-1.5.5 | Ensure scanners are in place for open-source vulnerabilities in used packagesgitlab · Nivel 2 | gitlab | Media | 2 | Automatizada |
| TMA-GITLAB-1.5.6 | Ensure scanners are in place for open-source license issues in used packagesgitlab · Nivel 2 | gitlab | Media | 2 | Revisión manual |
| TMA-GITLAB-2.1.2 | Ensure all aspects of the pipeline infrastructure and configuration are immutablegitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.1.3 | Ensure the build environment is loggedgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.1.4 | Ensure the creation of the build environment is automatedgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.1.5 | Ensure access to build environments is limitedgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.1.6 | Ensure users must authenticate to access the build environmentgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.1.8 | Ensure the build infrastructure is automatically scanned for vulnerabilitiesgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.2.1 | Ensure build workers are single-usedgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.2.2 | Ensure build worker environments and commands are passed and not pulledgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.2.3 | Ensure the duties of each build worker are segregatedgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.2.4 | Ensure build workers have minimal network connectivitygitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.2.5 | Ensure run-time security is enforced for build workersgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.2.6 | Ensure build workers are automatically scanned for vulnerabilitiesgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.2.7 | Ensure build workers' deployment configuration is stored in a version control platformgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.2.8 | Ensure resource consumption of build workers is monitoredgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.3.1 | Ensure all build steps are defined as codegitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.3.2 | Ensure steps have clearly defined build stage input and outputgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.3.3 | Ensure output is written to a separate, secured storage repositorygitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |
| TMA-GITLAB-2.3.5 | Ensure access to build process triggering is minimizedgitlab · Nivel 1 | gitlab | Media | 1 | Revisión manual |