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.
120 reglas encontradasde 8597Página 1 de 5
| ID | Título | Plataforma | Severidad | Nivel | Verificación |
|---|---|---|---|---|---|
| TMA-GITHUB-1.1.3 | Ensure any change to code receives approval of two strongly authenticated usersgithub · Nivel 1 | github | Alta | 1 | Automatizada |
| TMA-GITHUB-1.1.4 | Ensure previous approvals are dismissed when updates are introduced to a code change proposalgithub · Nivel 1 | github | Alta | 1 | Automatizada |
| TMA-GITHUB-1.1.12 | Ensure verification of signed commits for new changes before merginggithub · Nivel 2 | github | Alta | 2 | Automatizada |
| TMA-GITHUB-1.1.14 | Ensure branch protection rules are enforced for administratorsgithub · Nivel 1 | github | Alta | 1 | Automatizada |
| TMA-GITHUB-1.1.16 | Ensure force push code to branches is deniedgithub · Nivel 1 | github | Alta | 1 | Automatizada |
| TMA-GITHUB-1.2.1 | Ensure all public repositories contain a SECURITY.md filegithub · Nivel 1 | github | Alta | 1 | Automatizada |
| TMA-GITHUB-1.3.3 | Ensure minimum number of administrators are set for the organizationgithub · Nivel 1 | github | Alta | 1 | Revisión manual |
| TMA-GITHUB-1.3.4 | Ensure Multi-Factor Authentication (MFA) is required for contributors of new codegithub · Nivel 2 | github | Alta | 2 | Automatizada |
| TMA-GITHUB-1.3.5 | Ensure the organization is requiring members to use Multi- Factor Authentication (MFA)github · Nivel 2 | github | Alta | 2 | Automatizada |
| TMA-GITHUB-1.3.7 | Ensure two administrators are set for each repositorygithub · Nivel 2 | github | Alta | 2 | Revisión manual |
| TMA-GITHUB-1.3.11 | Ensure an organization provides SSH certificatesgithub · Nivel 2 | github | Alta | 2 | Revisión manual |
| TMA-GITHUB-1.4.1 | Ensure administrator approval is required for every installed applicationgithub · Nivel 1 | github | Alta | 1 | Revisión manual |
| TMA-GITHUB-1.4.4 | Ensure only secured webhooks are usedgithub · Nivel 1 | github | Alta | 1 | Automatizada |
| TMA-GITHUB-2.1.7 | Ensure build secrets are limited to the minimal necessary scopegithub · Nivel 2 | github | Alta | 2 | Revisión manual |
| TMA-GITHUB-2.1.9 | Ensure default passwords are not usedgithub · Nivel 1 | github | Alta | 1 | Revisión manual |
| TMA-GITHUB-2.1.10 | Ensure webhooks of the build environment are securedgithub · Nivel 1 | github | Alta | 1 | Revisión manual |
| TMA-GITHUB-2.1.11 | Ensure minimum number of administrators are set for the build environmentgithub · Nivel 1 | github | Alta | 1 | Revisión manual |
| TMA-GITHUB-2.4.1 | Ensure all artifacts on all releases are signedgithub · Nivel 1 | github | Alta | 1 | Revisión manual |
| TMA-GITHUB-3.1.3 | Ensure signed metadata of the build process is required and verifiedgithub · Nivel 1 | github | Alta | 1 | Revisión manual |
| TMA-GITHUB-3.1.6 | Ensure a signed Software Bill of Materials (SBOM) of the code is suppliedgithub · Nivel 1 | github | Alta | 1 | Revisión manual |
| TMA-GITHUB-4.1.1 | Ensure all artifacts are signed by the build pipeline itselfgithub · Nivel 2 | github | Alta | 2 | Revisión manual |
| TMA-GITHUB-4.1.2 | Ensure artifacts are encrypted before distributiongithub · Nivel 2 | github | Alta | 2 | Revisión manual |
| TMA-GITHUB-4.2.3 | Ensure user access to the package registry utilizes Multi- Factor Authentication (MFA)github · Nivel 2 | github | Alta | 2 | Revisión manual |
| TMA-GITHUB-4.2.5 | Ensure anonymous access to artifacts is revokedgithub · Nivel 1 | github | Alta | 1 | Revisión manual |
| TMA-GITHUB-4.2.6 | Ensure minimum number of administrators are set for the package registrygithub · Nivel 1 | github | Alta | 1 | Revisión manual |