From f032053bfb91ed7f64193e0375e28b33c7826748 Mon Sep 17 00:00:00 2001 From: Eric Harney Date: Wed, 4 Apr 2018 14:15:28 -0400 Subject: [PATCH] Doc: Add driver security notes to contributor doc Document some requirements that driver authors should consider when creating drivers. Change-Id: Ieae8863d5e4c140545d89c4cfa4e019dbb301a36 --- doc/source/contributor/drivers.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/source/contributor/drivers.rst b/doc/source/contributor/drivers.rst index 412c2fa24ab..df280f38d7d 100644 --- a/doc/source/contributor/drivers.rst +++ b/doc/source/contributor/drivers.rst @@ -55,6 +55,18 @@ Core Functionality * Clone Volume * Extend Volume +Security Requirements +--------------------- + +* Drivers must delete volumes in a way where volumes deleted from the backend + will not leak data into new volumes when they are created. Cinder operates + in multi-tenant environments and this is critical to ensure data safety. +* Drivers should support secure TLS/SSL communication between the cinder + volume service and the backend as configured by the "driver_ssl_cert_verify" + and "driver_ssl_cert_path" options in cinder.conf. +* Drivers should use standard Python libraries to handle encryption-related + functionality, and not contain custom implementations of encryption code. + Volume Stats ------------