a1bca9c436
We need a safe way for people to report vulnerabilities. People now can go on SECURITY.md and follow our policy. We want to have a policy for expected behaviour. People can check out CODE_OF_CONDUCT.md.
23 lines
1.1 KiB
Markdown
23 lines
1.1 KiB
Markdown
# Security Policy
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
Security is very important to us.
|
|
|
|
If you have any issue regarding security, please disclose the information responsibly submiting [this form](https://vdp.numerique.gouv.fr/p/Send-a-report?lang=en) and not by creating an issue on the repository. You can also email us at docs@numerique.gouv.fr
|
|
|
|
We appreciate your effort to make Docs more secure.
|
|
|
|
## Vulnerability disclosure policy
|
|
|
|
Working with security issues in an open source project can be challenging, as we are required to disclose potential problems that could be exploited by attackers. With this in mind, our security fix policy is as follows:
|
|
|
|
1. The Maintainers team will handle the fix as usual (Pull Request,
|
|
release).
|
|
2. In the release notes, we will include the identification numbers from the
|
|
GitHub Advisory Database (GHSA) and, if applicable, the Common Vulnerabilities
|
|
and Exposures (CVE) identifier for the vulnerability.
|
|
3. Once this grace period has passed, we will publish the vulnerability.
|
|
|
|
By adhering to this security policy, we aim to address security concerns
|
|
effectively and responsibly in our open source software project. |