Doc Migration (master) (#1377)
* Doc Migration from Gitlab (#1289) * doc migration * fix * Update FakeQuantize_1.md * Update performance_benchmarks.md * Updates graphs for FPGA * Update performance_benchmarks.md * Change DL Workbench structure (#1) * Changed DL Workbench structure * Fixed tags * fixes * Update ie_docs.xml * Update performance_benchmarks_faq.md * Fixes in DL Workbench layout * Fixes for CVS-31290 * [DL Workbench] Minor correction * Fix for CVS-30955 * Added nGraph deprecation notice as requested by Zoe * fix broken links in api doxy layouts * CVS-31131 fixes * Additional fixes * Fixed POT TOC * Update PAC_Configure.md PAC DCP 1.2.1 install guide. * Update inference_engine_intro.md * fix broken link * Update opset.md * fix * added opset4 to layout * added new opsets to layout, set labels for them * Update VisionAcceleratorFPGA_Configure.md Updated from 2020.3 to 2020.4 Co-authored-by: domi2000 <domi2000@users.noreply.github.com>
This commit is contained in:
1 parent
4037613db3
commit
ef45b5da8d
532 files changed
+30445
-313
No files matched your search
@@ -0,0 +1,7 @@
|
||||
# Introduction to OpenVINO™ Security {#openvino_docs_security_guide_introduction}
|
||||
|
||||
Deploying deep learning models for OpenVINO™ may raise security and privacy issues.
|
||||
Trained models are often valuable intellectual property and you may choose to protect them with encryption or other security tools.
|
||||
|
||||
Actual security and privacy requirements depend on your unique deployment scenario.
|
||||
This section provides general guidance on using OpenVINO tools and libraries securely.
|
||||
@@ -0,0 +1,36 @@
|
||||
# Deep Learning Workbench Security {#openvino_docs_security_guide_workbench}
|
||||
|
||||
Deep Learning Workbench (DL Workbench) is a web application running within a Docker\* container.
|
||||
|
||||
## Run DL Workbench
|
||||
|
||||
Unless necessary, limit the connections to the DL Workbench to `localhost` (127.0.0.1), so that it
|
||||
is only accessible from the machine the Docker container is built on:
|
||||
|
||||
* The script [starting the DL Workbench from the
|
||||
package](@ref workbench_docs_Workbench_DG_Install_from_Package) ensures that the container and the web
|
||||
application are accessible only from the `localhost` by default.
|
||||
|
||||
* When using `docker run` to [start the DL Workbench from Docker
|
||||
Hub](@ref workbench_docs_Workbench_DG_Install_from_Docker_Hub), limit connections for the host IP 127.0.0.1.
|
||||
For example, limit the connections for the host IP to the port `5665` with the `-p
|
||||
127.0.0.1:5665:5665` command . Refer to [Container
|
||||
networking](https://docs.docker.com/config/containers/container-networking/#published-ports) for
|
||||
details.
|
||||
|
||||
## Authentication Security
|
||||
|
||||
DL Workbench uses [authentication tokens](@ref workbench_docs_Workbench_DG_Authentication) to access the
|
||||
application. The script starting the DL Workbench creates an authentication token each time the DL
|
||||
Workbench starts. Anyone who has the authentication token can use the DL Workbench.
|
||||
|
||||
When you finish working with the DL Workbench, log out to prevent the use of the DL Workbench from
|
||||
the same browser session without authentication.
|
||||
|
||||
To invalidate the authentication token completely, [restart the DL
|
||||
Workbench](@ref workbench_docs_Workbench_DG_Docker_Container).
|
||||
|
||||
## Use TLS to Protect Communications
|
||||
|
||||
[Configure Transport Layer Security (TLS)](@ref workbench_docs_Workbench_DG_Configure_TLS) to keep the
|
||||
authentication token encrypted.
|
||||
Reference in new issue
Block a user