Penjelajah aturan
Jelajahi setiap aturan hardening di katalog. Filter menurut platform, tingkat keparahan, level profil, dan apakah pemeriksaan dapat diotomatisasi.
122 aturan ditemukandari 11.219Halaman 1 dari 5
| ID | Judul | Platform | Tingkat keparahan | Level | Pemeriksaan |
|---|---|---|---|---|---|
| TMA-GITLAB-1.1.3 | Ensure any change to code receives approval of two strongly authenticated usersgitlab · Level 1 | gitlab | Tinggi | 1 | Otomatis |
| TMA-GITLAB-1.1.4 | Ensure previous approvals are dismissed when updates are introduced to a code change proposalgitlab · Level 1 | gitlab | Tinggi | 1 | Otomatis |
| TMA-GITLAB-1.1.12 | Ensure verification of signed commits for new changes before merginggitlab · Level 2 | gitlab | Tinggi | 2 | Otomatis |
| TMA-GITLAB-1.1.14 | Ensure branch protection rules are enforced for administratorsgitlab · Level 1 | gitlab | Tinggi | 1 | Otomatis |
| TMA-GITLAB-1.1.16 | Ensure force push code to branches is deniedgitlab · Level 1 | gitlab | Tinggi | 1 | Otomatis |
| TMA-GITLAB-1.2.1 | Ensure all public repositories contain a SECURITY.md filegitlab · Level 1 | gitlab | Tinggi | 1 | Otomatis |
| TMA-GITLAB-1.3.3 | Ensure minimum number of administrators are set for the organizationgitlab · Level 1 | gitlab | Tinggi | 1 | Tinjauan manual |
| TMA-GITLAB-1.3.4 | Ensure Multi-Factor Authentication (MFA) is required for contributors of new codegitlab · Level 2 | gitlab | Tinggi | 2 | Otomatis |
| TMA-GITLAB-1.3.5 | Ensure the organization is requiring members to use Multi- Factor Authentication (MFA)gitlab · Level 2 | gitlab | Tinggi | 2 | Otomatis |
| TMA-GITLAB-1.3.7 | Ensure two administrators are set for each repositorygitlab · Level 2 | gitlab | Tinggi | 2 | Tinjauan manual |
| TMA-GITLAB-1.3.11 | Ensure an organization provides SSH certificatesgitlab · Level 2 | gitlab | Tinggi | 2 | Tinjauan manual |
| TMA-GITLAB-1.4.1 | Ensure administrator approval is required for every installed applicationgitlab · Level 1 | gitlab | Tinggi | 1 | Tinjauan manual |
| TMA-GITLAB-1.4.4 | Ensure only secured webhooks are usedgitlab · Level 1 | gitlab | Tinggi | 1 | Otomatis |
| TMA-GITLAB-2.1.7 | Ensure build secrets are limited to the minimal necessary scopegitlab · Level 2 | gitlab | Tinggi | 2 | Tinjauan manual |
| TMA-GITLAB-2.1.9 | Ensure default passwords are not usedgitlab · Level 1 | gitlab | Tinggi | 1 | Tinjauan manual |
| TMA-GITLAB-2.1.10 | Ensure webhooks of the build environment are securedgitlab · Level 1 | gitlab | Tinggi | 1 | Tinjauan manual |
| TMA-GITLAB-2.1.11 | Ensure minimum number of administrators are set for the build environmentgitlab · Level 1 | gitlab | Tinggi | 1 | Tinjauan manual |
| TMA-GITLAB-2.4.1 | Ensure all artifacts on all releases are signedgitlab · Level 1 | gitlab | Tinggi | 1 | Tinjauan manual |
| TMA-GITLAB-3.1.3 | Ensure signed metadata of the build process is required and verifiedgitlab · Level 1 | gitlab | Tinggi | 1 | Tinjauan manual |
| TMA-GITLAB-3.1.6 | Ensure a signed Software Bill of Materials (SBOM) of the code is suppliedgitlab · Level 1 | gitlab | Tinggi | 1 | Tinjauan manual |
| TMA-GITLAB-4.1.1 | Ensure all artifacts are signed by the build pipeline itselfgitlab · Level 2 | gitlab | Tinggi | 2 | Tinjauan manual |
| TMA-GITLAB-4.1.2 | Ensure artifacts are encrypted before distributiongitlab · Level 2 | gitlab | Tinggi | 2 | Tinjauan manual |
| TMA-GITLAB-4.2.3 | Ensure user access to the package registry utilizes Multi- Factor Authentication (MFA)gitlab · Level 2 | gitlab | Tinggi | 2 | Tinjauan manual |
| TMA-GITLAB-4.2.5 | Ensure anonymous access to artifacts is revokedgitlab · Level 1 | gitlab | Tinggi | 1 | Tinjauan manual |
| TMA-GITLAB-4.2.6 | Ensure minimum number of administrators are set for the package registrygitlab · Level 1 | gitlab | Tinggi | 1 | Tinjauan manual |