Skip to content

Commit a5e182b

Browse files
fix: security.md typo
1 parent ba60ad4 commit a5e182b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

handbook/security.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ The vulnerability management workflow is a structured approach to managing secur
163163

164164
1. **Focus on released products**: Since builds occur in a protected environment, the primary focus is on vulnerabilities in released products.
165165

166-
2. **Automated identification**: The identification process is automated. Every night, the [SBOM Uploader](https://github.com/NethServer/nh-sbom/actions/workflows/sbom-uploader.yml) GitHub Action scans a list of configured repositories, retrieve the SBOMs, and uploads them to [Dependency Track](https://dependencytrack.org/). Nethesis maintains its own instance of Dependency Track at [https://dependecytrack.nethesis.it](https://dependecytrack.nethesis.it). Access to this platform is restricted to Nethesis employees; any employee can request an account for access.
166+
2. **Automated identification**: The identification process is automated. Every night, the [SBOM Uploader](https://github.com/NethServer/nh-sbom/actions/workflows/sbom-uploader.yml) GitHub Action scans a list of configured repositories, retrieve the SBOMs, and uploads them to [Dependency Track](https://dependencytrack.org/). Nethesis maintains its own instance of Dependency Track at [https://dependencytrack.nethesis.it](https://dependencytrack.nethesis.it). Access to this platform is restricted to Nethesis employees; any employee can request an account for access.
167167

168168
3. **Vulnerability analysis**: Each project manager must allocate a minimum amount of time within the development process to analyze discovered vulnerabilities, focusing on critical and high-priority issues. It is recommended to allocate enough time every month for this task, including time for handling [EOL](#handling-end-of-life-eol).
169169

@@ -197,4 +197,4 @@ Mitigation can be documented in the project manual or README file, ensuring user
197197
## Best practices
198198

199199
When creating software, it is essential to follow best practices to ensure security and maintainability.
200-
Take a look at the [Best practices](best_practices.md) section for more details on how to create secure containers, manage dependencies, and implement testing.
200+
Take a look at the [Best practices](best_practices.md) section for more details on how to create secure containers, manage dependencies, and implement testing.

0 commit comments

Comments
 (0)