Pregledač pravila
Pregledajte svako pravilo za ojačavanje bezbednosti u katalogu. Filtrirajte po platformi, ozbiljnosti, nivou profila i tome da li se provera može automatizovati.
Pronađena 122 pravilaod 16.927Stranica 1 od 5
| ID | Naslov | Platforma | Ozbiljnost | Nivo | Provera |
|---|---|---|---|---|---|
| TMA-GITLAB-1.1.3 | Ensure any change to code receives approval of two strongly authenticated usersgitlab · Nivo 1 | gitlab | Visoka | 1 | Automatska |
| TMA-GITLAB-1.1.4 | Ensure previous approvals are dismissed when updates are introduced to a code change proposalgitlab · Nivo 1 | gitlab | Visoka | 1 | Automatska |
| TMA-GITLAB-1.1.12 | Ensure verification of signed commits for new changes before merginggitlab · Nivo 2 | gitlab | Visoka | 2 | Automatska |
| TMA-GITLAB-1.1.14 | Ensure branch protection rules are enforced for administratorsgitlab · Nivo 1 | gitlab | Visoka | 1 | Automatska |
| TMA-GITLAB-1.1.16 | Ensure force push code to branches is deniedgitlab · Nivo 1 | gitlab | Visoka | 1 | Automatska |
| TMA-GITLAB-1.2.1 | Ensure all public repositories contain a SECURITY.md filegitlab · Nivo 1 | gitlab | Visoka | 1 | Automatska |
| TMA-GITLAB-1.3.3 | Ensure minimum number of administrators are set for the organizationgitlab · Nivo 1 | gitlab | Visoka | 1 | Ručni pregled |
| TMA-GITLAB-1.3.4 | Ensure Multi-Factor Authentication (MFA) is required for contributors of new codegitlab · Nivo 2 | gitlab | Visoka | 2 | Automatska |
| TMA-GITLAB-1.3.5 | Ensure the organization is requiring members to use Multi- Factor Authentication (MFA)gitlab · Nivo 2 | gitlab | Visoka | 2 | Automatska |
| TMA-GITLAB-1.3.7 | Ensure two administrators are set for each repositorygitlab · Nivo 2 | gitlab | Visoka | 2 | Ručni pregled |
| TMA-GITLAB-1.3.11 | Ensure an organization provides SSH certificatesgitlab · Nivo 2 | gitlab | Visoka | 2 | Ručni pregled |
| TMA-GITLAB-1.4.1 | Ensure administrator approval is required for every installed applicationgitlab · Nivo 1 | gitlab | Visoka | 1 | Ručni pregled |
| TMA-GITLAB-1.4.4 | Ensure only secured webhooks are usedgitlab · Nivo 1 | gitlab | Visoka | 1 | Automatska |
| TMA-GITLAB-2.1.7 | Ensure build secrets are limited to the minimal necessary scopegitlab · Nivo 2 | gitlab | Visoka | 2 | Ručni pregled |
| TMA-GITLAB-2.1.9 | Ensure default passwords are not usedgitlab · Nivo 1 | gitlab | Visoka | 1 | Ručni pregled |
| TMA-GITLAB-2.1.10 | Ensure webhooks of the build environment are securedgitlab · Nivo 1 | gitlab | Visoka | 1 | Ručni pregled |
| TMA-GITLAB-2.1.11 | Ensure minimum number of administrators are set for the build environmentgitlab · Nivo 1 | gitlab | Visoka | 1 | Ručni pregled |
| TMA-GITLAB-2.4.1 | Ensure all artifacts on all releases are signedgitlab · Nivo 1 | gitlab | Visoka | 1 | Ručni pregled |
| TMA-GITLAB-3.1.3 | Ensure signed metadata of the build process is required and verifiedgitlab · Nivo 1 | gitlab | Visoka | 1 | Ručni pregled |
| TMA-GITLAB-3.1.6 | Ensure a signed Software Bill of Materials (SBOM) of the code is suppliedgitlab · Nivo 1 | gitlab | Visoka | 1 | Ručni pregled |
| TMA-GITLAB-4.1.1 | Ensure all artifacts are signed by the build pipeline itselfgitlab · Nivo 2 | gitlab | Visoka | 2 | Ručni pregled |
| TMA-GITLAB-4.1.2 | Ensure artifacts are encrypted before distributiongitlab · Nivo 2 | gitlab | Visoka | 2 | Ručni pregled |
| TMA-GITLAB-4.2.3 | Ensure user access to the package registry utilizes Multi- Factor Authentication (MFA)gitlab · Nivo 2 | gitlab | Visoka | 2 | Ručni pregled |
| TMA-GITLAB-4.2.5 | Ensure anonymous access to artifacts is revokedgitlab · Nivo 1 | gitlab | Visoka | 1 | Ručni pregled |
| TMA-GITLAB-4.2.6 | Ensure minimum number of administrators are set for the package registrygitlab · Nivo 1 | gitlab | Visoka | 1 | Ručni pregled |