TMAegis

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đeno 120 pravilaod 11.219Stranica 1 od 5

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