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đena 122 pravilaod 16.927Stranica 5 od 5
| ID | Naslov | Platforma | Ozbiljnost | Nivo | Provera |
|---|---|---|---|---|---|
| TMA-GITLAB-5.1.1 | Ensure deployment configuration files are separated from source codegitlab · Nivo 2 | gitlab | Srednja | 2 | Ručni pregled |
| TMA-GITLAB-5.1.2 | Ensure changes in deployment configuration are auditedgitlab · Nivo 1 | gitlab | Srednja | 1 | Ručni pregled |
| TMA-GITLAB-5.1.3 | Ensure scanners are in place to identify and prevent sensitive data in deployment configurationgitlab · Nivo 1 | gitlab | Srednja | 1 | Ručni pregled |
| TMA-GITLAB-5.1.4 | Limit access to deployment configurationsgitlab · Nivo 1 | gitlab | Srednja | 1 | Ručni pregled |
| TMA-GITLAB-5.1.5 | Scan Infrastructure as Code (IaC)gitlab · Nivo 2 | gitlab | Srednja | 2 | Ručni pregled |
| TMA-GITLAB-5.1.6 | Ensure deployment configuration manifests are verifiedgitlab · Nivo 1 | gitlab | Srednja | 1 | Ručni pregled |
| TMA-GITLAB-5.1.7 | Ensure deployment configuration manifests are pinned to a specific, verified versiongitlab · Nivo 1 | gitlab | Srednja | 1 | Ručni pregled |
| TMA-GITLAB-5.2.1 | Ensure deployments are automatedgitlab · Nivo 1 | gitlab | Srednja | 1 | Ručni pregled |
| TMA-GITLAB-5.2.2 | Ensure the deployment environment is reproduciblegitlab · Nivo 1 | gitlab | Srednja | 1 | Ručni pregled |
| TMA-GITLAB-5.2.3 | Ensure access to production environment is limitedgitlab · Nivo 1 | gitlab | Srednja | 1 | Ručni pregled |
| TMA-GITLAB-1.1.1 | Ensure any changes to code are tracked in a version control platformgitlab · Nivo 1 | gitlab | Niska | 1 | Ručni pregled |
| TMA-GITLAB-1.1.8 | Ensure inactive branches are periodically reviewed and removedgitlab · Nivo 1 | gitlab | Niska | 1 | Ručni pregled |
| TMA-GITLAB-1.2.5 | Ensure all copies (forks) of code are tracked and accounted forgitlab · Nivo 1 | gitlab | Niska | 1 | Ručni pregled |
| TMA-GITLAB-1.2.6 | Ensure all code projects are tracked for changes in visibility statusgitlab · Nivo 1 | gitlab | Niska | 1 | Ručni pregled |
| TMA-GITLAB-1.2.7 | Ensure inactive repositories are reviewed and archived periodicallygitlab · Nivo 1 | gitlab | Niska | 1 | Ručni pregled |
| TMA-GITLAB-1.3.1 | Ensure inactive users are reviewed and removed periodicallygitlab · Nivo 2 | gitlab | Niska | 2 | Ručni pregled |
| TMA-GITLAB-1.3.13 | Ensure anomalous code behavior is trackedgitlab · Nivo 1 | gitlab | Niska | 1 | Ručni pregled |
| TMA-GITLAB-1.4.2 | Ensure stale applications are reviewed and inactive ones are removedgitlab · Nivo 1 | gitlab | Niska | 1 | Ručni pregled |
| TMA-GITLAB-1.5.7 | Ensure scanners are in place for web application runtime security weaknessesgitlab · Nivo 2 | gitlab | Niska | 2 | Ručni pregled |
| TMA-GITLAB-1.5.8 | Ensure scanners are in place for API runtime security weaknessesgitlab · Nivo 2 | gitlab | Niska | 2 | Ručni pregled |
| TMA-GITLAB-2.1.1 | Ensure each pipeline has a single responsibilitygitlab · Nivo 2 | gitlab | Niska | 2 | Ručni pregled |
| TMA-GITLAB-2.3.4 | Ensure changes to pipeline files are tracked and reviewedgitlab · Nivo 1 | gitlab | Niska | 1 | Ručni pregled |