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 11,219Page 2 of 5
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-GITHUB-4.3.1 | Ensure all signed artifacts are validated upon uploading the package registrygithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-4.3.4 | Ensure webhooks of the repository are securedgithub · Level 1 | github | High | 1 | Automated |
| TMA-GITHUB-5.2.4 | Ensure default passwords are not usedgithub · Level 1 | github | High | 1 | Manual review |
| TMA-GITHUB-1.1.2 | Ensure any change to code can be traced back to its associated taskgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-1.1.5 | Ensure there are restrictions on who can dismiss code change reviewsgithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-1.1.6 | Ensure code owners are set for extra sensitive code or configurationgithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-1.1.7 | Ensure code owner's review is required when a change affects owned codegithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-1.1.9 | Ensure all checks have passed before merging new codegithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-1.1.10 | Ensure open Git branches are up to date before they can be merged into code basegithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-1.1.11 | Ensure all open comments are resolved before allowing code change merginggithub · Level 2 | github | Medium | 2 | Automated |
| TMA-GITHUB-1.1.13 | Ensure linear history is requiredgithub · Level 2 | github | Medium | 2 | Automated |
| TMA-GITHUB-1.1.15 | Ensure pushing or merging of new code is restricted to specific individuals or teamsgithub · Level 2 | github | Medium | 2 | Automated |
| TMA-GITHUB-1.1.17 | Ensure branch deletions are deniedgithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-1.1.18 | Ensure any merging of code is automatically scanned for risksgithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-1.1.19 | Ensure any changes to branch protection rules are auditedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-1.1.20 | Ensure branch protection is enforced on the default branchgithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-1.2.2 | Ensure repository creation is limited to specific membersgithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-1.2.3 | Ensure repository deletion is limited to specific usersgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-1.2.4 | Ensure issue deletion is limited to specific usersgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-1.3.2 | Ensure team creation is limited to specific membersgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-1.3.6 | Ensure new members are required to be invited using company-approved emailgithub · Level 2 | github | Medium | 2 | Manual review |
| TMA-GITHUB-1.3.8 | Ensure strict base permissions are set for repositoriesgithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-1.3.9 | Ensure an organization's identity is confirmed with a "Verified" badgegithub · Level 2 | github | Medium | 2 | Automated |
| TMA-GITHUB-1.3.10 | Ensure Source Code Management (SCM) email notifications are restricted to verified domainsgithub · Level 2 | github | Medium | 2 | Automated |
| TMA-GITHUB-1.3.12 | Ensure Git access is limited based on IP addressesgithub · Level 2 | github | Medium | 2 | Automated |