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 5 of 5
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-GITHUB-5.1.1 | Ensure deployment configuration files are separated from source codegithub · Level 2 | github | Medium | 2 | Manual review |
| TMA-GITHUB-5.1.2 | Ensure changes in deployment configuration are auditedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-5.1.3 | Ensure scanners are in place to identify and prevent sensitive data in deployment configurationgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-5.1.4 | Limit access to deployment configurationsgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-5.1.5 | Scan Infrastructure as Code (IaC)github · Level 2 | github | Medium | 2 | Manual review |
| TMA-GITHUB-5.1.6 | Ensure deployment configuration manifests are verifiedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-5.1.7 | Ensure deployment configuration manifests are pinned to a specific, verified versiongithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-5.2.1 | Ensure deployments are automatedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-5.2.2 | Ensure the deployment environment is reproduciblegithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-5.2.3 | Ensure access to production environment is limitedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-1.1.1 | Ensure any changes to code are tracked in a version control platformgithub · Level 1 | github | Low | 1 | Manual review |
| TMA-GITHUB-1.1.8 | Ensure inactive branches are periodically reviewed and removedgithub · Level 1 | github | Low | 1 | Manual review |
| TMA-GITHUB-1.2.5 | Ensure all copies (forks) of code are tracked and accounted forgithub · Level 1 | github | Low | 1 | Manual review |
| TMA-GITHUB-1.2.6 | Ensure all code projects are tracked for changes in visibility statusgithub · Level 1 | github | Low | 1 | Manual review |
| TMA-GITHUB-1.2.7 | Ensure inactive repositories are reviewed and archived periodicallygithub · Level 1 | github | Low | 1 | Manual review |
| TMA-GITHUB-1.3.1 | Ensure inactive users are reviewed and removed periodicallygithub · Level 2 | github | Low | 2 | Manual review |
| TMA-GITHUB-1.3.13 | Ensure anomalous code behavior is trackedgithub · Level 1 | github | Low | 1 | Manual review |
| TMA-GITHUB-1.4.2 | Ensure stale applications are reviewed and inactive ones are removedgithub · Level 1 | github | Low | 1 | Manual review |
| TMA-GITHUB-2.1.1 | Ensure each pipeline has a single responsibilitygithub · Level 2 | github | Low | 2 | Manual review |
| TMA-GITHUB-2.3.4 | Ensure changes to pipeline files are tracked and reviewedgithub · Level 1 | github | Low | 1 | Manual review |