Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

[DOC] Add instructions to report a security vulnerability #16383

Merged
merged 1 commit into from
Oct 7, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/static_site/src/pages/api/faq/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,23 @@ permalink: /api/faq/security
<!--- specific language governing permissions and limitations -->
<!--- under the License. -->

# Reporting a security vulnerability
The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against its products.

We strongly encourage folks to report such problems to our private security mailing list first, before disclosing them in a public forum.

Please note that the security mailing list should only be used for reporting undisclosed security vulnerabilities and managing the process of fixing such vulnerabilities. We cannot accept regular bug reports or other queries at this address. All mail sent to this address that does not relate to an undisclosed security problem in our source code will be ignored.


Questions about:
* if a vulnerability applies to your particular application
* obtaining further information on a published vulnerability
* availability of patches and/or new releases
should be addressed to the users mailing list. Please see the [mailing lists page](/community/contribute#mxnet-dev-communications) for details of how to subscribe.

The private security mailing address is: <a href="mailto:[email protected]">[email protected]</a> <i class="far fa-envelope">. Feel free to consult the general [Apache Security guide](http://www.apache.org/security/) for further details about the reporting process.


# MXNet Security Best Practices

MXNet framework has no built-in security protections. It assumes that the MXNet entities involved in model training and inferencing (hosting) are fully trusted. It also assumes that their communications cannot be eavesdropped or tampered with. MXNet consumers shall ensure that the above assumptions are met.
Expand Down