Importing NVD data into Assets
To import NVD data into Assets, navigate to the Import section in the object schema configuration. Learn more about importing in Assets
インポート タイプ設定
Here's the list of configuration options:
| 名前 | 説明 |
|---|---|
| Published range start date | Vulnerabilities published from this date will be imported. This field is mandatory. Enter the date in the format YYYY-MM-DD. The oldest CVE object in NVD database was published on 1988-10-01. If you’d like to import the complete NVD database, use this date. |
| Published range start date | When set, only the CVEs modified in the last n days will be imported for the CVEs published within the date range set above and the corresponding objects will be updated. Set this field after your initial import is complete to enable faster synching. We recommend that you keep this number greater than your import schedule interval so you don’t miss any updates. |
| Last modified (in days) | When set, only the CVEs modified in the last n days will be imported for the CVEs published within the date range set above and the corresponding objects will be updated. Set this field after your initial import is complete to enable faster synching. We recommend that you keep this number greater than your import schedule interval so you don’t miss any updates. |
| API key | As NVD applies rate limiting to their services, you can synchronize data faster by using an API key. |
Here’s an example configuration to import the entire NVD Database into an Assets Schema:
- Set Published range start date field to 1988-10-01.
- Leave the Published range end date field empty.
- Add your API key in the API Key field.
- Leave the Last modified (in days) field empty.
- Run the import. This import takes up a significant amount of time and memory to complete as you’re importing the full range of data.
- Once import is complete, edit the configuration settings as below:
- Enter 5 in the Last modified (in days) field.
Enter Set synchronization config to run every day.
- [保存] を選択します。