규칙 탐색기
카탈로그의 모든 하드닝 규칙을 둘러보세요. 플랫폼, 심각도, 프로필 레벨 및 자동 점검 가능 여부로 필터링할 수 있습니다.
규칙 120개 찾음/ 전체 11,219개5페이지 중 1페이지
| ID | 제목 | 플랫폼 | 심각도 | 레벨 | 점검 |
|---|---|---|---|---|---|
| TMA-GITHUB-1.1.3 | Ensure any change to code receives approval of two strongly authenticated usersgithub · 레벨 1 | github | 높음 | 1 | 자동 |
| TMA-GITHUB-1.1.4 | Ensure previous approvals are dismissed when updates are introduced to a code change proposalgithub · 레벨 1 | github | 높음 | 1 | 자동 |
| TMA-GITHUB-1.1.12 | Ensure verification of signed commits for new changes before merginggithub · 레벨 2 | github | 높음 | 2 | 자동 |
| TMA-GITHUB-1.1.14 | Ensure branch protection rules are enforced for administratorsgithub · 레벨 1 | github | 높음 | 1 | 자동 |
| TMA-GITHUB-1.1.16 | Ensure force push code to branches is deniedgithub · 레벨 1 | github | 높음 | 1 | 자동 |
| TMA-GITHUB-1.2.1 | Ensure all public repositories contain a SECURITY.md filegithub · 레벨 1 | github | 높음 | 1 | 자동 |
| TMA-GITHUB-1.3.3 | Ensure minimum number of administrators are set for the organizationgithub · 레벨 1 | github | 높음 | 1 | 수동 검토 |
| TMA-GITHUB-1.3.4 | Ensure Multi-Factor Authentication (MFA) is required for contributors of new codegithub · 레벨 2 | github | 높음 | 2 | 자동 |
| TMA-GITHUB-1.3.5 | Ensure the organization is requiring members to use Multi- Factor Authentication (MFA)github · 레벨 2 | github | 높음 | 2 | 자동 |
| TMA-GITHUB-1.3.7 | Ensure two administrators are set for each repositorygithub · 레벨 2 | github | 높음 | 2 | 수동 검토 |
| TMA-GITHUB-1.3.11 | Ensure an organization provides SSH certificatesgithub · 레벨 2 | github | 높음 | 2 | 수동 검토 |
| TMA-GITHUB-1.4.1 | Ensure administrator approval is required for every installed applicationgithub · 레벨 1 | github | 높음 | 1 | 수동 검토 |
| TMA-GITHUB-1.4.4 | Ensure only secured webhooks are usedgithub · 레벨 1 | github | 높음 | 1 | 자동 |
| TMA-GITHUB-2.1.7 | Ensure build secrets are limited to the minimal necessary scopegithub · 레벨 2 | github | 높음 | 2 | 수동 검토 |
| TMA-GITHUB-2.1.9 | Ensure default passwords are not usedgithub · 레벨 1 | github | 높음 | 1 | 수동 검토 |
| TMA-GITHUB-2.1.10 | Ensure webhooks of the build environment are securedgithub · 레벨 1 | github | 높음 | 1 | 수동 검토 |
| TMA-GITHUB-2.1.11 | Ensure minimum number of administrators are set for the build environmentgithub · 레벨 1 | github | 높음 | 1 | 수동 검토 |
| TMA-GITHUB-2.4.1 | Ensure all artifacts on all releases are signedgithub · 레벨 1 | github | 높음 | 1 | 수동 검토 |
| TMA-GITHUB-3.1.3 | Ensure signed metadata of the build process is required and verifiedgithub · 레벨 1 | github | 높음 | 1 | 수동 검토 |
| TMA-GITHUB-3.1.6 | Ensure a signed Software Bill of Materials (SBOM) of the code is suppliedgithub · 레벨 1 | github | 높음 | 1 | 수동 검토 |
| TMA-GITHUB-4.1.1 | Ensure all artifacts are signed by the build pipeline itselfgithub · 레벨 2 | github | 높음 | 2 | 수동 검토 |
| TMA-GITHUB-4.1.2 | Ensure artifacts are encrypted before distributiongithub · 레벨 2 | github | 높음 | 2 | 수동 검토 |
| TMA-GITHUB-4.2.3 | Ensure user access to the package registry utilizes Multi- Factor Authentication (MFA)github · 레벨 2 | github | 높음 | 2 | 수동 검토 |
| TMA-GITHUB-4.2.5 | Ensure anonymous access to artifacts is revokedgithub · 레벨 1 | github | 높음 | 1 | 수동 검토 |
| TMA-GITHUB-4.2.6 | Ensure minimum number of administrators are set for the package registrygithub · 레벨 1 | github | 높음 | 1 | 수동 검토 |