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 16,927Page 4 of 5
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-GITHUB-2.3.6 | Ensure pipelines are automatically scanned for misconfigurationsgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.3.7 | Ensure pipelines are automatically scanned for vulnerabilitiesgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.3.8 | Ensure scanners are in place to identify and prevent sensitive data in pipeline filesgithub · Level 2 | github | Medium | 2 | Automated |
| TMA-GITHUB-2.4.2 | Ensure all external dependencies used in the build process are lockedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.4.3 | Ensure dependencies are validated before being usedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.4.4 | Ensure the build pipeline creates reproducible artifactsgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.4.5 | Ensure pipeline steps produce a Software Bill of Materials (SBOM)github · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-2.4.6 | Ensure pipeline steps sign the Software Bill of Materials (SBOM) producedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-3.1.1 | Ensure third-party artifacts and open-source libraries are verifiedgithub · Level 1 | github | Medium | 1 | Automated |
| TMA-GITHUB-3.1.2 | Ensure Software Bill of Materials (SBOM) is required from all third-party suppliersgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-3.1.4 | Ensure dependencies are monitored between open-source componentsgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-3.1.5 | Ensure trusted package managers and repositories are defined and prioritizedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-3.1.7 | Ensure dependencies are pinned to a specific, verified versiongithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-3.1.8 | Ensure all packages used are more than 60 days oldgithub · Level 2 | github | Medium | 2 | Manual review |
| TMA-GITHUB-3.2.1 | Ensure an organization-wide dependency usage policy is enforcedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-3.2.2 | Ensure packages are automatically scanned for known vulnerabilitiesgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-3.2.3 | Ensure packages are automatically scanned for license implicationsgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-3.2.4 | Ensure packages are automatically scanned for ownership changegithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-4.1.3 | Ensure only authorized platforms have decryption capabilities of artifactsgithub · Level 2 | github | Medium | 2 | Manual review |
| TMA-GITHUB-4.2.1 | Ensure the authority to certify artifacts is limitedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-4.2.2 | Ensure number of permitted users who may upload new artifacts is minimizedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-4.2.4 | Ensure user management of the package registry is not localgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-4.3.2 | Ensure all versions of an existing artifact have their signatures validatedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-4.3.3 | Ensure changes in package registry configuration are auditedgithub · Level 1 | github | Medium | 1 | Manual review |
| TMA-GITHUB-4.4.1 | Ensure artifacts contain information about their origingithub · Level 1 | github | Medium | 1 | Manual review |