TMAegis

Regel-Explorer

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

120 Regeln gefundenvon 11.219Seite 1 von 5

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