Differences

This shows you the differences between two versions of the page.

--- securitypolicy [2019/02/10 16:23] – update security process henningw
+++ securitypolicy [2019/02/10 19:00] (current) – move page to security namespace henningw
@@ Line 1: / Line 1: @@
-==== Security Vulnerability Policy ====
-References:
-  * [[https://wiki.asterisk.org/wiki/display/AST/Asterisk+Security+Vulnerabilities|Asterisk security process]]
-  * [[https://en.wikipedia.org/wiki/Vulnerability_(computing)|Wikipedia reference for vulnerabilities]]
-=== Definition ===
-A security vulnerability is (for example) when a user of Kamailio can cause Kamailio to crash or lock up by sending messages to the server process.
-=== Reporting a security Vulnerability ===
-If you believe there's a security vulnerability, please don't use the public forums. Send an e-mail to the security team and the issue will be handled properly.
-  - Send an e-mail to **security at kamailio dot org** and include the following information
-     * A summary
-     * A detailed explanation of how this issue can be exploited and/or reproduced
-  - A member of the Kamailio Security Team will respond
-  - The kamailio developer team will work to solve the issue.
-  - When there is a patch for the issue, it should NOT be committed directly without clarification with the security team. In many cases this should be coordinated with the release of a security release as well as the publication of a Kamailio project security vulnerability report.
-=== Publishing security vulnerabilities ===
-Kamailio will publish security vulnerabilities, including an CVE ID, on the kamailio-business mailing list, sr-dev, sr-users as well as related lists. The advisories will also be published on the kamailio.org web site.
-CVE entries should be created for vulnerabilities in the core and major modules, for rarely used modules this is not necessary. If there are several security issues together in one release, they should be announced together.
-The Kamailio project release security fixed in the normal time based maintenance schedule, no immediate security releases are done. If possible a non-code workaround should be provided for the found security vulnerability.
-=== Timeline of the security process ===
-  - Initial acknowledge time to the reporting party for a report about a new security issue for a new report: 3 working days
-  - Time for verification and bug fix from Kamailio development: 5 working days (could be extended e.g. in vacation period)
-  - Waiting time for public announcement after the fix is in an official release: 2 months
-  - Project preparation time for kamailio.org announcement: 3 working days
-=== Kamailio Security Team ===
-A Kamailio Security team is appointed with core developers of the project. These individuals will be part of the security process and review patches and text for the vulnerability report. Persons of this group take the role of Kamailio Security Officers. One of these should manage each security incident - which does not mean solving the code issue, but managing the process from report to publication and patch release.
-=== PGP encryption ===
-The address used for reporting security reports to the Kamailio project should have a PGP key associated, used by the security officers.