From 547d6d4bcc394c7a89b85f97c46753fa0e04b63f Mon Sep 17 00:00:00 2001 From: Jeremy Long Date: Tue, 5 May 2015 19:38:28 -0400 Subject: [PATCH] fixed formating issues Former-commit-id: d602cf23c16ec7b1a7e77011ab7dd0e08579aa18 --- src/site/markdown/data/mirrornvd.md | 25 ++++++++++++++++--------- 1 file changed, 16 insertions(+), 9 deletions(-) diff --git a/src/site/markdown/data/mirrornvd.md b/src/site/markdown/data/mirrornvd.md index b7cbfd2e4..3e70542ed 100644 --- a/src/site/markdown/data/mirrornvd.md +++ b/src/site/markdown/data/mirrornvd.md @@ -4,13 +4,20 @@ Several organizations have opted to mirror the NVD on an internal server and have the dependency-check clients simply pull the updates from the mirror. This setup is fairly simple: -1) Setup a nightly job to pull down the latest NVD files files from NIST - * See the [Nist-Data-Mirror](https://github.com/stevespringett/nist-data-mirror/) - project on github. - * All of the NVD -2) Configure the dependency-check clients to use the internal CVE urls. Note, all four URLs +
    +
  1. Setup a nightly job to pull down the latest NVD files files from NIST +
      +
    • Note, all of the NVD files must be downloaded: both 1.2 and 2.0 schema for 2002 on.
      • +
    • See the Nist-Data-Mirror project on github.
      • +
    +
    2. +
  2. Configure the dependency-check clients to use the internal CVE urls. Note, all four URLs must be specified (see the configuration for the specific dependency-check client used): - * cveUrl12Modified - * cveUrl20Modified - * cveUrl12Base - * cveUrl20Base +
      +
    • cveUrl12Modified
      • +
    • cveUrl20Modified
      • +
    • cveUrl12Base
      • +
    • cveUrl20Base
      • +
    +
    3. +