Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Further details for offline environments (#955) #960

Merged
merged 2 commits into from
Nov 11, 2020
Merged

Further details for offline environments (#955) #960

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
952642a
Further details for offline environments (#955)
anthonyharrison Nov 9, 2020
bf46b38
Further details for offline environments (#955)
anthonyharrison Nov 9, 2020
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
6 changes: 4 additions & 2 deletions doc/how_to_guides/offline.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,10 @@ The way of transfer depends on the environment. The files to be transferred are
## Import the vulnerability database file on the offline system
The vulnerability database should be copied into ~/.cache/cve-bin-tool

## Run cve-bin-tool with --update never option
In an offline environment, when running a scan specify `--update never` so that cve-bin-tool doesn't attempt to download the latest database files.
## Run cve-bin-tool with --update never and --disable-version-check options
In an offline environment, when running a scan specify `--update never` so that cve-bin-tool doesn't attempt to download the latest database files and `--disable-version-check` so that the cve-bin-tool doesn't attempt to check for a newer version of the tool.

## Maintenance Updates
In an offline environment, it is important to update the vulnerability database on a regular basis as often as you feel appropriate, so that the scanner can continue to detect recently-identified vulnerabilities. If any changes to CVE data is required (e.g. to remove false positives), you might also want to create and copy over a triage data file for usage.

It is important to periodically check if the cve-bin-tool has also been updated as this check cannot be performed within an offline environment.