To become a CNA, we need to more clearly specifiy the scope of
security support. This change updates the document and points
to and pages generated from

Also fixed a typo in the following paragraph.

Signed-off-by: Lars Kurth <>
security-policy.pandoc | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/security-policy.pandoc b/security-policy.pandoc
index 5783183..6796220 100644
--- a/security-policy.pandoc
+++ b/security-policy.pandoc
@@ -19,7 +19,15 @@ Scope of this process
 This process primarily covers the [Xen Hypervisor
-Vulnerabilties reported against other Xen Project teams will be handled on a
+Specific information about features with security support can be found in
+1.  [](;a=blob;
+    in the releases' tar ball and its xen.git tree and on
+    [web pages generated from the 
+2.  For releases that do not contain, this information can be found
+    on the [Release Feature wiki 
+Vulnerabilities reported against other Xen Project teams will be handled on a
best effort basis by the relevant Project Lead together with the Security
Response Team.
@@ -401,7 +409,7 @@ Change History
 <div class="box-note">
+-   **v3.18 April 9th 2017:** Added reference to
-   **v3.17 July 20th 2017:** Added Zynstra
-   **v3.16 April 21st 2017:** Added HostPapa
-   **v3.15 March 21st 2017:** Added CloudVPS (Feb 13) and BitDefender SRL

Xen-devel mailing list

Reply via email to