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