Pregledač pravila
Pregledajte svako pravilo za ojačavanje bezbednosti u katalogu. Filtrirajte po platformi, ozbiljnosti, nivou profila i tome da li se provera može automatizovati.
Pronađeno 120 pravilaod 16.927Stranica 3 od 5
| ID | Naslov | Platforma | Ozbiljnost | Nivo | Provera |
|---|---|---|---|---|---|
| TMA-GITHUB-1.4.3 | Ensure the access granted to each installed application is limited to the least privilege neededgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-1.5.1 | Ensure scanners are in place to identify and prevent sensitive data in codegithub · Nivo 2 | github | Srednja | 2 | Automatska |
| TMA-GITHUB-1.5.2 | Ensure scanners are in place to secure Continuous Integration (CI) pipeline instructionsgithub · Nivo 2 | github | Srednja | 2 | Ručni pregled |
| TMA-GITHUB-1.5.3 | Ensure scanners are in place to secure Infrastructure as Code (IaC) instructionsgithub · Nivo 2 | github | Srednja | 2 | Ručni pregled |
| TMA-GITHUB-1.5.4 | Ensure scanners are in place for code vulnerabilitiesgithub · Nivo 2 | github | Srednja | 2 | Automatska |
| TMA-GITHUB-1.5.5 | Ensure scanners are in place for open-source vulnerabilities in used packagesgithub · Nivo 2 | github | Srednja | 2 | Automatska |
| TMA-GITHUB-1.5.6 | Ensure scanners are in place for open-source license issues in used packagesgithub · Nivo 2 | github | Srednja | 2 | Ručni pregled |
| TMA-GITHUB-2.1.2 | Ensure all aspects of the pipeline infrastructure and configuration are immutablegithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.1.3 | Ensure the build environment is loggedgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.1.4 | Ensure the creation of the build environment is automatedgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.1.5 | Ensure access to build environments is limitedgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.1.6 | Ensure users must authenticate to access the build environmentgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.1.8 | Ensure the build infrastructure is automatically scanned for vulnerabilitiesgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.2.1 | Ensure build workers are single-usedgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.2.2 | Ensure build worker environments and commands are passed and not pulledgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.2.3 | Ensure the duties of each build worker are segregatedgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.2.4 | Ensure build workers have minimal network connectivitygithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.2.5 | Ensure run-time security is enforced for build workersgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.2.6 | Ensure build workers are automatically scanned for vulnerabilitiesgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.2.7 | Ensure build workers' deployment configuration is stored in a version control platformgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.2.8 | Ensure resource consumption of build workers is monitoredgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.3.1 | Ensure all build steps are defined as codegithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.3.2 | Ensure steps have clearly defined build stage input and outputgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.3.3 | Ensure output is written to a separate, secured storage repositorygithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |
| TMA-GITHUB-2.3.5 | Ensure access to build process triggering is minimizedgithub · Nivo 1 | github | Srednja | 1 | Ručni pregled |