Rule explorer
Browse every hardening rule in the catalog. Filter by platform, severity, profile level and whether the check can be automated.
122 rules foundof 16,927Page 5 of 5
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-GITLAB-5.1.1 | Ensure deployment configuration files are separated from source codegitlab · Level 2 | gitlab | Medium | 2 | Manual review |
| TMA-GITLAB-5.1.2 | Ensure changes in deployment configuration are auditedgitlab · Level 1 | gitlab | Medium | 1 | Manual review |
| TMA-GITLAB-5.1.3 | Ensure scanners are in place to identify and prevent sensitive data in deployment configurationgitlab · Level 1 | gitlab | Medium | 1 | Manual review |
| TMA-GITLAB-5.1.4 | Limit access to deployment configurationsgitlab · Level 1 | gitlab | Medium | 1 | Manual review |
| TMA-GITLAB-5.1.5 | Scan Infrastructure as Code (IaC)gitlab · Level 2 | gitlab | Medium | 2 | Manual review |
| TMA-GITLAB-5.1.6 | Ensure deployment configuration manifests are verifiedgitlab · Level 1 | gitlab | Medium | 1 | Manual review |
| TMA-GITLAB-5.1.7 | Ensure deployment configuration manifests are pinned to a specific, verified versiongitlab · Level 1 | gitlab | Medium | 1 | Manual review |
| TMA-GITLAB-5.2.1 | Ensure deployments are automatedgitlab · Level 1 | gitlab | Medium | 1 | Manual review |
| TMA-GITLAB-5.2.2 | Ensure the deployment environment is reproduciblegitlab · Level 1 | gitlab | Medium | 1 | Manual review |
| TMA-GITLAB-5.2.3 | Ensure access to production environment is limitedgitlab · Level 1 | gitlab | Medium | 1 | Manual review |
| TMA-GITLAB-1.1.1 | Ensure any changes to code are tracked in a version control platformgitlab · Level 1 | gitlab | Low | 1 | Manual review |
| TMA-GITLAB-1.1.8 | Ensure inactive branches are periodically reviewed and removedgitlab · Level 1 | gitlab | Low | 1 | Manual review |
| TMA-GITLAB-1.2.5 | Ensure all copies (forks) of code are tracked and accounted forgitlab · Level 1 | gitlab | Low | 1 | Manual review |
| TMA-GITLAB-1.2.6 | Ensure all code projects are tracked for changes in visibility statusgitlab · Level 1 | gitlab | Low | 1 | Manual review |
| TMA-GITLAB-1.2.7 | Ensure inactive repositories are reviewed and archived periodicallygitlab · Level 1 | gitlab | Low | 1 | Manual review |
| TMA-GITLAB-1.3.1 | Ensure inactive users are reviewed and removed periodicallygitlab · Level 2 | gitlab | Low | 2 | Manual review |
| TMA-GITLAB-1.3.13 | Ensure anomalous code behavior is trackedgitlab · Level 1 | gitlab | Low | 1 | Manual review |
| TMA-GITLAB-1.4.2 | Ensure stale applications are reviewed and inactive ones are removedgitlab · Level 1 | gitlab | Low | 1 | Manual review |
| TMA-GITLAB-1.5.7 | Ensure scanners are in place for web application runtime security weaknessesgitlab · Level 2 | gitlab | Low | 2 | Manual review |
| TMA-GITLAB-1.5.8 | Ensure scanners are in place for API runtime security weaknessesgitlab · Level 2 | gitlab | Low | 2 | Manual review |
| TMA-GITLAB-2.1.1 | Ensure each pipeline has a single responsibilitygitlab · Level 2 | gitlab | Low | 2 | Manual review |
| TMA-GITLAB-2.3.4 | Ensure changes to pipeline files are tracked and reviewedgitlab · Level 1 | gitlab | Low | 1 | Manual review |