Update FAQ #33
Update FAQ #33
Conversation
|
|
||
| ### Does NB Defense JupyterLab Extension run in my kernel? | ||
|
|
||
| We recommend that you isolate NB Defense from the kernel that you are using for your notebook. If you have installed NB Defense into a separate python environment, it will not run in your kernel. We do use your active kernels python path to determine which third party dependencies are installed, so we can scan them for CVEs and licenses. | ||
| No. We recommend installing NB Defense Jupyterlab extension outside of Kernel specific environment. NB Defense runs its code on the Jupyter Server instead of Notebook specific Kernel(s). We do use your active kernels python path to determine which third party dependencies are installed, so we can scan them for CVEs and licenses. |
There was a problem hiding this comment.
Current
We recommend installing NB Defense Jupyterlab extension outside of Kernel specific environment.
Recommended
We recommend installing NB Defense JupyterLab extension outside of a kernel-specific environment.
Also, we should add an apostrophe for kernel's and capitalize Python in active kernel's Python path in the next sentence.
|
|
||
| NB Defense is special because it allows you to scan Jupyter Notebooks. We provide both a [JupyterLab Extension](./getting-started/jupyter-lab-extension.md) that you can use to scan notebooks while you're working, and a [CLI](./getting-started/cli.md) that you can use to scan groups of notebooks or repositories. Using both of these tools, you can scan your notebooks for personally identifiable information (PII), secrets, common exposures and vulnerabilities (CVEs), and non permissive licenses. | ||
|
|
||
| NB Defense allows you to scan Jupyter Notebooks. Currently most security tools do not support Notebook `.ipynb` formatted files. NB Defense fills this gap. We provide both a [JupyterLab Extension](./getting-started/jupyter-lab-extension.md) that you can use to scan notebooks within Jupyterlab environment, and a [CLI](./getting-started/cli.md) that you can use to scan groups of notebooks or repositories. Using both of these tools, you can scan your notebooks for personally identifiable information (PII), secrets, common exposures and vulnerabilities (CVEs), and non permissive licenses. |
There was a problem hiding this comment.
Current
that you can use to scan notebooks within Jupyterlab environment
Recommended
that you can use to scan notebooks within a JupyterLab environment
There was a problem hiding this comment.
Perhaps instead of saying they don't support .ipynb files, state that they aren't rendering findings in a way that a Jupyter user understands. Specifically they will report an issue on a line of a JSON file, not within a specific cell or output.
No description provided.