VNFRQTS - R-41994 change LS 1.1 to TLS 1.2

R-41994 change LS 1.1 to TLS 1.2
modified Chapter4 and Chapter8

Change-Id: I141cafbe5d3377c047e208469f33b12fd141e67f
Issue-ID: VNFRQTS-168
Signed-off-by: steven stark <ss820f@att.com>

diff --git a/docs/Chapter4.rst b/docs/Chapter4.rst
index ee3e90e..420bd33 100644 (file)
--- a/docs/Chapter4.rst
+++ b/docs/Chapter4.rst
@@ -293,7 +293,7 @@ Integration and operation within a robust security environment is necessary and
 * R-46908 The VNF **MUST**, if not using the NCSP’s IDAM API, comply with "password complexity" policy. When passwords are used, they shall be complex and shall at least meet the following password construction requirements: (1) be a minimum configurable number of characters in length, (2) include 3 of the 4 following types of characters: upper-case alphabetic, lower-case alphabetic, numeric, and special, (3) not be the same as the UserID with which they are associated or other common strings as specified by the environment, (4) not contain repeating or sequential characters or numbers, (5) not to use special characters that may have command functions, and (6) new passwords must not contain sequences of three or more characters from the previous password.
 * R-39342 The VNF **MUST**, if not using the NCSP’s IDAM API, comply with "password changes (includes default passwords)" policy. Products will support password aging, syntax and other credential management practices on a configurable basis.
 * R-40521 The VNF **MUST**, if not using the NCSP’s IDAM API, support use of common third party authentication and authorization tools such as TACACS+, RADIUS.
-* R-41994 The VNF **MUST**, if not using the NCSP’s IDAM API, comply with "No Self-Signed Certificates" policy. Self-signed certificates must be used for encryption only, using specified and approved encryption protocols such as LS 1.1 or higher or equivalent security protocols such as IPSec, AES.
+* R-41994 The VNF **MUST**, if not using the NCSP’s IDAM API, comply with "No Self-Signed Certificates" policy. Self-signed certificates must be used for encryption only, using specified and approved encryption protocols such as TLS 1.2 or higher or equivalent security protocols such as IPSec, AES.
 * R-23135 The VNF **MUST**, if not using the NCSP’s IDAM API, authenticate system to system communications where one system accesses the resources of another system, and must never conceal individual accountability.
 
 VNF Identity and Access Management Requirements

diff --git a/docs/Chapter8.rst b/docs/Chapter8.rst
index beffec0..fbe2d89 100644 (file)
--- a/docs/Chapter8.rst
+++ b/docs/Chapter8.rst
@@ -908,7 +908,7 @@ R-09467: The VNF **MUST**  utilize only NCSP standard compute flavors. [5]_
 
 R-62170: The VNF **MUST** over-ride any default values for configurable parameters that can be set by ONAP in the roles, cookbooks and recipes.
 
-R-41994: The VNF **MUST**, if not using the NCSP’s IDAM API, comply with "No Self-Signed Certificates" policy. Self-signed certificates must be used for encryption only, using specified and approved encryption protocols such as LS 1.1 or higher or equivalent security protocols such as IPSec, AES.
+R-41994: The VNF **MUST**, if not using the NCSP’s IDAM API, comply with "No Self-Signed Certificates" policy. Self-signed certificates must be used for encryption only, using specified and approved encryption protocols such as TLS 1.2 or higher or equivalent security protocols such as IPSec, AES.
 
 R-38474: The VNF **MUST** have a corresponding environment file for a Base Module.