Input this data into NVD database.

[LiamTownsley2]

No description provided.

[LiamTownsley2]

Best Practices

When properly implemented, the following practices enable users to efficiently download the complete NVD dataset and to accurately maintain this data using very few requests. To further assist developers working with the APIs, the NVD is documenting the best practices for popular workflows.

Initial Data Population

During initial dataset population, users should start by calling the API beginning with a startIndex of 0. Iterative requests should increment the startIndex by the value of resultsPerPage until the response's startIndex has exceeded the value in totalResults.

Maintaining Data

• After initial data population has occurred, the last modified date parameters provide an efficient way to update a user's local repository and stay within the API rate limits. No more than once every two hours, automated requests should include a range where lastModStartDate equals the time of the last CVE or CPE received and lastModEndDate equals the current time.
• It is recommended that users "sleep" their scripts for six seconds between requests.
• It is recommended to use the default resultsPerPage value as this value has been optimized for the API response.
• Enterprise scale development should enforce these practices through a single requestor to ensure all users are in sync and have the latest CVE, Change History, CPE, and CPE match criteria information.

SOURCE: https://nvd.nist.gov/developers/start-here

[LiamTownsley2]

send 3 api requests for a scan, as the database doesnt seem to do very well fuzzy searching:

• Manufacturer + Name
• Name + Version
• Manufacturer + Name + Version

keep in mind the database splits into multiple pages, will need to go through all pages for all requests and store them and then make a set with all CVE's, so they can be ensured they are unique, then store them in db as a scan & display to user