You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user/cve_tracking.md
+2-4
Original file line number
Diff line number
Diff line change
@@ -28,11 +28,9 @@ When creating a CVE object, the following fields are available. Fields in **bold
28
28
!!! note
29
29
In addition to these standard fields, you can also add one or more [Custom Fields](https://docs.nautobot.com/projects/core/en/stable/models/extras/customfield/) to the model.
30
30
31
-
<<<<<<< HEAD
32
-
=======
33
31
### Software Association
34
32
35
-
As stated previously, you can associate a CVE to one or many [Software objects](./software_lifecycle.md#software-objects). These relationships will present themselves as breadcrumb links on the CVE item's detail view, and as the "Related CVEs" tab on the Software item's detail view.
33
+
As stated previously, you can associate a CVE to one or many software versions. These relationships will present themselves as breadcrumb links on the CVE item's detail view, and as the "Related CVEs" tab on the Software item's detail view.
36
34
37
35
Example of a breadcrumb link on a CVE item's view:
38
36
@@ -41,7 +39,6 @@ Example of a breadcrumb link on a CVE item's view:
41
39
Example of the "Related CVEs" tab on a Software item's view:
42
40
43
41

44
-
>>>>>>> a54d358 (Adding the new NIST CVE Tracking feature for 3.x release.)
45
42
46
43
## Vulnerability objects
47
44
@@ -80,6 +77,7 @@ An External Integration must be created and configured in order to use the NIST
80
77
- A new Secrets Group object named ``NAUTOBOT DLM NIST SECRETS GROUP`` used for access to the NIST API Key from the External Integration.
81
78
- A new Secret object named ``NAUTOBOT DLM NIST API KEY``. This object is created for you during setup with minimum defaults. The Secret name must be exactly as above, but you will need to configure the Secret to properly access the NIST API Key.
82
79
- To obtain your NIST API Key go [here]('https://nvd.nist.gov/developers/request-an-api-key').
80
+
- This key will be made invalid if not used for a seven day period and a request for a new key will be necessary to use this function.
83
81
84
82
NOTE: You may change the name of the External Integration or create your own using other configuration settings, but the SecretsGroup and Secret objects must be named as above. The External Integration is selected when starting the Job run.
0 commit comments