TMAegis

Regel-Explorer

Durchsuchen Sie jede Härtungsregel im Katalog. Filtern Sie nach Plattform, Schweregrad, Profilstufe und danach, ob die Prüfung automatisierbar ist.

122 Regeln gefundenvon 11.219Seite 1 von 5

IDTitelSchweregrad
TMA-GITLAB-1.1.3Ensure any change to code receives approval of two strongly authenticated usersgitlab · Stufe 1Hoch
TMA-GITLAB-1.1.4Ensure previous approvals are dismissed when updates are introduced to a code change proposalgitlab · Stufe 1Hoch
TMA-GITLAB-1.1.12Ensure verification of signed commits for new changes before merginggitlab · Stufe 2Hoch
TMA-GITLAB-1.1.14Ensure branch protection rules are enforced for administratorsgitlab · Stufe 1Hoch
TMA-GITLAB-1.1.16Ensure force push code to branches is deniedgitlab · Stufe 1Hoch
TMA-GITLAB-1.2.1Ensure all public repositories contain a SECURITY.md filegitlab · Stufe 1Hoch
TMA-GITLAB-1.3.3Ensure minimum number of administrators are set for the organizationgitlab · Stufe 1Hoch
TMA-GITLAB-1.3.4Ensure Multi-Factor Authentication (MFA) is required for contributors of new codegitlab · Stufe 2Hoch
TMA-GITLAB-1.3.5Ensure the organization is requiring members to use Multi- Factor Authentication (MFA)gitlab · Stufe 2Hoch
TMA-GITLAB-1.3.7Ensure two administrators are set for each repositorygitlab · Stufe 2Hoch
TMA-GITLAB-1.3.11Ensure an organization provides SSH certificatesgitlab · Stufe 2Hoch
TMA-GITLAB-1.4.1Ensure administrator approval is required for every installed applicationgitlab · Stufe 1Hoch
TMA-GITLAB-1.4.4Ensure only secured webhooks are usedgitlab · Stufe 1Hoch
TMA-GITLAB-2.1.7Ensure build secrets are limited to the minimal necessary scopegitlab · Stufe 2Hoch
TMA-GITLAB-2.1.9Ensure default passwords are not usedgitlab · Stufe 1Hoch
TMA-GITLAB-2.1.10Ensure webhooks of the build environment are securedgitlab · Stufe 1Hoch
TMA-GITLAB-2.1.11Ensure minimum number of administrators are set for the build environmentgitlab · Stufe 1Hoch
TMA-GITLAB-2.4.1Ensure all artifacts on all releases are signedgitlab · Stufe 1Hoch
TMA-GITLAB-3.1.3Ensure signed metadata of the build process is required and verifiedgitlab · Stufe 1Hoch
TMA-GITLAB-3.1.6Ensure a signed Software Bill of Materials (SBOM) of the code is suppliedgitlab · Stufe 1Hoch
TMA-GITLAB-4.1.1Ensure all artifacts are signed by the build pipeline itselfgitlab · Stufe 2Hoch
TMA-GITLAB-4.1.2Ensure artifacts are encrypted before distributiongitlab · Stufe 2Hoch
TMA-GITLAB-4.2.3Ensure user access to the package registry utilizes Multi- Factor Authentication (MFA)gitlab · Stufe 2Hoch
TMA-GITLAB-4.2.5Ensure anonymous access to artifacts is revokedgitlab · Stufe 1Hoch
TMA-GITLAB-4.2.6Ensure minimum number of administrators are set for the package registrygitlab · Stufe 1Hoch