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 16.927Seite 4 von 5

IDTitelSchweregrad
TMA-GITHUB-2.3.6Ensure pipelines are automatically scanned for misconfigurationsgithub · Stufe 1Mittel
TMA-GITHUB-2.3.7Ensure pipelines are automatically scanned for vulnerabilitiesgithub · Stufe 1Mittel
TMA-GITHUB-2.3.8Ensure scanners are in place to identify and prevent sensitive data in pipeline filesgithub · Stufe 2Mittel
TMA-GITHUB-2.4.2Ensure all external dependencies used in the build process are lockedgithub · Stufe 1Mittel
TMA-GITHUB-2.4.3Ensure dependencies are validated before being usedgithub · Stufe 1Mittel
TMA-GITHUB-2.4.4Ensure the build pipeline creates reproducible artifactsgithub · Stufe 1Mittel
TMA-GITHUB-2.4.5Ensure pipeline steps produce a Software Bill of Materials (SBOM)github · Stufe 1Mittel
TMA-GITHUB-2.4.6Ensure pipeline steps sign the Software Bill of Materials (SBOM) producedgithub · Stufe 1Mittel
TMA-GITHUB-3.1.1Ensure third-party artifacts and open-source libraries are verifiedgithub · Stufe 1Mittel
TMA-GITHUB-3.1.2Ensure Software Bill of Materials (SBOM) is required from all third-party suppliersgithub · Stufe 1Mittel
TMA-GITHUB-3.1.4Ensure dependencies are monitored between open-source componentsgithub · Stufe 1Mittel
TMA-GITHUB-3.1.5Ensure trusted package managers and repositories are defined and prioritizedgithub · Stufe 1Mittel
TMA-GITHUB-3.1.7Ensure dependencies are pinned to a specific, verified versiongithub · Stufe 1Mittel
TMA-GITHUB-3.1.8Ensure all packages used are more than 60 days oldgithub · Stufe 2Mittel
TMA-GITHUB-3.2.1Ensure an organization-wide dependency usage policy is enforcedgithub · Stufe 1Mittel
TMA-GITHUB-3.2.2Ensure packages are automatically scanned for known vulnerabilitiesgithub · Stufe 1Mittel
TMA-GITHUB-3.2.3Ensure packages are automatically scanned for license implicationsgithub · Stufe 1Mittel
TMA-GITHUB-3.2.4Ensure packages are automatically scanned for ownership changegithub · Stufe 1Mittel
TMA-GITHUB-4.1.3Ensure only authorized platforms have decryption capabilities of artifactsgithub · Stufe 2Mittel
TMA-GITHUB-4.2.1Ensure the authority to certify artifacts is limitedgithub · Stufe 1Mittel
TMA-GITHUB-4.2.2Ensure number of permitted users who may upload new artifacts is minimizedgithub · Stufe 1Mittel
TMA-GITHUB-4.2.4Ensure user management of the package registry is not localgithub · Stufe 1Mittel
TMA-GITHUB-4.3.2Ensure all versions of an existing artifact have their signatures validatedgithub · Stufe 1Mittel
TMA-GITHUB-4.3.3Ensure changes in package registry configuration are auditedgithub · Stufe 1Mittel
TMA-GITHUB-4.4.1Ensure artifacts contain information about their origingithub · Stufe 1Mittel