diff options
author | Krzysztof Opasiak <k.opasiak@samsung.com> | 2019-08-08 00:04:58 +0200 |
---|---|---|
committer | Krzysztof Opasiak <k.opasiak@samsung.com> | 2019-08-08 00:04:58 +0200 |
commit | 0131effd6aec0e8f2c6fd1b9be485b68b47fc58a (patch) | |
tree | cb70d1d33856f8489e840893d2f792918c51b5f6 | |
parent | c45208e505b860dcb3fd1025056b17a1982c50b2 (diff) |
Explicitly mention onap-security ML in our process
onap-security mailing list is never mentioned in the vulnerability
management. Let's fix this by adding this as a legitimate option of
reporting security vulnerabilities
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Ie2d4b50fa510fbecdcfcf0f17960d222c2618e24
-rw-r--r-- | docs/process.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/process.rst b/docs/process.rst index 2ea2b07..ed6c471 100644 --- a/docs/process.rst +++ b/docs/process.rst @@ -87,7 +87,7 @@ All the tasks mentioned below should be executed by VMS coordinator who is chose Reception ~~~~~~~~~ -A report can be received either as a ticket in `Vulnerability Reporting Jira Project <https://jira.onap.org/projects/OJSI>`_ or as a private encrypted email to one of the VMS members. +A report can be received either as a ticket in `Vulnerability Reporting Jira Project <https://jira.onap.org/projects/OJSI>`_, email to `onap-security@lists.onap.org <onap-security@lists.onap.org>`_ or as a private encrypted email to one of the VMS members. Steps that has to be completed depend on reception method: |