Rule explorer
Browse every hardening rule in the catalog. Filter by platform, severity, profile level and whether the check can be automated.
120 rules foundof 8,597Page 1 of 5
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-GITHUB-1.1.3 | Ensure any change to code receives approval of two strongly authenticated usersgithub · Level 1 | github | High | 1 | Automated |
| TMA-GITHUB-1.1.4 | Ensure previous approvals are dismissed when updates are introduced to a code change proposalgithub · Level 1 | github | High | 1 | Automated |
| TMA-GITHUB-1.1.12 | Ensure verification of signed commits for new changes before merginggithub · Level 2 | github | High | 2 | Automated |
| TMA-GITHUB-1.1.14 | Ensure branch protection rules are enforced for administratorsgithub · Level 1 | github | High | 1 | Automated |
| TMA-GITHUB-1.1.16 | Ensure force push code to branches is deniedgithub · Level 1 | github | High | 1 | Automated |
| TMA-GITHUB-1.2.1 | Ensure all public repositories contain a SECURITY.md filegithub · Level 1 | github | High | 1 | Automated |
| TMA-GITHUB-1.3.3 | Ensure minimum number of administrators are set for the organizationgithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-1.3.4 | Ensure Multi-Factor Authentication (MFA) is required for contributors of new codegithub · Level 2 | github | High | 2 | Automated |
| TMA-GITHUB-1.3.5 | Ensure the organization is requiring members to use Multi- Factor Authentication (MFA)github · Level 2 | github | High | 2 | Automated |
| TMA-GITHUB-1.3.7 | Ensure two administrators are set for each repositorygithub · Level 2 | github | High | 2 | Manual review |
| TMA-GITHUB-1.3.11 | Ensure an organization provides SSH certificatesgithub · Level 2 | github | High | 2 | Manual review |
| TMA-GITHUB-1.4.1 | Ensure administrator approval is required for every installed applicationgithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-1.4.4 | Ensure only secured webhooks are usedgithub · Level 1 | github | High | 1 | Automated |
| TMA-GITHUB-2.1.7 | Ensure build secrets are limited to the minimal necessary scopegithub · Level 2 | github | High | 2 | Manual review |
| TMA-GITHUB-2.1.9 | Ensure default passwords are not usedgithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-2.1.10 | Ensure webhooks of the build environment are securedgithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-2.1.11 | Ensure minimum number of administrators are set for the build environmentgithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-2.4.1 | Ensure all artifacts on all releases are signedgithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-3.1.3 | Ensure signed metadata of the build process is required and verifiedgithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-3.1.6 | Ensure a signed Software Bill of Materials (SBOM) of the code is suppliedgithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-4.1.1 | Ensure all artifacts are signed by the build pipeline itselfgithub · Level 2 | github | High | 2 | Manual review |
| TMA-GITHUB-4.1.2 | Ensure artifacts are encrypted before distributiongithub · Level 2 | github | High | 2 | Manual review |
| TMA-GITHUB-4.2.3 | Ensure user access to the package registry utilizes Multi- Factor Authentication (MFA)github · Level 2 | github | High | 2 | Manual review |
| TMA-GITHUB-4.2.5 | Ensure anonymous access to artifacts is revokedgithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-4.2.6 | Ensure minimum number of administrators are set for the package registrygithub · Level 1 | github | High | 1 | Manual review |