Каталог правил
Просматривайте все правила укрепления защиты в каталоге. Фильтруйте по платформе, критичности, уровню профиля и возможности автоматической проверки.
Найдено 122 правилаиз 16 927Страница 3 из 5
| ID | Название | Платформа | Критичность | Уровень | Проверка |
|---|---|---|---|---|---|
| TMA-GITLAB-1.4.3 | Ensure the access granted to each installed application is limited to the least privilege neededgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-1.5.1 | Ensure scanners are in place to identify and prevent sensitive data in codegitlab · Уровень 2 | gitlab | Средний | 2 | Автоматическая |
| TMA-GITLAB-1.5.2 | Ensure scanners are in place to secure Continuous Integration (CI) pipeline instructionsgitlab · Уровень 2 | gitlab | Средний | 2 | Ручная проверка |
| TMA-GITLAB-1.5.3 | Ensure scanners are in place to secure Infrastructure as Code (IaC) instructionsgitlab · Уровень 2 | gitlab | Средний | 2 | Ручная проверка |
| TMA-GITLAB-1.5.4 | Ensure scanners are in place for code vulnerabilitiesgitlab · Уровень 2 | gitlab | Средний | 2 | Автоматическая |
| TMA-GITLAB-1.5.5 | Ensure scanners are in place for open-source vulnerabilities in used packagesgitlab · Уровень 2 | gitlab | Средний | 2 | Автоматическая |
| TMA-GITLAB-1.5.6 | Ensure scanners are in place for open-source license issues in used packagesgitlab · Уровень 2 | gitlab | Средний | 2 | Ручная проверка |
| TMA-GITLAB-2.1.2 | Ensure all aspects of the pipeline infrastructure and configuration are immutablegitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.1.3 | Ensure the build environment is loggedgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.1.4 | Ensure the creation of the build environment is automatedgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.1.5 | Ensure access to build environments is limitedgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.1.6 | Ensure users must authenticate to access the build environmentgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.1.8 | Ensure the build infrastructure is automatically scanned for vulnerabilitiesgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.2.1 | Ensure build workers are single-usedgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.2.2 | Ensure build worker environments and commands are passed and not pulledgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.2.3 | Ensure the duties of each build worker are segregatedgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.2.4 | Ensure build workers have minimal network connectivitygitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.2.5 | Ensure run-time security is enforced for build workersgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.2.6 | Ensure build workers are automatically scanned for vulnerabilitiesgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.2.7 | Ensure build workers' deployment configuration is stored in a version control platformgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.2.8 | Ensure resource consumption of build workers is monitoredgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.3.1 | Ensure all build steps are defined as codegitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.3.2 | Ensure steps have clearly defined build stage input and outputgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.3.3 | Ensure output is written to a separate, secured storage repositorygitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |
| TMA-GITLAB-2.3.5 | Ensure access to build process triggering is minimizedgitlab · Уровень 1 | gitlab | Средний | 1 | Ручная проверка |