From 984894270f2fa384827b86e37b353ffed1afd2fc Mon Sep 17 00:00:00 2001
From: Krzysztof Opasiak <k.opasiak@samsung.com>
Date: Tue, 28 May 2019 11:02:41 +0200
Subject: Add reference to OSA repo

Add reference to ONAP Security to ensure that it is navigable from
main ONAP documentation.

Issue-ID: SECCOM-239
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Ia76fc2a19e3326078f1b2605a0d29d54dd6a9042
---
 docs/release/index.rst | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

(limited to 'docs')

diff --git a/docs/release/index.rst b/docs/release/index.rst
index c3bcba2f4..a9d3e764a 100644
--- a/docs/release/index.rst
+++ b/docs/release/index.rst
@@ -160,8 +160,14 @@ ONAP Dublin Release provides multiple documents including the following:
 
 Security Notes
 ==============
+Details about discovered and mitigated vulnerabilities are in :ref:`ONAP Security <onap-security>`
+
+.. toctree::
+   :hidden:
+
+   ../submodules/osa.git/docs/index.rst
+
 ONAP has adopted the `CII Best Practice Badge Program <https://bestpractices.coreinfrastructure.org/en>`_.
-The goal of the Casablanca release is for all ONAP projects to be close to achieving a CII Passing badge.
 
 - `Badging Requirements <https://github.com/coreinfrastructure/best-practices-badge#core-infrastructure-initiative-best-practices-badge>`_
 - `Badging Status for all ONAP projects <https://bestpractices.coreinfrastructure.org/en/projects?q=onap>`_
-- 
cgit 1.2.3-korg