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 3 of 5
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-GITHUB-1.4.3 | Ensure the access granted to each installed application is limited to the least privilege neededgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-1.5.1 | Ensure scanners are in place to identify and prevent sensitive data in codegithub · Level 2 | github | Medium | 2 | Automated |
| TMA-GITHUB-1.5.2 | Ensure scanners are in place to secure Continuous Integration (CI) pipeline instructionsgithub · Level 2 | github | Medium | 2 | Manual review |
| TMA-GITHUB-1.5.3 | Ensure scanners are in place to secure Infrastructure as Code (IaC) instructionsgithub · Level 2 | github | Medium | 2 | Manual review |
| TMA-GITHUB-1.5.4 | Ensure scanners are in place for code vulnerabilitiesgithub · Level 2 | github | Medium | 2 | Automated |
| TMA-GITHUB-1.5.5 | Ensure scanners are in place for open-source vulnerabilities in used packagesgithub · Level 2 | github | Medium | 2 | Automated |
| TMA-GITHUB-1.5.6 | Ensure scanners are in place for open-source license issues in used packagesgithub · Level 2 | github | Medium | 2 | Manual review |
| TMA-GITHUB-2.1.2 | Ensure all aspects of the pipeline infrastructure and configuration are immutablegithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.1.3 | Ensure the build environment is loggedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.1.4 | Ensure the creation of the build environment is automatedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.1.5 | Ensure access to build environments is limitedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.1.6 | Ensure users must authenticate to access the build environmentgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.1.8 | Ensure the build infrastructure is automatically scanned for vulnerabilitiesgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.2.1 | Ensure build workers are single-usedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.2.2 | Ensure build worker environments and commands are passed and not pulledgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.2.3 | Ensure the duties of each build worker are segregatedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.2.4 | Ensure build workers have minimal network connectivitygithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.2.5 | Ensure run-time security is enforced for build workersgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.2.6 | Ensure build workers are automatically scanned for vulnerabilitiesgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.2.7 | Ensure build workers' deployment configuration is stored in a version control platformgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.2.8 | Ensure resource consumption of build workers is monitoredgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.3.1 | Ensure all build steps are defined as codegithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.3.2 | Ensure steps have clearly defined build stage input and outputgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.3.3 | Ensure output is written to a separate, secured storage repositorygithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.3.5 | Ensure access to build process triggering is minimizedgithub · Level 1 | github | Medium | 1 | Manual review |